Skip to content

Commit dc7d738

Browse files
committed
edit pass: sql-vulnerability-assessment
1 parent 9feeae4 commit dc7d738

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ In your Azure SQL Database pane, under the **Security** heading, select **Advanc
5050

5151
Configure a storage account where your scan results for all databases on the server will be stored. For information about storage accounts, see [About Azure storage accounts](../storage/common/storage-create-storage-account.md). After storage is configured, select **Scan** to scan your database for vulnerabilities.
5252

53-
![Scan a database](./media/sql-vulnerability-assessment/pp_va_initialize.png)
53+
![Scan a database](./media/sql-vulnerability-assessment/pp_va_initialize.png)
5454

5555
> [!NOTE]
5656
> 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,21 +61,21 @@ When your scan is finished, your scan report is automatically displayed in the A
6161

6262
![View the report](./media/sql-vulnerability-assessment/pp_main_getstarted.png)
6363

64-
### 3. Analyze the results and resolve problems
64+
### 3. Analyze the results and resolve issues
6565

66-
Review your results and determine the findings in the report that are true security problems in your environment. Drill down to each failed result to understand the impact of the finding and why each security check failed. Use the actionable remediation information provided by the report to resolve the problem.
66+
Review your results and determine the findings in the report that are true security issues in your environment. Drill down to each failed result to understand the impact of the finding and why each security check failed. Use the actionable remediation information provided by the report to resolve the issue.
6767

6868
![Analyze the report](./media/sql-vulnerability-assessment/pp_fail_rule_show_remediation.png)
6969

7070
### 4. Set your baseline
7171

72-
As you review your assessment results, you can mark specific results as being an acceptable *baseline* in your environment. The baseline is essentially a customization of how the results are reported. Results that match the baseline are considered as passing in subsequent scans. 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 problems.
72+
As you review your assessment results, you can mark specific results as being an acceptable *baseline* in your environment. The baseline is essentially a customization of how the results are reported. Results that match the baseline are considered as passing in subsequent scans. 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.
7373

7474
![Set your baseline](./media/sql-vulnerability-assessment/pp_fail_rule_show_baseline.png)
7575

7676
### 5. Run a new scan to see your customized tracking report
7777

78-
After you finish setting up your **Rule Baselines**, run a new scan to view the customized report. Vulnerability Assessment now reports only the security problems that deviate from your approved baseline state.
78+
After you finish setting up your **Rule Baselines**, run a new scan to view the customized report. Vulnerability Assessment now reports only the security issues that deviate from your approved baseline state.
7979

8080
![View your customized report](./media/sql-vulnerability-assessment/pp_pass_main_with_baselines.png)
8181

0 commit comments

Comments
 (0)