Skip to content

Commit 8d9a6f9

Browse files
committed
PM feedback
1 parent 0d90c64 commit 8d9a6f9

File tree

5 files changed

+26
-32
lines changed

5 files changed

+26
-32
lines changed

articles/defender-for-cloud/defender-for-sql-introduction.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,6 @@ Microsoft Defender for Azure SQL helps you discover and mitigate potential [data
1212

1313
- [Vulnerability assessment](#discover-and-mitigate-vulnerabilities): Scan databases to discover, track, and remediate vulnerabilities. Learn more about [vulnerability assessment](sql-azure-vulnerability-assessment-overview.md).
1414
- [Threat protection](#advanced-threat-protection): Receive detailed security alerts and recommended actions based on SQL Advanced Threat Protection to provide to mitigate threats. Learn more about [SQL Advanced Threat Protection](/azure/azure-sql/database/threat-detection-overview).
15-
- Identify sensitive information: Create a custom policy to label and classify sensitive information stored in your databases. Learn more about [SQL information protection](sql-information-protection-policy.md).
1615

1716
When you enable **Microsoft Defender for Azure SQL**, all supported resources that exist within the subscription are protected. Future resources created on the same subscription will also be protected.
1817

16.2 KB
Loading

articles/defender-for-cloud/sql-azure-vulnerability-assessment-enable.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,6 +61,9 @@ To enable vulnerability assessment without a storage account, use the express co
6161

6262
Now you can go to the [**SQL databases should have vulnerability findings resolved**](https://ms.portal.azure.com/#view/Microsoft_Azure_Security_AzureDefenderForData/SqlVaServersRecommendationDetailsBlade/assessmentKey/82e20e14-edc5-4373-bfc4-f13121257c37) recommendation to see the vulnerabilities found in your databases. You can also run on-demand vulnerability assessment scans to see the current findings.
6363

64+
> [!NOTE]
65+
> Each database is randomly assigned a scan time on a set day of the week. Email notifications are scheduled randomly per server on a set day of the week. The email notification report includes data from all recurring database scans that were executed during the preceding week (does not include on-demand scans).
66+
6467
#### Enable express vulnerability assessment at scale
6568

6669
If you have SQL resources that do not have Advanced Threat Protection and vulnerability assessment enable, you can use the [SQL vulnerability assessment APIs](sql-azure-vulnerability-assessment-manage.md#manage-vulnerability-assessments-programmatically) to enable SQL vulnerability assessment with the express configuration at scale.
@@ -84,7 +87,7 @@ To enable vulnerability assessment with a storage account, use the classic confi
8487
1. Configure a storage account where your scan results for all databases on the server or managed instance will be stored. For information about storage accounts, see [About Azure storage accounts](/azure/storage/common/storage-account-create).
8588

8689
1. To configure vulnerability assessments to automatically run weekly scans to detect security misconfigurations, set **Periodic recurring scans** to **On**. The results are sent to the email addresses you provide in **Send scan reports to**. You can also send email notification to admins and subscription owners by enabling **Also send email notification to admins and subscription owners**.
87-
90+
8891
> [!NOTE]
8992
> Each database is randomly assigned a scan time on a set day of the week. Email notifications are scheduled randomly per server on a set day of the week. The email notification report includes data from all recurring database scans that were executed during the preceding week (does not include on-demand scans).
9093

articles/defender-for-cloud/sql-azure-vulnerability-assessment-find.md

Lines changed: 14 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -47,19 +47,19 @@ SQL vulnerability assessment queries the SQL server using publicly available que
4747

4848
### On-demand vulnerability scans
4949

50-
1. SQL vulnerability assessment scans can also be run on-demand:
50+
You can run SQL vulnerability assessment scans on-demand:
5151

52-
1. From the resource's **Defender for Cloud** page, select **View additional findings in Vulnerability Assessment** to access the scan results from previous scans.
52+
1. From the resource's **Defender for Cloud** page, select **View additional findings in Vulnerability Assessment** to access the scan results from previous scans.
5353

54-
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/view-additional-findings-link.png" alt-text="Opening the scan results and manual scan options.":::
54+
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/view-additional-findings-link.png" alt-text="Opening the scan results and manual scan options.":::
5555

56-
1. To run an on-demand scan to scan your database for vulnerabilities, select **Scan** from the toolbar:
56+
1. To run an on-demand scan to scan your database for vulnerabilities, select **Scan** from the toolbar:
5757

58-
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/on-demand-vulnerability-scan.png" alt-text="Select scan to run an on-demand vulnerability assessment scan of your SQL resource":::
58+
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/on-demand-vulnerability-scan.png" alt-text="Select scan to run an on-demand vulnerability assessment scan of your SQL resource":::
5959

6060

61-
> [!NOTE]
62-
> The scan is lightweight and safe. It takes a few seconds to run and is entirely read-only. It doesn't make any changes to your database.
61+
> [!NOTE]
62+
> The scan is lightweight and safe. It takes a few seconds to run and is entirely read-only. It doesn't make any changes to your database.
6363
6464
### Remediate vulnerabilities
6565

@@ -120,27 +120,19 @@ SQL vulnerability assessment allows you to specify the region where your data wi
120120

121121
### Run on-demand vulnerability scans
122122

123-
SQL vulnerability assessment scans can also be run on-demand:
123+
You can run SQL vulnerability assessment scans on-demand:
124124

125-
From the resource'sDefender for Cloudpage, selectView additional findings in vulnerability assessment to access the scan results from previous scans.
125+
1. From the resource's **Defender for Cloud** page, select **View additional findings in Vulnerability Assessment** to access the scan results from previous scans.
126126

127-
To run an on-demand scan to scan your database for vulnerabilities, select Scan from the toolbar:
127+
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/view-additional-findings-link.png" alt-text="Opening the scan results and manual scan options.":::
128128

129-
### Run on-demand scans
129+
1. To run an on-demand scan to scan your database for vulnerabilities, select **Scan** from the toolbar:
130130

131-
1. SQL vulnerability assessment scans can also be run on-demand:
131+
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/on-demand-vulnerability-scan.png" alt-text="Select scan to run an on-demand vulnerability assessment scan of your SQL resource":::
132132

133-
1. From the resource's **Defender for Cloud** page, select **View additional findings in Vulnerability Assessment** to access the scan results from previous scans.
134133

135-
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/view-additional-findings-link.png" alt-text="Opening the scan results and manual scan options.":::
136-
137-
1. To run an on-demand scan to scan your database for vulnerabilities, select **Scan** from the toolbar:
138-
139-
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/on-demand-vulnerability-scan.png" alt-text="Select scan to run an on-demand vulnerability assessment scan of your SQL resource":::
140-
141-
142-
> [!NOTE]
143-
> The scan is lightweight and safe. It takes a few seconds to run and is entirely read-only. It doesn't make any changes to your database.
134+
> [!NOTE]
135+
> The scan is lightweight and safe. It takes a few seconds to run and is entirely read-only. It doesn't make any changes to your database.
144136
145137
### Remediate vulnerabilities
146138

articles/defender-for-cloud/sql-azure-vulnerability-assessment-manage.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -62,9 +62,7 @@ To create a rule:
6262

6363
## Configure email notifications using Azure Logic Apps
6464

65-
To receive regular updates of the vulnerability assessment status for your database, you can use the following customizable Azure Logic Apps template:
66-
67-
https://github.com/Azure/Microsoft-Defender-for-Cloud/tree/main/Workflow%20automation/Notify-SQLVulnerabilityReport
65+
To receive regular updates of the vulnerability assessment status for your database, you can use the [customizable Azure Logic Apps template](https://github.com/Azure/Microsoft-Defender-for-Cloud/tree/main/Workflow%20automation/Notify-SQLVulnerabilityReport).
6866

6967
Using the template will allow you to:
7068

@@ -90,7 +88,7 @@ The express configuration is supported in the latest REST API version with the f
9088
| Execute manual scan | User Database | [Database Sql Vulnerability Assessment Execute Scan](/rest/api/sql/2022-05-01-preview/database-sql-vulnerability-assessment-execute-scan) |
9189
| Execute manual scan | System Database | [Sql Vulnerability Assessment Execute Scan](/rest/api/sql/2022-05-01-preview/sql-vulnerability-assessment-execute-scan) |
9290
| VA settings (GET only is supported for Express Configuration) | User Database | [Database Sql Vulnerability Assessments Settings](/rest/api/sql/2022-05-01-preview/database-sql-vulnerability-assessments-settings) |
93-
| VA Settings operations | Server | [Sql Vulnerability Assessments Settings](/rest/api/sql/2022-05-01-preview/sql-vulnerability-assessments-settings)<br>[Sql Vulnerability Assessments](/rest/api/sql/2022-05-01-preview/sql-vulnerability-assessments |
91+
| VA Settings operations | Server | [Sql Vulnerability Assessments Settings](/rest/api/sql/2022-05-01-preview/sql-vulnerability-assessments-settings)<br>[Sql Vulnerability Assessments](/rest/api/sql/2022-05-01-preview/sql-vulnerability-assessments) |
9492

9593
### Using Resource Manager templates
9694

@@ -229,14 +227,16 @@ To change an Azure SQL database from the express vulnerability assessment config
229227

230228
### Errors
231229

232-
- “Vulnerability Assessment is enabled on this server or one of its underlying databases with an incompatible version” Error:
230+
“Vulnerability Assessment is enabled on this server or one of its underlying databases with an incompatible version”
231+
232+
Possible causes:
233+
234+
- Switching to express configuration failed due to a server policy error. This could be due to a transient operation.
233235

234-
**Cause**: Switching to express configuration failed due to a server policy error. This could be due to a transient operation.
235236
**Solution**: Try again to enable the express configuration. If the issue persists, try to disable the Microsoft Defender for SQL in the Azure SQL resource, select **Save**, enable Microsoft Defender for SQL again, and select **Save**.
236237

237-
- Switching to express configuration failed due to a database policy error:
238+
- Switching to express configuration failed due to a database policy error. Database policies aren't visible in the Azure portal for Defender for SQL vulnerability assessment, so we check for them during the validation stage of switching to express configuration.
238239

239-
**Cause**: Database policies aren't visible in the Azure portal for Defender for SQL vulnerability assessment, so we check for them during the validation stage of switching to express configuration.
240240
**Solution**: Disable all database policies for the relevant server and then try to switch to express configuration again.
241241

242242
### [Classic configuration](#tab/classic)

0 commit comments

Comments
 (0)