By providing strong Passwords, Limited the access to make sure right people have access to the right data, Creating Customized database roles, server roles and assign privileges and by choosing the correct authentication mode etc.

A DBA should be careful in providing security…..General precautions includes:

• Minimize the number of sysadmins allowed to access SQL Server.
• Give users the least amount of permissions they need to perform their job.
• Use stored procedures or views to allow users to access data instead of letting them DIRECTLY access tables.
• When possible, use Windows Authentication logins instead of SQL Server logins.
• Don’t grant permissions to the public database role.
• Remove user login IDs who no longer need access to SQL Server.
• Avoid creating network shares on any SQL Server.
• Turn on login auditing so you can see who has succeeded, and failed, to login.
• Ensure that your SQL Servers are behind a firewall and are not exposed directly to the Internet.
• Using server, database and application roles to control access to the data
• Securing the physical database files using NTFS permissions
• Using an un guessable SA password
• Restricting physical access to the SQL Server
• Disabling the Guest account
• Isolating SQL Server from the web server
• Choose either of the service to run SQL Server (Local User – Not an Admin , Domain User – Not an Admin)
• Restrict the remote administration (TC)
• If SQL Server authentication is used, the credentials are secured over the network by using IPSec or SSL, or by installing a database server certificate.
• Do not use DBO users as application logins
• Firewall restrictions ensure that only the SQL Server listening port is available on the database server.
• Remove the SQL guest user account.
• Remove the BUILTINAdministrators server login.
• Apply the latest security updates / patches

We have plenty of FEATURES in SQL SERVER to enforce the security. The major features include:

• Password policies
• ENCRYPTION
• Limited metadata visibility (system Tables to Catalog Views)
• DDL triggers
• User-schema separation
• Impersonation
• Granular permission sets
• Security catalog views

In addition to these features we have some more added in SQL SERVER 2008, like Policy Based Management, Security Audit, Improved Encryption, Backup Security etc.

When we talk about the security we have to consider the below:

• Patches and Updates
• Services
• Protocols
• Accounts
• Files and Directories
• Shares
• Ports
• Registry
• Auditing and LOGGING
• SQL Server Security
• SQL Server Logins, Users, and Roles
• SQL Server Database Objects

By providing strong Passwords, Limited the access to make sure right people have access to the right data, Creating Customized database roles, server roles and assign privileges and by choosing the correct authentication mode etc.

A DBA should be careful in providing security…..General precautions includes:

We have plenty of features in SQL SERVER to enforce the security. The major features include:

In addition to these features we have some more added in SQL SERVER 2008, like Policy Based Management, Security Audit, Improved Encryption, Backup Security etc.

When we talk about the security we have to consider the below: