Skip to main content

Exception Policy Settings

[Policy] > [Basic Decontamination Policy] > Setting [Exceptions]​

Among the decontamination policies of the SHIELDEX File,'Exception' settingis an item that allows for bypassing general security policies or defining exceptions in specific situations.
Exception settings allow for detailed control over the sanitization of documents or the import of originals based on file extensions and conditions.

⚠️ The basic declassification policy setting authority is granted to [Administrator Type - Super Administrator], and
Administrator permission settings can be done in [Administrator] > [Administrator List].

Detailed Description of Settings Items​

Policy NameExplanation
Harmless Extension Allowlist FilterEnter the extensions allowed for harmless processing, separated by semicolons. Extensions not included here will be classified as unsupported extensions and processed according to the 'Unsupported Extension Blocking Settings' in the [Common] tab. If no value is entered, harmless processing will be allowed for all extensions. Example input) docx;xlsx;
Harmlessness Block Extension FilterSpecify the extensions to block the import itself, regardless of decontamination, separated by semicolons. Example input) exe;bat;cmd;
Non-decontamination Excluded Extension FilterSpecify the file extensions to be imported in their original state without decontamination, separated by semicolons. Input example) txt;csv;
Exception settings for blocking unsupported file extensions[Common] Tab > Among the unsupported extensions blocked by 'Unsupported Extension Block Settings', the extensions specified as exceptions in this item allow for original imports. Input example) log;tmp;
Unsupported File Binary Exception SettingsFiles blocked by unsupported extension blocking will be treated as exceptions if they match a specific binary pattern and extension. Input format: file signature (hex), starting position (offset), comparison length (size), extension (ext). Example input) BO F0 30 ED,0,4,ofc;
Exception settings for blocking extension forgery[Common] Tab > Among the tampered files blocked by 'Extension Tampering Prevention Settings', the extensions specified as exceptions in this item allow the import of originals. (Input method: extension name) Input example) pdf;docx;
Original Import Settings When Threat Elements Are Not DetectedSet the handling of documents that do not contain threats such as OLE objects, macros, scripts, and ActiveX. Documents without threats can be imported in their original state, preserving the format and content of the document.

Input Rules and Precautions​

  • The extension input must be**Separated by semicolons (;)**must be done, and enter without spaces.
  • 'Extension Spoofing Prevention Exception Settings' was previously done using the MIME type input method, butChange to extension name input methodIt has been done. If you have previously registered a MIME type, it needs to be reset with the extension name.
  • 'Unsupported file binary exception setting' only allows exceptions when the actual binary signature matches, even for unsupported extensions, thereby reducing the risk of extension forgery.

Reference Note​

  • 'File extension unspecified block setting', 'Original import setting in case of decontamination error', 'Original import setting in case of timeout', 'Timeout criteria setting' items are configured in the [Common] tab.
  • After the policy change, you can check the change history in [Policy Change History], and if necessary, you can also restore the policy.