Rule configurations are inherited from the root level by default. With OU Compatible Security Policy, you can choose to make changes at the leaf OU level(s) that override the root level configurations.
The following use case examples are some of the most common policy rules that you might want to configure:
- Overriding a root level policy rule at the leaf level
You can create a root level policy rule to notify users when a phishing attack occurs on their device, which will apply to your whole organization. However, you may want to override this for one specific leaf OU level (for example, one that represents an office in a particular country) by creating a policy override for that leaf OU level.
You can override a configuration by making changes directly, or alternatively, you can select Override at the leaf OU level.
To revert any overridden changes back to the root level policy, change the setting back to Inherit.
Note:If you select Override but don't make any changes, you must click Inherit to continue to inherit the policy from the root level
- Overriding the severity level for a specific leaf level
By increasing the threat severity level, a certain business app (WPA) might start being blocked according to the required maximum device risk level if you are using Signal UEM to apply Conditional Access policies. By doing so at the leaf level, you are differentiating the behavior within your organization.