Under certain circumstances, you
may want to prevent
IMSVA from scanning
certain types of messages that could be part of a DoS attack. For example,
messages with extremely large attachments require significant
IMSVA server
resources to scan fully. Additionally, messages addressed to hundreds
of recipients are most likely spam or some type of attack.
Rather than consuming IMSVA resources
to scan these types of messages, set scan exceptions to bypass scanning
and instruct IMSVA to
take action on the messages immediately.
 |
WARNING
-
For the actions specified in Scan
Exceptions to take effect, verify that the Global antivirus rule
is enabled.
-
For malformed messages, when a message triggers the scan exception, IMSVA stops scanning
and takes the corresponding actions. That means IMSVA will not
trigger any policy rules when a scan exception occurs.
For security setting violations and encryption
exceptions, IMSVA will not
stop scanning after the action of the scan exception executes. IMSVA continues
checking other policy rules. IMSVA will stop
scanning if it encounters a terminal scan action.
|
