You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/sql-azure-vulnerability-assessment-manage.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ If the vulnerability settings show the option to configure a storage account, yo
28
28
29
29
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.
30
30
31
-
Express configuration does not store scan results if they are identical to previous scans, so the history page updates only when the status of a finding changes.
31
+
Express configuration doesn't store scan results if they're identical to previous scans, so the history page updates only when the status of a finding changes.
32
32
33
33
## Disable specific findings from Microsoft Defender for Cloud (preview)
34
34
@@ -54,17 +54,17 @@ To create a rule:
54
54
- Benchmarks
55
55
56
56
1. Create a disable rule for VA findings on SQL servers on machines
57
-
1. Select Apply rule. Changes might take up to 24hrs to take effect.
57
+
1. Select Apply rule. Changes might take up to 24 hrs to take effect.
58
58
1. To view, override, or delete a rule:
59
59
1. Select Disable rule.
60
60
1. From the scope list, subscriptions with active rules show as Rule applied.
61
61
1. To view or delete the rule, select the ellipsis menu ("...").
62
62
63
63
## Configure email notifications using Azure Logic Apps
64
64
65
-
In order to receive regular updates of your databases’ vulnerability assessment status you can use the following customizable Azure Logic Apps template:
@@ -96,7 +96,7 @@ The express configuration is supported in the latest REST API version with the f
96
96
97
97
To configure vulnerability assessment baselines by using Azure Resource Manager templates, use the `Microsoft.Sql/servers/databases/vulnerabilityAssessments/rules/baselines` type. Make sure that `vulnerabilityAssessments` is enabled before you add baselines.
98
98
99
-
Here are several examples to how you can setup baselines using ARM templates:
99
+
Here are several examples to how you can set up baselines using ARM templates:
100
100
101
101
- Setup batch baseline based on latest scan results:
102
102
@@ -143,7 +143,7 @@ Here are several examples to how you can setup baselines using ARM templates:
143
143
}
144
144
```
145
145
146
-
- Setup baseline for a specific rule:
146
+
- Set up baseline for a specific rule:
147
147
148
148
```json
149
149
{
@@ -159,7 +159,7 @@ Here are several examples to how you can setup baselines using ARM templates:
159
159
}
160
160
```
161
161
162
-
- Setup batch baselines on master database based on latest scan results:
162
+
- Set up batch baselines on the master database based on latest scan results:
163
163
164
164
```json
165
165
{
@@ -174,7 +174,7 @@ Here are several examples to how you can setup baselines using ARM templates:
174
174
175
175
### Using PowerShell
176
176
177
-
Express configuration is not supported in PowerShell cmdlets but you can use PowerShell to invoke the latest vulnerability assessment capabilities using REST API, for example:
177
+
Express configuration isn't supported in PowerShell cmdlets but you can use PowerShell to invoke the latest vulnerability assessment capabilities using REST API, for example:
178
178
179
179
- [Enable express configuration](powershell-sample-vulnerability-assessment-azure-sql.md) on an Azure SQL Server
180
180
- [Setup baselines](powershell-sample-vulnerability-assessment-baselines.md) based on latest scan results for all databases in an Azure SQL Server
@@ -183,7 +183,7 @@ Express configuration is not supported in PowerShell cmdlets but you can use Pow
183
183
184
184
### What happens to the old scan results and baselines after I switch to express configuration?
185
185
186
-
Old results and baselines settings remain available on your storage account, but will not be updated or used by the system. When express configuration is enabled, customers do not have direct access to the result and baseline data because it is stored on internal Microsoft storage.
186
+
Old results and baselines settings remain available on your storage account, but won't be updated or used by the system. When express configuration is enabled, customers don't have direct access to the result and baseline data because it's stored on internal Microsoft storage.
187
187
188
188
### Is there a way with express configuration to get the weekly email report that is provided in the classic configuration?
189
189
@@ -199,7 +199,7 @@ SQL vulnerability assessment reports all vulnerabilities and misconfigurations i
199
199
200
200
### Can I revert back to the classic configuration?
201
201
202
-
Yes. You can revert back to the classic configuration using the existing REST APIs and PowerShell cmdlets. When you revert back to the classic configuration you see a notification in the Azure portal to change to the express configuration.
202
+
Yes. You can revert back to the classic configuration using the existing REST APIs and PowerShell cmdlets. When you revert back to the classic configuration, you see a notification in the Azure portal to change to the express configuration.
203
203
204
204
### Will we see express configuration for other types of SQL?
205
205
@@ -236,7 +236,7 @@ To change an Azure SQL database from the express vulnerability assessment config
236
236
237
237
- Switching to express configuration failed due to a database policy error:
238
238
239
-
**Cause**: Database policies are not 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.
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.
240
240
**Solution**: Disable all database policies for the relevant server and then try to switch to express configuration again.
241
241
242
242
### [Classic configuration](#tab/classic)
@@ -272,7 +272,7 @@ To create a rule:
272
272
273
273
:::image type="content" source="media/defender-for-sql-Azure-vulnerability-assessment/disable-rule-vulnerability-findings-sql.png" alt-text="Create a disable rule for VA findings on SQL servers on machines":::
274
274
275
-
1. Select **Apply rule**. Changes might take up to 24hrs to take effect.
275
+
1. Select **Apply rule**. Changes might take up to 24 hrs to take effect.
276
276
1. To view, override, or delete a rule:
277
277
1. Select **Disable rule**.
278
278
1. From the scope list, subscriptions with active rules show as **Rule applied**.
@@ -389,8 +389,8 @@ Here's an example for defining Baseline Rule VA2065 to `master` database and VA1
389
389
390
390
For `master` database and `user` database, the resource names are defined differently:
0 commit comments