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/sql-database/sql-vulnerability-assessment.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ In your Azure SQL Database pane, under the **Security** heading, select **Advanc
50
50
51
51
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.
52
52
53
-

53
+

54
54
55
55
> [!NOTE]
56
56
> 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
61
61
62
62

63
63
64
-
### 3. Analyze the results and resolve problems
64
+
### 3. Analyze the results and resolve issues
65
65
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.
67
67
68
68

69
69
70
70
### 4. Set your baseline
71
71
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.
73
73
74
74

75
75
76
76
### 5. Run a new scan to see your customized tracking report
77
77
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.
79
79
80
80

0 commit comments