Skip to content

Commit 3999796

Browse files
author
David Curwin
committed
Fix formatting
1 parent 2171c90 commit 3999796

5 files changed

+17
-22
lines changed

articles/defender-for-cloud/review-pull-request-annotations.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,11 +37,11 @@ Once you've configured the scanner, you're able to view all issues that were det
3737

3838
1. Follow the remediation steps in the annotation.
3939

40-
1. Select **Active** to change the status of the annotation and access the dropdown menu.
40+
1. Select **Active** to change the status of the annotation and access the dropdown menu.
4141

4242
1. Select an action to take:
4343

44-
- **Active** - The default status for new annotations.
44+
- **Active** - The default status for new annotations.
4545
- **Pending** - The finding is being worked on.
4646
- **Resolved** - The finding has been addressed.
4747
- **Won't fix** - The finding is noted but won't be fixed.

articles/defender-for-cloud/review-security-recommendations.md

Lines changed: 10 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -87,34 +87,34 @@ You can perform many actions to interact with recommendations. If an option isn'
8787
- Select **View policy definition** to view the Azure Policy entry for the underlying recommendation (if relevant).
8888

8989
1. In **Findings**, you can review affiliated findings by severity.
90-
90+
9191
:::image type="content" source="media/review-security-recommendations/recommendation-findings.png" alt-text="Screenshot of the findings tab in a recommendation that shows all of the attack paths for that recommendation." lightbox="media/review-security-recommendations/recommendation-findings.png":::
9292

9393
1. In **Take action**:
9494
- **Remediate**: A description of the manual steps required to remediate the security issue on the affected resources. For recommendations with the **Fix** option, you can select **View remediation logic** before applying the suggested fix to your resources.
95-
96-
- **Assign owner and due date**: If you have a [governance rule](governance-rules.md) turned on for the recommendation, you can assign an owner and due date.
97-
95+
96+
- **Assign owner and due date**: If you have a [governance rule](governance-rules.md) turned on for the recommendation, you can assign an owner and due date.
97+
9898
- **Exempt**: You can exempt resources from the recommendation, or disable specific findings using disable rules.
99-
99+
100100
- **Workflow automation**: Set a logic app to trigger with this recommendation.
101-
102-
:::image type="content" source="media/review-security-recommendations/recommendation-take-action.png" alt-text="Screenshot that shows what you can see in the recommendation when you select the take action tab." lightbox="media/review-security-recommendations/recommendation-take-action.png":::
103-
101+
102+
:::image type="content" source="media/review-security-recommendations/recommendation-take-action.png" alt-text="Screenshot that shows what you can see in the recommendation when you select the take action tab." lightbox="media/review-security-recommendations/recommendation-take-action.png":::
103+
104104
1. In **Graph**, you can view and investigate all context that is used for risk prioritization, including [attack paths](how-to-manage-attack-path.md). You can select a node in an attack path to view the details of the selected node.
105105

106106
:::image type="content" source="media/review-security-recommendations/recommendation-graph.png" alt-text="Screenshot of the graph tab in a recommendation that shows all of the attack paths for that recommendation." lightbox="media/review-security-recommendations/recommendation-graph.png":::
107107

108108
## How are recommendations classified?
109109

110110
Every security recommendation from Defender for Cloud is assigned one of three severity ratings:
111-
111+
112112
- **High severity**: These recommendations should be addressed immediately, as they indicate a critical security vulnerability that could be exploited by an attacker to gain unauthorized access to your systems or data. Examples of high severity recommendations are when we’ve discovered unprotected secrets on a machine, overly-permissive inbound NSG rules, clusters allowing images to be deployed from untrusted registries, and unrestricted public access to storage accounts or databases.
113113

114114
- **Medium severity**: These recommendations indicate a potential security risk that should be addressed in a timely manner, but may not require immediate attention. Examples of medium severity recommendations might include containers sharing sensitive host namespaces, web apps not using managed identities, Linux machines not requiring SSH keys during authentication, and unused credentials being left in the system after 90 days of inactivity.
115115

116116
- **Low severity**: These recommendations indicate a relatively minor security issue that can be addressed at your convenience. Examples of low severity recommendations might include the need to disable local authentication in favor of Microsoft Entra ID, health issues with your endpoint protection solution, best practices not being followed with network security groups, or misconfigured logging settings that could make it harder to detect and respond to security incidents.
117-
117+
118118
Of course, the internal views of an organization might differ with Microsoft’s classification of a specific recommendation. So, it's always a good idea to review each recommendation carefully and consider its potential impact on your security posture before deciding how to address it.
119119

