Skip to content

Commit 942ff25

Browse files
Merge pull request #224632 from liorarviv/main
Update governance-rules.md
2 parents 3436ea3 + 2264337 commit 942ff25

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -90,6 +90,10 @@ If there are existing recommendations that match the definition of the governanc
9090
> - Create and apply rules on multiple scopes at once using management scopes cross cloud.
9191
> - Check effective rules on selected scope using the scope filter.
9292
93+
To view the effect rules on specific scope, use the “scope” filter and select a desired scope.
94+
95+
Conflicting rules are applied in priority order. For example, rules on a management scope, (Azure management groups, AWS master accents and GCP organizations) take effect before rules on scopes (for example, Azure subscriptions, AWS accounts, or GCP projects).
96+
9397
## Manually assigning owners and due dates for recommendation remediation
9498

9599
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

Comments
 (0)