Security Options Within Microsoft SQL Server

779 Words2 Pages

INTRODUCTION
The integrity and effectiveness of the organizations use of Microsoft SQL Server heavily relies on the steps of the initial implementation. This encompasses many options that ensure security, including but not limited to encryption, authentication, user-defined roles, and auditing. The purpose of the following proposal is to suggest best practices of assuring security within Microsoft SQL Server 2012. Additionally, we will examine the functionality and reasoning behind each security best practice. The goal is to educate administrators and corresponding staff with not only best practices, but how they function and why they matter. Thank you in advance for your consideration.
As most security options are assumed to be strictly provided within the software, it is imperative to consider the physical components associated with SQL Server in that they are properly secured. This means keeping hardware locked away in an area only accessible to administrators. This is the first and most important step of ensuring security.
ENCRYPTION
Encryption is a necessary defense to assist with securing an instance of SQL Server. It is important to understand that there is not a specific algorithm that is right for all circumstances. However, Microsoft (2013) suggests that the following points are understood: that a longer key is more beneficial as they are generally stronger than short keys, strong encryption consumes more CPU, complex passwords are stronger than short passwords, block ciphers are stronger than stream ciphers, large amounts of data should be encrypted with a symmetric key and the symmetric key should be encrypted with an asymmetric key, and if compression is used, the data should be compressed before encrypting it (“Choose an encryption,” 2013).
A beneficial attribute, specific to the enterprise version of SQL Server 2012 is the transparent data encryption (TDE) feature. This feature assists with keeping data secure in the scenario that physical media are stolen. TDE preforms real-time I/O encryption and decryption of database and log files within a SQL Server instance (“Transparent data encryption,” 2013).
AUTHENTICATION
The enhancements in authentication features within SQL Server 2012 have greatly improved the method in which users are able to login. In prior versions, the login could be a windows user account, windows group account, or SQL Server account. This created dependency on individual logins which caused issues with portability (Mistry & Misner, 2012, p. 67). The solution is within Contained Database Authentication. With this feature, the user’s login is authenticated directly into a user database.

Open Document