Secure SQL Server (Security Best Practices) and you will be protecting one of an organization’s greatest assets (information/data). Banks need to keep financial data; hospitals need to keep medical records. An online store needs to keep credit card numbers. Having such data published in the public domain violates the confidentiality goal of information. Securing a system requires collective responsibility from all stakeholders involved from end users, developers through to database administrators
. This article gives you ten (10) SQL Server security best practices that will primarily protect you from outside attacks. Servers that are exposed online are more likely to be attacked by hackers. Follow these recommendations and you will make the attacker’s life a living hell.
SQL Server Security 10 Best Practices
- Disable sa account – attackers use it as the default account to attack when a system is compromised. If it has a weak password then bazinga! You can kiss the confidentiality goal of information good bye. All it takes is a simple automated dictionary attack. A dictionary attack uses a list of commonly used passwords to try and connect to SQL server. If the attacker has a valid login, then the chances of a successful attacker are high.
- Access control – SQL Server sinfully allows you to grant different permissions to users. If a user only needs to read data from the database then why in security’s name would we grant them access rights to create, drop and write data. Opportunity makes a thief an attacker. Don’t be an enabler.
- Disable SQL Server browser service – if it were that bad perhaps Microsoft would have removed the feature. The browser service simplifies the process of find instances of SQL Server on a network/computer. From a developer’s point of view, it makes life easy for the users to select the server name from the listed instances and connect to. Every second counts to an attacker to quickly get data and log out, they will thank the gods and you if you enable them to easily find instances of SQL server. Weather you disable this service or not depends on the likelihood of an attack occurring, current security measures already implemented and the impact a successful attack would have on the business organization.
- Change default SQL Server port for servers with sensitive data and high likelihoods of successful network attacks – the attacker needs a port to connect to. The default for SQL server is 1444; change it to a different and you would have added another obstacle for the attacker. Hackers will actually hate you for doing this.
- Enforce password policy for SQL Server authentication – as users we all love qwerty and p@$$word as passwords, we already discussed dictionary word list attacks above. It will only take a couple of minutes to gain access if you allow users to user simple passwords. Password policy ensures that users use long and strong passwords.
- Install only required services – in most enterprise environments, you will have servers dedicated for specific activities i.e. database server, email server etc. enabling IIS on a database server may just open you up to unnecessary attacks. Disable all the services that you are not using and only leave the necessary ones to get the job done. You will actually thank yourself afterwards as this will improve system performance and cut down on the maintenance time and cost of unnecessary services running
- Patch managements – the word patch always reminds me of one eyed pirates and what they are capable of. A patch is an update that fixes security vulnerability. CVEDetails is your best pal when it comes to identifying vulnerabilities. Vulnerability is a weakness in a system that can be exploited to gain or allow users with limited access rights to perform super user actions. Attackers exploit these vulnerabilities to gain access to your system. Always ensure that you install the latest updates for the version of SQL Server that you are using.
- Always use a backup server for critical data – in a world where medical records have been computerized, the server going down is the difference between life and death. Doctors need access to the medical history of a patient before prescribing drugs. A backup server (with a possibility of data replication) can be used as a fallback when things go wrong with the main server. You don’t need to be a hospital system developer to use backup servers. Think of it as a business continuity thing.
- Server disk space – that’s right, SQL server needs space on the disk. As the database grows, it will need disk space. Not having disk space may cause processes to fail.
- Keep the OS secure – as an attacker, if I cannot break into SQL Server then I will simply gain access to the OS, copy the data files, paste on my local machine, attach them using SQL Server management studio then smile flamboyantly as I browse through the credit card numbers, medical records etc. I have access to the database even if I do not know the sa or whatever account’s password used on the server where I got the files from.
SQL Server is a great and popular database engine loved by most windows users. A good security policy in place will turn you into the next rock star database security administrator and users will extend their love to you too. Follow the above best practices to keep data safe.