Skip to content

Commit f0fcb82

Browse files
authored
Merge pull request #153936 from DavidTrigano/patch-29
Update sql-vulnerability-assessment.md
2 parents 53fe739 + d462064 commit f0fcb82

File tree

1 file changed

+40
-2
lines changed

1 file changed

+40
-2
lines changed

articles/azure-sql/database/sql-vulnerability-assessment.md

Lines changed: 40 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.topic: how-to
1111
author: davidtrigano
1212
ms.author: datrigan
1313
ms.reviewer: vanto
14-
ms.date: 02/11/2021
14+
ms.date: 04/09/2021
1515
tags: azure-synapse
1616
---
1717
# SQL vulnerability assessment helps you identify database vulnerabilities
@@ -120,6 +120,44 @@ Select **Export Scan Results** to create a downloadable Excel report of your sca
120120

121121
Select **Scan History** in the vulnerability assessment pane to view a history of all scans previously run on this database. Select a particular scan in the list to view the detailed results of that scan.
122122

123+
### Disable specific findings from Azure Security Center (preview)
124+
125+
If you have an organizational 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.
126+
127+
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:
128+
129+
- Disable findings with severity below medium
130+
- Disable findings that are non-patchable
131+
- Disable findings from benchmarks that aren't of interest for a defined scope
132+
133+
> [!IMPORTANT]
134+
> To disable specific findings, you need permissions to edit a policy in Azure Policy. Learn more in [Azure RBAC permissions in Azure Policy](../../governance/policy/overview.md#azure-rbac-permissions-in-azure-policy).
135+
136+
To create a rule:
137+
138+
1. From the recommendations detail page for **Vulnerability assessment findings on your SQL servers on machines should be remediated**, select **Disable rule**.
139+
140+
1. Select the relevant scope.
141+
142+
1. Define your criteria. You can use any of the following criteria:
143+
- Finding ID
144+
- Severity
145+
- Benchmarks
146+
147+
:::image type="content" source="../../security-center/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":::
148+
149+
1. Select **Apply rule**. Changes might take up to 24hrs to take effect.
150+
151+
1. To view, override, or delete a rule:
152+
153+
1. Select **Disable rule**.
154+
155+
1. From the scope list, subscriptions with active rules show as **Rule applied**.
156+
157+
:::image type="content" source="../../security-center/media/remediate-vulnerability-findings-vm/modify-rule.png" alt-text="Modify or delete an existing rule":::
158+
159+
1. To view or delete the rule, select the ellipsis menu ("...").
160+
123161
## Manage vulnerability assessments programmatically
124162

125163
### Using Azure PowerShell
@@ -241,4 +279,4 @@ To handle Boolean types as true/false, set the baseline result with binary input
241279

242280
- Learn more about [Azure Defender for SQL](azure-defender-for-sql.md).
243281
- Learn more about [data discovery and classification](data-discovery-and-classification-overview.md).
244-
- Learn more about [Storing vulnerability assessment scan results in a storage account accessible behind firewalls and VNets](sql-database-vulnerability-assessment-storage.md).
282+
- Learn more about [Storing vulnerability assessment scan results in a storage account accessible behind firewalls and VNets](sql-database-vulnerability-assessment-storage.md).

0 commit comments

Comments
 (0)