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
|Required roles and permissions:|Azure - **Contributor**, **Security Admin**, or **Owner** on the subscription<br>AWS, GCP – **Contributor**, **Security Admin**, or **Owner** on the connector|
> 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
+
35
41
### Defining governance rules to automatically set the owner and due date of recommendations
36
42
37
43
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,19 @@ By default, email notifications are sent to the resource owners weekly to provid
46
52
47
53
To define a governance rule that assigns an owner and due date:
48
54
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. In the **Environment settings**, select **Governance rules**.
56
+
1. In **Governance rules**, select **Create governance rule**.
51
57
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.
58
+
1. Select a scope to apply the rule and use the exclusions if needed. Rules on management scope (Azure management groups, AWS master accounts, GCP organizations) are being applyed before rules on single scope.
59
+
1. Priority is being assigned automatically after scope selection. You can override this field if needed.
53
60
1. Select the recommendations that the rule applies to, either:
54
61
-**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.
62
+
-**By specific recommendations** - Select the specific recommendations that the rule applies to.
56
63
1. Set the owner to assign to the recommendations either:
57
64
-**By resource tag** - Enter the resource tag on your resources that defines the resource owner.
58
65
-**By email address** - Enter the email address of the owner to assign to the recommendations.
59
66
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**.
67
+
1. If you don't want the resources to impact your secure score until they're overdue, select **Apply grace period**.
61
68
1. If you don't want either the owner or the owner's manager to receive weekly emails, clear the notification options.
62
69
1. Select **Create**.
63
70
@@ -69,6 +76,12 @@ If there are existing recommendations that match the definition of the governanc
69
76
> [!NOTE]
70
77
> When you delete or disable a rule, all existing assignments and notifications will remain.
71
78
79
+
> [!TIP]
80
+
> Use-cases for the at-scale experience
81
+
> - View and manage all governance rules effective in the organization using a single page.
82
+
> - Create and apply rules on multiple scopes at once using management scopes cross cloud.
83
+
> - Check effective rules on selected scope using the scope filter.
84
+
72
85
## Manually assigning owners and due dates for recommendation remediation
73
86
74
87
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.
0 commit comments