120120
## Manage recommendations assigned to you
@@ -192,4 +192,3 @@ When you open the underlying query, and run it, Azure Resource Graph Explorer re
192192
## Next steps
193193

194194
[Remediate security recommendations](implement-security-recommendations.md)
195-

articles/defender-for-cloud/secure-score-access-and-track.md

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ You can find your overall secure score, and your score per subscription, through
1414
1515
## Get your secure score from the portal
1616

17-
Defender for Cloud displays your score prominently in the portal. When you select the Secure score tile on the overview page, you're taken to the dedicated secure score page, where you'll see the score broken down by subscription. Select a single subscription to see the detailed list of prioritized recommendations and the potential effect that remediating them will have on the subscription's score.
17+
Defender for Cloud displays your score prominently in the portal. When you select the Secure score tile on the overview page, you're taken to the dedicated secure score page, where you'll see the score broken down by subscription. Select a single subscription to see the detailed list of prioritized recommendations and the potential effect that remediating them will have on the subscription's score.
1818

1919
Your secure score is shown in the following locations in Defender for Cloud's portal pages.
2020

@@ -29,7 +29,7 @@ Your secure score is shown in the following locations in Defender for Cloud's po
2929
:::image type="content" source="./media/secure-score-security-controls/secure-score-management-groups.png" alt-text="The secure score for management groups on Defender for Cloud's secure score page":::
3030

3131
> [!NOTE]
32-
> Any management groups for which you don't have sufficient permissions, will show their score as “Restricted.”
32+
> Any management groups for which you don't have sufficient permissions, will show their score as “Restricted.”
3333
3434
- At the top of the **Recommendations** page:
3535

@@ -41,7 +41,7 @@ You can access your score via the secure score API. The API methods provide the
4141

4242
![Retrieving a single secure score via the API.](media/secure-score-security-controls/single-secure-score-via-api.png)
4343

44-
For examples of tools built on top of the secure score API, see [the secure score area of our GitHub community](https://github.com/Azure/Azure-Security-Center/tree/master/Secure%20Score).
44+
For examples of tools built on top of the secure score API, see [the secure score area of our GitHub community](https://github.com/Azure/Azure-Security-Center/tree/master/Secure%20Score).
4545

4646
## Get your secure score from Azure Resource Graph
4747

@@ -55,7 +55,7 @@ To access the secure score for multiple subscriptions with Azure Resource Graph:
5555

5656
1. Enter your Kusto query (using the following examples for guidance).
5757

58-
- This query returns the subscription ID, the current score in points and as a percentage, and the maximum score for the subscription.
58+
- This query returns the subscription ID, the current score in points and as a percentage, and the maximum score for the subscription.
5959

6060
```kusto
6161
SecurityResources
@@ -64,7 +64,7 @@ To access the secure score for multiple subscriptions with Azure Resource Graph:
6464
| project subscriptionId, current, max, percentage = ((current / max)*100)
6565
```
6666
67-
- This query returns the status of all the security controls. For each control, you'll get the number of unhealthy resources, the current score, and the maximum score.
67+
- This query returns the status of all the security controls. For each control, you'll get the number of unhealthy resources, the current score, and the maximum score.
6868
6969
```kusto
7070
SecurityResources
@@ -75,7 +75,6 @@ To access the secure score for multiple subscriptions with Azure Resource Graph:
7575
7676
1. Select **Run query**.
7777
78-
7978
## Tracking your secure score over time
8079
8180
### Secure Score Over Time report in workbooks page
@@ -99,7 +98,6 @@ The dashboard contains the following two reports to help you analyze your securi
9998
10099
:::image type="content" source="./media/secure-score-security-controls/power-bi-secure-score-dashboard.png" alt-text="The optional Secure Score Over Time Power BI dashboard for tracking your secure score over time and investigating changes.":::
101100
102-
103101
## Next steps
104102
105103
This article described how to access and track your secure score. For related material, see the following articles:

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

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,6 @@ This article details the changes made to the SQL vulnerability assessment servic
4646
|VA1220 |Database communication using TDS should be protected through TLS |Logic change |
4747
|VA2108 |Minimal set of principals should be members of fixed high impact database roles |Logic change |
4848

49-
5049
## December 2020
5150

5251
|Rule ID |Rule Title |Change details |

articles/defender-for-cloud/support-matrix-cloud-environment.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,6 @@ This article indicates which Defender for Cloud features are supported in Azure
1313

1414
In the support table, **NA** indicates that the feature isn't available.
1515

16-
1716
|**Feature/Plan** | **Azure** | **Azure Government** | **Microsoft Azure operated by 21Vianet**|
1817
|--- | --- | --- | --- |
1918
|**GENERAL FEATURES** | | ||

0 commit comments

Comments
 (0)