<\/p>\n
I was doing some security work to make a SQL Server production environment safer and ready for inspections. I had more than 900 SQL Login in the environment.<\/p>\n
First of all, with the help of the following query, I looked at how much of these SQL Logins were checked with Password Policy:<\/p>\n
SELECT is_policy_checked, count(*) [count] FROM sys.sql_logins GROUP BY is_policy_checked<\/pre>\nFirst of all, let me tell you how I did the test. On SQL Server, there is a Function named “PWDCOMPARE<\/strong>“. This function basically takes 2 parameters, the first one is the password you will try, the second one is the encryption has.<\/p>\n
I ran queries similar to the following:<\/strong><\/p>\n
SELECT name FROM sys.sql_logins WHERE PWDCOMPARE('1234', password_hash) = 1\u00a0\r\nSELECT name FROM sys.sql_logins WHERE PWDCOMPARE('12345', password_hash) = 1\u00a0\r\nSELECT name FROM sys.sql_logins WHERE PWDCOMPARE('123456', password_hash) = 1\u00a0\r\nSELECT name FROM sys.sql_logins WHERE PWDCOMPARE('12345678', password_hash) = 1\u00a0\r\nSELECT name FROM sys.sql_logins WHERE PWDCOMPARE('1', password_hash) = 1\u00a0\r\nSELECT name FROM sys.sql_logins WHERE PWDCOMPARE('111111', password_hash) = 1\u00a0\r\nSELECT name FROM sys.sql_logins WHERE PWDCOMPARE('qwerty', password_hash) = 1\u00a0\r\nSELECT name FROM sys.sql_logins WHERE PWDCOMPARE('abc123', password_hash) = 1<\/pre>\nThe following query returns the logins whose password is null:<\/strong><\/p>\n
SELECT name FROM sys.sql_logins WHERE PWDCOMPARE('', password_hash) = 1<\/pre>\nThe following query returns the login whose password is the user name:<\/strong><\/p>\n
SELECT name FROM sys.sql_logins WHERE PWDCOMPARE(name, password_hash) = 1<\/pre>\nI strongly recommend that you do similar security work in SQL Server Instance that you take over. In every possible SQL Instance, you must try to enable Password Policy for Logins so that you can implement a specific security policy.<\/p>\n
According to the Verizon Business 2012 data leakage survey report, 96% of the leaked data in 2011 were taken from database servers.<\/p>\n
In %55 of this, predictable passwords were used.<\/p>\n
In 40% of this, stolen account information was used.<\/p>\n
According to Application Security Inc.research, the top 10 threats to their databases are users with weak passwords or blank passwords. So obviously two studies complement each other. With my test, three studies confirm each other. If you test your SQL logins in your own environment and share your findings with us, I would appreciate it!<\/p>\n\n
<\/div>\n