Skip to content

Commit edc07fb

Browse files
Add periods to alt-text
1 parent 8f3e03b commit edc07fb

File tree

3 files changed

+12
-12
lines changed

3 files changed

+12
-12
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -78,11 +78,11 @@ To enable vulnerability assessment with a storage account, use the classic confi
7878

7979
1. Select **Configure** on the link to open the Microsoft Defender for SQL settings pane for either the entire server or managed instance.
8080

81-
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/opening-sql-configuration.png" alt-text="Screenshot of the Defender for SQL configuration":::
81+
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/opening-sql-configuration.png" alt-text="Screenshot of the Defender for SQL configuration.":::
8282

8383
1. In the **Server settings** page, enter the Microsoft Defender for SQL settings:
8484

85-
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/sql-vulnerability-scan-settings.png" alt-text="Screenshot of configuring the SQL vulnerability assessment scans":::
85+
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/sql-vulnerability-scan-settings.png" alt-text="Screenshot of configuring the SQL vulnerability assessment scans.":::
8686

8787
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).
8888

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

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ You can run SQL vulnerability assessment scans on-demand:
5757

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

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

6262

6363
> [!NOTE]
@@ -72,7 +72,7 @@ When a vulnerability scan completes, the report is displayed in the Azure portal
7272
- A summary by severity of the risks
7373
- A list of the findings for further investigations
7474

75-
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/sample-sql-vulnerabilities-report.png" alt-text="Screenshot of sample scan report from the SQL vulnerability assessment scanner":::
75+
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/sample-sql-vulnerabilities-report.png" alt-text="Screenshot of sample scan report from the SQL vulnerability assessment scanner.":::
7676

7777
To remediate the vulnerabilities discovered:
7878

@@ -87,11 +87,11 @@ To remediate the vulnerabilities discovered:
8787

8888
1. As you review your assessment results, you can mark specific results as being an acceptable *baseline* in your environment. A baseline is essentially a customization of how the results are reported. In subsequent scans, results that match the baseline are considered as passes. After you've established your baseline security state, vulnerability assessment only reports on deviations from the baseline. In this way, you can focus your attention on the relevant issues.
8989

90-
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/baseline-approval.png" alt-text="Screenshot of approving a finding as a baseline for future scans":::
90+
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/baseline-approval.png" alt-text="Screenshot of approving a finding as a baseline for future scans.":::
9191

9292
1. Any findings you've added to the baseline will now appear as **Passed** with an indication that they've passed because of the baseline changes. There's no need to run another scan for the baseline to take effect.
9393

94-
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/passed-per-custom-baseline.png" alt-text="Screenshot of passed assessments indicating they've passed per custom baseline":::
94+
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/passed-per-custom-baseline.png" alt-text="Screenshot of passed assessments indicating they've passed per custom baseline.":::
9595

9696
Your vulnerability assessment scans can now be used to ensure that your database maintains a high level of security, and that your organizational policies are met.
9797

@@ -130,7 +130,7 @@ You can run SQL vulnerability assessment scans on-demand:
130130

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

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

135135

136136
> [!NOTE]
@@ -145,7 +145,7 @@ When a vulnerability scan completes, the report is displayed in the Azure portal
145145
- A summary by severity of the risks
146146
- A list of the findings for further investigations
147147

148-
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/sample-sql-vulnerabilities-report.png" alt-text="Screenshot of sample scan report from the SQL vulnerability assessment scanner":::
148+
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/sample-sql-vulnerabilities-report.png" alt-text="Screenshot of sample scan report from the SQL vulnerability assessment scanner.":::
149149

150150
To remediate the vulnerabilities discovered:
151151

@@ -160,11 +160,11 @@ To remediate the vulnerabilities discovered:
160160

161161
1. As you review your assessment results, you can mark specific results as being an acceptable *baseline* in your environment. A baseline is essentially a customization of how the results are reported. In subsequent scans, results that match the baseline are considered as passes. After you've established your baseline security state, vulnerability assessment only reports on deviations from the baseline. In this way, you can focus your attention on the relevant issues.
162162

163-
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/baseline-approval.png" alt-text="Screenshot of approving a finding as a baseline for future scans":::
163+
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/baseline-approval.png" alt-text="Screenshot of approving a finding as a baseline for future scans.":::
164164

165165
1. If you change the baselines, use the **Scan** button to run an on-demand scan and view the customized report. Any findings you've added to the baseline will now appear in **Passed** with an indication that they've passed because of the baseline changes.
166166

167-
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/passed-per-custom-baseline.png" alt-text="Screenshot of passed assessments indicating they've passed per custom baseline":::
167+
:::image type="content" source="media/defender-for-sql-azure-vulnerability-assessment/passed-per-custom-baseline.png" alt-text="Screenshot of passed assessments indicating they've passed per custom baseline.":::
168168

169169
Your vulnerability assessment scans can now be used to ensure that your database maintains a high level of security, and that your organizational policies are met.
170170

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -287,14 +287,14 @@ To create a rule:
287287
- Severity
288288
- Benchmarks
289289

290-
:::image type="content" source="media/defender-for-sql-Azure-vulnerability-assessment/disable-rule-vulnerability-findings-sql.png" alt-text="Screenshot of create a disable rule for VA findings on SQL servers on machines":::
290+
:::image type="content" source="media/defender-for-sql-Azure-vulnerability-assessment/disable-rule-vulnerability-findings-sql.png" alt-text="Screenshot of create a disable rule for VA findings on SQL servers on machines.":::
291291

292292
1. Select **Apply rule**. Changes might take up to 24 hrs to take effect.
293293
1. To view, override, or delete a rule:
294294
1. Select **Disable rule**.
295295
1. From the scope list, subscriptions with active rules show as **Rule applied**.
296296

297-
:::image type="content" source="media/defender-for-sql-Azure-vulnerability-assessment/modify-rule.png" alt-text="Screenshot of modify or delete an existing rule":::
297+
:::image type="content" source="media/defender-for-sql-Azure-vulnerability-assessment/modify-rule.png" alt-text="Screenshot of modify or delete an existing rule.":::
298298

299299
1. To view or delete the rule, select the ellipsis menu ("...").
300300

0 commit comments

Comments
 (0)