Scan for vulnerabilities on SQL servers
In brief
The article updates guidance for reviewing SQL vulnerability assessment findings from Defender for Cloud or an individual resource page. It adds modern and legacy experience guidance, explains baselines, and directs administrators to use recommendation exemptions for findings they choose to ignore.
What Defender admins need to know
Use the updated guidance when reviewing findings and managing baselines or exemptions. No required administrator action is stated.
Summaries are generated from the documentation change itself.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
- The scan is lightweight, safe, takes only a few seconds per database, and is entirely read-only. It does not make any changes to your database.
- Execute permissions on the following stored procedures are required for some of the vulnerability assessment rules to run correctly: xp_instance_regread, sysmail_help_profile_sp.
Explore vulnerability assessment reportsfindings
The vulnerability assessment service scans your databases every 12 hours.
The vulnerability assessment dashboard provides an overview of assessment results across all your databases. It also summarizes healthy and unhealthy databases and failing checks by risk distribution.
You can view the vulnerability assessment results directly from Defender for Cloud.
From Defender forCloud's sidebar, openor theRecommendationsindividual resource page.Select the recommendation SQL servers on machines should have vulnerability findings resolved. For more information, see the Defender for Cloud recommendations reference page.:::image type="content" source="./media/security-center-advanced-iaas-data/data-and-storage-sqldb-vulns-on-vm.png" alt-text="Screenshot of recommendation cardThe article Review and remediate vulnerabilities provides detailed guidance for working with SQLservers on machines should havevulnerabilityfindings resolved in Defender for Cloud.":::assessment scan results.The detailed view for the SQL servers vulnerability recommendation appears.:::image type="content" source="./media/defender-for-sql-on-machines-vulnerability-assessment/sql-vulnerability-findings.png" alt-text="Screenshot of recommendation details view for SQL servers on machines showing vulnerability findings.":::Check out additional information about the recommendation:For an overview of scanned resources (databases) and the list of security checks that were tested, open theAffected resourcesand select the server of interest.For an overview of the vulnerabilities grouped by a specific SQL database, select the database of interest.
In each view, the security checks are sorted bySeverity. Select a specific security check to see a details pane with aDescription, how toRemediateit, and other related information such asImpactorBenchmark.
Set a baseline
As you review SQL vulnerability assessment results, you can mark specific findings as an acceptable baseline in your environment. A baseline customizes how results are reported. Results that match the baseline are considered passing in later scans. After you establish a baseline security state, the vulnerability assessment scanner reports only deviations from that baseline so you can focus on relevant issues.
Modern recommendations experience:
:::image type="content" source="media/defender-for-sql-on-machines-vulnerability-assessment/set-sql-vulnerability-assessment-baseline.png" alt-text="Screenshot of a SQL Vulnerability Assessment recommendation with Manage query results and remediation and Add all results as baseline highlighted." lightbox="media/defender-for-sql-on-machines-vulnerability-assessment/set-sql-vulnerability-assessment-baseline.png":::
Legacy findings experience:
:::image type="content" source="media/defender-for-sql-on-machines-vulnerability-assessment/analyze-report-for-details.png" alt-text="Screenshot of vulnerability assessment results page where you can mark findings as an acceptable baseline for your environment.":::
Defender for Cloud's integrated Azure Monitor Workbooks gallery includes an interactive report of findings from vulnerability scanners for machines, containers in container registries, and SQL servers.
Findings for each of these scanners are reported in separate recommendations:
Machines should have vulnerability findings resolvedContainer registry images should have vulnerability findings resolved (powered by Qualys)SQL databases should have vulnerability findings resolvedSQL servers on machines should have vulnerability findings resolved
The Vulnerability Assessment Findings report gathers these findings and organizes them by severity, resource type, and category. You can find this report in the workbooks gallery from Defender for Cloud's sidebar.
:::image type="content" source="media/defender-for-sql-on-machines-vulnerability-assessment/vulnerability-assessment-findings-report-sql.png" alt-text="Defender for Cloud's vulnerability assessment findings report":::
DisableExempt specific findings (recommendations)
IfNot all SQL VA findings might be relevant to your organization or configuration, and you needmight choose to ignore a finding rather than remediate it,them regardless of their status. To do this, you can optionally disable it. Disabled findings don't impactcreate an exemption at the subscription or management group level so the recommendation no longer affects your secure score or generate unwanted noise.compliance for that scope.
When a finding matches
@@ -2,8 +2,8 @@ title: Scan for vulnerabilities on SQL servers description: Learn about Microsoft Defender for SQL servers on machines' integrated vulnerability assessment scanner ms.topic: how-to-ms.date: 05/27/2026-ms.custom: sfi-image-nochange+ms.date: 07/03/2026+ms.custom: sfi-image-nochange, msecd-doc-authoring-1013 #customer intent: As a user, I want to scan for vulnerabilities on SQL servers using Microsoft Defender for SQL servers on machines' integrated vulnerability assessment scanner. ai-usage: ai-assisted ---@@ -28,35 +28,25 @@ The integrated [vulnerability assessment scanner](./sql-azure-vulnerability-asse > - The scan is lightweight, safe, takes only a few seconds per database, and is entirely read-only. It does not make any changes to your database. > - Execute permissions on the following stored procedures are required for some of the vulnerability assessment rules to run correctly: xp_instance_regread, sysmail_help_profile_sp. -## Explore vulnerability assessment reports+## Explore vulnerability assessment findings The vulnerability assessment service scans your databases every 12 hours. The vulnerability assessment dashboard provides an overview of assessment results across all your databases. It also summarizes healthy and unhealthy databases and failing checks by risk distribution. -You can view the vulnerability assessment results directly from Defender for Cloud.+You can view the vulnerability assessment results directly from Defender for Cloud or the individual resource page. -1. From Defender for Cloud's sidebar, open the **Recommendations** page.+The article [Review and remediate vulnerabilities](/azure/defender-for-cloud/sql-azure-vulnerability-assessment-find) provides detailed guidance for working with SQL vulnerability assessment scan results. -1. Select the recommendation [SQL servers on machines should have vulnerability findings resolved](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/f97aa83c-9b63-4f9a-99f6-b22c4398f936). For more information, see the [Defender for Cloud recommendations reference page](review-security-recommendations.md).-- :::image type="content" source="./media/security-center-advanced-iaas-data/data-and-storage-sqldb-vulns-on-vm.png" alt-text="Screenshot of recommendation card for SQL servers on machines should have vulnerability findings resolved in Defender for Cloud.":::-- The detailed view for the SQL servers vulnerability recommendation appears.-- :::image type="content" source="./media/defender-for-sql-on-machines-vulnerability-assessment/sql-vulnerability-findings.png" alt-text="Screenshot of recommendation details view for SQL servers on machines showing vulnerability findings.":::--1. Check out additional information about the recommendation:+## Set a baseline - - For an overview of scanned resources (databases) and the list of security checks that were tested, open the **Affected resources** and select the server of interest.+As you review SQL vulnerability assessment results, you can mark specific findings as an acceptable baseline in your environment. A baseline customizes how results are reported. Results that match the baseline are considered passing in later scans. After you establish a baseline security state, the vulnerability assessment scanner reports only deviations from that baseline so you can focus on relevant issues. - - For an overview of the vulnerabilities grouped by a specific SQL database, select the database of interest.+Modern recommendations experience: - In each view, the security checks are sorted by **Severity**. Select a specific security check to see a details pane with a **Description**, how to **Remediate** it, and other related information such as **Impact** or **Benchmark**.+:::image type="content" source="media/defender-for-sql-on-machines-vulnerability-assessment/set-sql-vulnerability-assessment-baseline.png" alt-text="Screenshot of a SQL Vulnerability Assessment recommendation with Manage query results and remediation and Add all results as baseline highlighted." lightbox="media/defender-for-sql-on-machines-vulnerability-assessment/set-sql-vulnerability-assessment-baseline.png"::: -## Set a baseline--As you review SQL vulnerability assessment results, you can mark specific findings as an acceptable baseline in your environment. A baseline customizes how results are reported. Results that match the baseline are considered passing in later scans. After you establish a baseline security state, the vulnerability assessment scanner reports only deviations from that baseline so you can focus on relevant issues.+Legacy findings experience: :::image type="content" source="media/defender-for-sql-on-machines-vulnerability-assessment/analyze-report-for-details.png" alt-text="Screenshot of vulnerability assessment results page where you can mark findings as an acceptable baseline for your environment."::: @@ -68,54 +58,17 @@ Use the [Continuous export](continuous-export.md) feature of Microsoft Defender Defender for Cloud's integrated Azure Monitor Workbooks gallery includes an interactive report of findings from vulnerability scanners for machines, containers in container registries, and SQL servers. -Findings for each of these scanners are reported in separate recommendations:--- [Machines should have vulnerability findings resolved](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/1195afff-c881-495e-9bc5-1486211ae03f)-- [Container registry images should have vulnerability findings resolved (powered by Qualys)](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/dbd0cb49-b563-45e7-9724-889e799fa648)-- [SQL databases should have vulnerability findings resolved](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/82e20e14-edc5-4373-bfc4-f13121257c37)-- [SQL servers on machines should have vulnerability findings resolved](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/f97aa83c-9b63-4f9a-99f6-b22c4398f936)- The Vulnerability Assessment Findings report gathers these findings and organizes them by severity, resource type, and category. You can find this report in the workbooks gallery from Defender for Cloud's sidebar. :::image type="content" source="media/defender-for-sql-on-machines-vulnerability-assessment/vulnerability-assessment-findings-report-sql.png" alt-text="Defender for Cloud's vulnerability assessment findings report"::: -## Disable specific findings--If you need to ignore a finding rather than remediate it, you can optionally disable it. Disabled findings don't impact your secure score or generate unwanted noise.--When a finding matches the criteria you've defined in your disable rules, it won't appear in the list of findings. Typical scenarios include:+## Exempt specific findings (recommendations) -- Disable findings with severity below medium-- Disable findings that are non-patchable-- Disable findings from benchmarks that aren't of interest for a defined scope+Not all SQL VA findings might be relevant to your organization or configuration, and you might choose to ignore them regardless of their status. To do this, you can [create an exemption](/azure/defender-for-cloud/exempt-resource) at the subscription or management group level so the recommendation no longer affects your secure score or compliance for that scope. -> [!IMPORTANT]-> To disable specific findings, you need permission to edit a policy in Azure Policy. Learn more in [Azure RBAC permissions in Azure Policy](/azure/governance/policy/overview#azure-rbac-permissions-in-azure-policy).--To create a rule:--1. From the recommendations detail page for [SQL servers on machines should have vulnerability findings resolved](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/f97aa83c-9b63-4f9a-99f6-b22c4398f936), select **Disable rule**.--1. Select the relevant scope.--1. Define your criteria. You can use any of the following criteria:- - Finding ID- - Severity- - Benchmarks-- :::image type="content" source="./media/defender-for-sql-on-machines-vulnerability-assessment/disable-rule-vulnerability-findings-sql.png" alt-text="Create a disable rule for VA findings on SQL servers on machines.":::--1. Select **Apply rule**. Changes might take up to 24 hours to take effect.--1. To view, override, or delete a rule:-- 1. Select **Disable rule**.-- 1. From the scope list, subscriptions with active rules show as **Rule applied**.-- :::image type="content" source="./media/remediate-vulnerability-findings-vm/modify-rule.png" alt-text="Screenshot showing how to modify or delete an existing rule in the Defender for Cloud portal.":::-- 1. To view or delete the rule, select the ellipsis menu ("...").+> [!NOTE]+> - The exemption setup succeeds, but it will not take effect unless the **["Azure CSPM" standard is assigned](/azure/defender-for-cloud/assign-regulatory-compliance-standards)** on the selected scope.+> - Creating an exemption requires [specific permissions](/azure/defender-for-cloud/exempt-resource#prerequisites). ## Manage vulnerability assessments programmatically @@ -151,7 +104,8 @@ Metadata information about the connected machine is also collected, specifically You can specify the region where SQL Vulnerability Assessment data is stored by choosing the Log Analytics workspace location. Microsoft might replicate data to other regions for resiliency, but it doesn't replicate data outside the geography. -## Next step+<a name="next-step"></a>+## Next steps > [!div class="nextstepaction"] > [Overview of Microsoft Defender for SQL](defender-for-sql-introduction.md) 