Security | Vulnerability Scans and Assessment

How to perform vulnerability scan on Microsoft SQL Server

SQL Vulnerability Assessment is a new feature embedded in some of the most recent versions of SQL Server Management Studio. This feature is relatively very easy to use and it will show you all the security vulnerabilities and anomalies in your SQL database. Following best practice, it is recommended to apply strict security practices thereby ensuring that client’s data are not compromised. If you currently do not have SQL Server Management Studio (SSMS) installed on your PC or Server, kindly follow this link to have it downloaded. See the following guide on MySQL, how to reset Mysql Root password, how to access MySQL Server from command Prompt, how to create and delete MySQL database, and how to migrate Veeam MsSQL Database to a new MsSQL Server.

In this example, I will be performing a Vulnerability Assessment of one of my databases named “SolarWindOrion” as shown below.
Note: Orion is a performance management and fault management application that allows you to view the real-time statistics of your network directly from your web browser. This Db is actually used for this task in my laboratory and I wish to remediate and protect the Database. Click on Download SSMS as shown in the link above.

- Right-click on the database "SolarWindOrion" in SSMS, 
- Navigate to “Tasks”, 
- Then to “Vulnerability Assessment” and 
- Click on “Scan for Vulnerabilities” as shown below

Select the right location where the report will be saved as shown below.

Now Click on Okay and This will execute and prompte any found vulnerability below. See associated errors from my scans below.

Now you will be able to view the scan reports in SSMS. The details of the performed security checks such as failed checks and other information are available in a readable format.

Vulnerability Scan Exported to Excel

Click on one of the errors displayed. Let’s click on the first error as shown above. See the new image of the detailed checks below.

Since these details are self-explanatory, I will proceed and attached a new image showing the fix (remediation) as suggested by Microsoft in order to fix this issue.

Note: The Suggested remediation can be opened in the Querry Editor on a new SQL Querry Window and executed as shown below. In this way, we can have our database protected as suggested by Microsoft (Baseline)

Note: It is recommended to review the scan report, perform the necessary actions and run the scan again to ensure that all security risks are mitigated.

I welcome you to follow me on YouTube Channel. I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.

Notify of
Inline Feedbacks
View all comments
Would love your thoughts, please comment.x