HES provides centralized management for scan exceptions in both inbound and outbound protection.
This article answers the Frequently Asked Questions (FAQs) about scan exceptions if your legacy scan exception settings configured by policy conflict with each other.
This means you have configured different “scan exception” actions in different policies.
For example, policy A and policy B are configured for the same scan exception but with different actions, policy A’s action is “Reject the messages”, and policy B’s action is “Bypass this rule”, then the scan exception settings of the two policies “conflict” with each other.
Clicking the Initialize button resets the scan exception settings to default. This allows you to customize actions for each scan exception, which means more actions are provided than the previous policy-based scan exception settings, and your scan exception settings apply to all you managed domains.
The previous policy-based scan exception settings will still take effect, but you cannot update the settings any more. For newly added policies, you cannot customize “scan exception” actions, and HES will use the default action “Reject the messages” for the new policies.
New centralized management for scan exceptions provides more options for configuration. It is recommended that you initialize your legacy settings and customize scan exception settings for inbound and outbound protection.