The following table outlines the exclusions required for running ENS/VSE on an Oracle Database server.
|
Oracle Required Exclusions
|
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 will exist if the Oracle Development toolkit or backup and recovery are used.
|
....\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 scanning because this poses a potential high security risk.
- If you are in a clustered environment, you might need to consider additional 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, refer to the following documentation:
- ENS: "Configuring exclusions" section of the Endpoint Security 10.5 Product Guide (PD26799)
- VSE:
- KB66909 - Consolidated list of 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 in VirusScan Enterprise 8.x using wildcards
- KB61000 - VirusScan Enterprise exclusions and hardware paths (physical address versus logical address)
