Skip to content

Commit 93fa501

Browse files
authored
Merge pull request #217700 from liorarviv/main
Updates to the rules creation page
2 parents 239a770 + 5e6e933 commit 93fa501

File tree

2 files changed

+23
-6
lines changed

2 files changed

+23
-6
lines changed

articles/defender-for-cloud/governance-rules.md

Lines changed: 23 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -28,10 +28,16 @@ You can then review the progress of the tasks by subscription, recommendation, o
2828
|Aspect|Details|
2929
|----|:----|
3030
|Release state:|Preview.<br>[!INCLUDE [Legalese](../../includes/defender-for-cloud-preview-legal-text.md)]|
31-
|Pricing:|Free while in preview and will be a paid service after preview|
31+
| Prerequisite: | Requires the [Defender Cloud Security Posture Management (CSPM) plan](concept-cloud-security-posture-management.md) to be enabled.|
3232
|Required roles and permissions:|Azure - **Contributor**, **Security Admin**, or **Owner** on the subscription<br>AWS, GCP – **Contributor**, **Security Admin**, or **Owner** on the connector|
3333
|Clouds:|:::image type="icon" source="./media/icons/yes-icon.png"::: Commercial clouds<br>:::image type="icon" source="./media/icons/no-icon.png"::: National (Azure Government, Azure China 21Vianet)<br>:::image type="icon" source="./media/icons/yes-icon.png"::: Connected AWS accounts<br>:::image type="icon" source="./media/icons/yes-icon.png"::: Connected GCP accounts|
3434

35+
> [!NOTE]
36+
> Starting January 1, 2023, governance capabilities will require Defender Cloud Security Posture Management (CSPM) plan enablement.
37+
> Customers deciding to keep Defender CSPM plan off on scopes with governance content:
38+
> - Existing assignments remain as is and continue to work with no customization option or ability to create new ones.
39+
> - Existing rules will remain as is but won’t trigger new assignments creation.
40+
3541
### Defining governance rules to automatically set the owner and due date of recommendations
3642

3743
Governance rules can identify resources that require remediation according to specific recommendations or severities, and the rule assigns an owner and due date to make sure the recommendations are handled. Many governance rules can apply to the same recommendations, so the rule with lower priority value is the one that assigns the owner and due date.
@@ -46,18 +52,23 @@ By default, email notifications are sent to the resource owners weekly to provid
4652

4753
To define a governance rule that assigns an owner and due date:
4854

49-
1. In the **Environment settings**, select the Azure subscription, AWS account, or Google project that you want to define the rule for.
50-
1. In **Governance rules (preview)**, select **Add rule**.
55+
1. Navigate to **Environment settings** > **Governance rules**.
56+
57+
1. Select **Create governance rule**.
58+
5159
1. Enter a name for the rule.
52-
1. Set a priority for the rule. You can see the priority for the existing rules in the list of governance rules.
60+
1. Select a scope to apply the rule to and use exclusions if needed. Rules for management scope (Azure management groups, AWS master accounts, GCP organizations) are applied prior to the rules on a single scope.
61+
62+
1. Priority is assigned automatically after scope selection. You can override this field if needed.
63+
5364
1. Select the recommendations that the rule applies to, either:
5465
- **By severity** - The rule assigns the owner and due date to any recommendation in the subscription that doesn't already have them assigned.
55-
- **By name** - Select the specific recommendations that the rule applies to.
66+
- **By specific recommendations** - Select the specific recommendations that the rule applies to.
5667
1. Set the owner to assign to the recommendations either:
5768
- **By resource tag** - Enter the resource tag on your resources that defines the resource owner.
5869
- **By email address** - Enter the email address of the owner to assign to the recommendations.
5970
1. Set the **remediation timeframe**, which is the time between when the resources are identified to require remediation and the time that the remediation is due.
60-
1. If you don't want the resources to affect your secure score until they're overdue, select **Apply grace period**.
71+
1. If you don't want the resources to impact your secure score until they're overdue, select **Apply grace period**.
6172
1. If you don't want either the owner or the owner's manager to receive weekly emails, clear the notification options.
6273
1. Select **Create**.
6374

@@ -69,6 +80,12 @@ If there are existing recommendations that match the definition of the governanc
6980
> [!NOTE]
7081
> When you delete or disable a rule, all existing assignments and notifications will remain.
7182
83+
> [!TIP]
84+
> Here are some sample use-cases for the at-scale experience:
85+
> - View and manage all governance rules effective in the organization using a single page.
86+
> - Create and apply rules on multiple scopes at once using management scopes cross cloud.
87+
> - Check effective rules on selected scope using the scope filter.
88+
7289
## Manually assigning owners and due dates for recommendation remediation
7390

7491
For every resource affected by a recommendation, you can assign an owner and a due date so that you know who needs to implement the security changes to improve your security posture and when they're expected to do it by. You can also apply a grace period so that the resources that are given a due date don't impact your secure score unless they become overdue.
55.7 KB
Loading

0 commit comments

Comments
 (0)