The Scan Exclusions setting is a feature that does not scan specific folders, files, or extensions specified by the administrator when performing a V3 scan on the agent PC. Provides instructions for setting inspection exceptions.
(1) Logging in to the APC Administration Console
(2) [Management] - [Policy] - [V3 Policies] - [System Security] - [Scan Exclusions]
- Apply the scan exclusion list configured in the agents : Apply the scan exclusion according to the Scan Exclusions settings set by the user on the agent.
- Apply the scan exclusion list configured in Policy Server: Applies the scan exceptions set by the APC, regardless of the agent user's inspection exceptions settings.
Select 'Apply the scan exclusion list configured in Policy Server' to apply the inspection exception based on the settings of the APC administrator.
(3) Scan Exclusions Target Settings : Add folders/files/extensions that you do not want to scan.
- You can select an absolute path, the Winodows Program Files folder, and the Windows folder.
- The file name must be in the same format as 'Drive name:\folder name\file name' or 'Environmental variable\folder name\file name'.
- The extension can be up to 260 characters in length. (English characters)
- Separate them with '/' when setting up more than one extension (for example, bmp/gif/txt).
- \ : * ? " . > | cannot be used for extensions, and executable files such as exe, dll, or ox cannot be entered as inspection exception extensions.)
(4) Scan Exclusions Threats Settings: Settings for excluding inspection of known malicious codes
(When applying this setting, the registered malware will be excluded from the inspection, so please use it only when necessary.)
- In the Scan Exclusions Threats Settings, type the malware name in "Malware Exclusions Settings" that appears when you click Add.
- The malware name must be the same as the name diagnosed in V3. Enter the name of the malware, click OK, and make sure that the name of the malware you entered is registered in the list.
Scan Exclusions settings can increase attacks on systems and expose them to security threats.
It is not recommended to set the test exception without thoroughly testing and validation.