SQL Server is a repository of sensitive information for organizations, and that is why it is important to ensure that only authorized users have access to this sensitive information. However, securing SQL Server in a way that won’t create errors is not an easy task, and as database administrators (DBAs), we have to perform a series of additional steps to harden security configuration of our SQL Server implementation.
Checkout my article here, which provides Microsoft SQL Server security best practices checklist to help DBAs protect the SQL Server databases from internal and external attacks.
This article is published on SearchSQLServer.techtarget.com.
Databases are an important reservoir of sensitive information, and that is why it is important for us as a DBA to ensure that only authorized users have access to our databases. Obviously, securing SQL Server and databases is not an easy task, and we have to follow a set of best practices in order to accomplish this task.
Check out my article (ie. How to secure SQL Server infrastructure?) that discusses the series of SQL Server security best practices, which must be followed in order to secure SQL Server infrastructure from external and internal attacks. These practices also help organisations to meet various regulatory compliance requirements such as PCI, HIPPA, and SSAE16 etc.
This article is published on SSWUG.org.