Results 1 to 7 of 7

Thread: Site Safety using SQL Server 2005

  1. #1
    Join Date
    Jul 2010
    Posts
    142

    Site Safety using SQL Server 2005

    In order to control access to the website, reporting, three processes will be implemented to control and rights management:
    • Authentication from NTFS permissions (configured from IIS)
    • Management rights from the website
    • Security management data sources
    This implementation, which will be entirely based on Active Directory, will control the user before accessing the site, while allowing them to only see the reports and records concerning them.

  2. #2
    Join Date
    Apr 2008
    Posts
    240

    Re: Site Safety using SQL Server 2005

    The first part aims to verify the identity of the user of the site identity that eventually allows to manage rights. This type of authentication is based on the NTFS file system that can create access permissions on files, which define the access rights to the website. Configuration is done so in two steps:
    • Configure IIS to support the control rights.
    • Setting NTFS permissions on the folder containing the website.

    The following steps would be helpful for configure IIS :
    1. To set these permissions, you must visit the site properties in which the reporting is installed (default: "Default Web Site"), then the tab "Directory Security".
    2. In "Authentication and access control", uncheck "Enable anonymous access".
    It should nevertheless be noted that any computer with a session left unlocked to allow a normal user to access the site with the rights of the owner of the machine (it can also be the case if the user saves the password with the Digest authentication). Once the authentication type is selected, it remains only to configure the NTFS permissions of the file of the site.

  3. #3
    Join Date
    Aug 2008
    Posts
    129

    Re: Site Safety using SQL Server 2005

    Four types of authentication available in IIS:
    • Integrated Windows authentication: information retrieval opening sessions to identify the site (valid if each user is viewing the site from a computer belonging to the field and on which it identified itself with its personal settings when opening session).
    • Digest authentication for Windows domain servers: a dialog appears asking the user to enter the login and password for the domain to connect to the website. For convenience, the user can save the username and password in its session to allow quick access to the site. This type of authentication is possible only on Windows domain servers.
    • Basic Authentication: WARNING: DO NOT USE UNLESS USED IN CONJUNCTION WITH SSL. Indeed, it is an authentication similar to DIGEST authentication but the password is transmitted unencrypted over the network (risk of capture frame).
    • Authentication .NET Passport: This method requires access to the Internet, it is not feasible to use on an intranet.

  4. #4
    Join Date
    Nov 2008
    Posts
    94

    Re: Site Safety using SQL Server 2005

    The site has its own system for managing access to resources. This is a very close and NTFS permissions based on identity when authenticating to the site, and therefore information from Active Directory. For each file and report, it is possible to configure access permissions. By default, they inherit permissions from the parent folder, but it is nevertheless possible to break this inheritance, then restore it later. To configure these security options, simply go to the folder properties and / or report and then in the security section. Five options are available then:
    • Browser: Allows access to file / read-only report.
    • Content Manager: Manage the content server: added file, adding the report.
    • My Reports: Allows you to create and maintain records / reports in a personal space (currently disabled on the server).
    • Publisher: To publish reports and create linked reports accessible to all (unlike My Reports).
    • Report Builder: Allows access to the report generator.
    These permissions, configurable for each file and report allow precise control of resources.

  5. #5
    Join Date
    Apr 2009
    Posts
    65

    Re: Site Safety using SQL Server 2005

    A final point concerns the use of data sources. Indeed, by default, the Windows Integrated Security is selected. However, insofar as it can provide access to data by impersonating a user without the latter's knowledge, it is advisable to disable this option in the configuration utility of surface exposure : Configuration Utility Surface Area> Configuration Utility from the surface for Features> MSSQLSERVER> Reporting Services> Windows Integrated Security> uncheck "Enable Windows Integrated security for connections to the source Data Reporting". Also, when configuring data sources, it will be necessary to provide an account for connecting to the database (the account that has permission to access the data). This account can be different for each database server to increase security, it should have limited right to search the data and the active directory account option "Password never expires" shall be checked.

  6. #6
    Join Date
    Nov 2008
    Posts
    52

    Re: Site Safety using SQL Server 2005

    The implementation of the security of a website reporting should be done with method, because the multiplicity of options may, where appropriate, lead to an omission option, forgetting that when it comes to security, may have unfortunate consequences. Nevertheless, good management rights during the implementation will allow later access pleasant and transparent to the user (file prohibits not visible, invisible because authentication related logging. The website uses CSS technology reporting. It is therefore quite easy to change the graphics of it. The CSS file is at the root of the site reporting, in the style file:
    C: \ Program Files \ Microsoft SQL Server \ MSSQL 3 \ Reporting Services \ ReportManager \ Styles \

  7. #7
    Join Date
    Apr 2008
    Posts
    264

    Re: Site Safety using SQL Server 2005

    While many large companies have adopted business intelligence, this is not the case for all. The main reason being the cost, the arrival of the Business Intelligence Solution for SQL Server 2005 could democratize access to this technology, which, although used, can facilitate decision making and allow to have an objective view of the health of the company. Indeed, through the example that was discussed, we can see the simplicity of implementation. And if everything is not configurable, it is nevertheless a cheap solution for business intelligence that combines simplicity, performance and safety, all around a DBMS famous. Through the different versions of SQL Server, and many features, it is clear that this product may be suitable for both large and small businesses.

Similar Threads

  1. Cannot see Green Site Safety icon on 'Norton Secured' links
    By BonnieT in forum Networking & Security
    Replies: 3
    Last Post: 08-09-2011, 10:28 PM
  2. Norton Site safety warnings on Firefox upgrade
    By Abhra in forum Technology & Internet
    Replies: 4
    Last Post: 18-09-2010, 09:50 AM
  3. Norton site safety link scanner
    By Crista in forum Networking & Security
    Replies: 5
    Last Post: 18-09-2010, 04:01 AM
  4. SITE-To-SITE VPN using Windows Server 2003 Standard
    By S H A R I Q U E in forum Windows Server Help
    Replies: 9
    Last Post: 03-01-2009, 10:55 PM
  5. Upgrade fails: SQL Server Express 2005 to SQL Server 2005
    By Steve BB in forum Small Business Server
    Replies: 3
    Last Post: 11-06-2008, 07:37 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,714,051,640.30407 seconds with 17 queries