The following table outlines the exclusions needed for running ENS/VSE on an Oracle Database server.
|
Oracle Exclusions Needed
|
Comments
|
Example |
|
Data files
|
Data files generally have a .dbf extension. |
....\oracle\oradata\*.dbf
|
|
Redo files
|
Redo files have a .log extension.
NOTE: Redo logs exist if you use the Oracle Development toolkit or backup and recovery.
|
....\oracle\Inventory\logs\*.log |
|
Control files
|
Control files have a .ctl extension. |
....\oracle\oradata\*.ctl |
NOTES:
- It is not advised to exclude entire directories such as the Oracle Database directory and subdirectories from the scans. The reason is because it poses a potential high security risk.
- If you are in a clustered environment, you might need to consider rules for the Port Blocking section of Access Protection.
How to configure exclusions in ENS/VSE:
When configuring exclusions, always apply the principle that the more precise the exclusion, the smaller the potential security risk. For instructions to configure exclusions, see the following documentation:
- ENS: "Preventing Threat Prevention from blocking trusted programs, networks, and services" section of the Endpoint Security Product Guide
- VSE:
- KB66909 - Endpoint Security/VirusScan Enterprise exclusion articles
- KB55898 - Understanding VirusScan Enterprise Exclusions
- KB67544 - How to create low-risk and high-risk process exclusions for VirusScan Enterprise 8.x in ePolicy Orchestrator
- KB50998 - How to manage file and folder exclusions using wildcards
- KB61000 - VirusScan Enterprise exclusions and hardware paths (physical address versus logical address)
