Policy Management

When using Glasswall's Embedded Engine, you have the option to set your own sanitisation preferences by changing the policy settings for each of the supported file types.

This means you can shape your organisation’s security policy in accordance to its risk tolerance.

Policy settings

The following policy settings can be applied to active content:

• Sanitise: as a general rule, we'll analyse the file and remove this type of risky content, then rebuild the file. See Embedded Files and Embedded Images for exceptions.

  • Example: you can sanitise (remove) macros from Word files.

• Allow: we'll analyse and rebuild the file, but we won't remove this type of risky active content.

  • Example: you can allow macros for Word files. (This presents a risk to you if an attacker has placed malware within a file.)

• Disallow: we'll analyse the file, but if we find risky content, we won't process the file at all.

  • Example: you can specify that Word files with macros aren't processed at all.

The content management types currently available for each format are depicted in the table below:

[ *]: Content management switch available in Editor's "enableRebuild" (default) mode or Rebuild only

All content types not represented by a content management type for a specific file format will be automatically remediated by the Glasswall engine if identified as malicious.

Embedded Files

The "Embedded Files" content management type applies only to non-image file formats which are either unsupported by the Glasswall engine or obfuscated by the containing file. For MS Office formats, embedded files in supported formats are processed as a standalone file and if the embedded supported file is conforming it will be regenerated regardless of content management settings, otherwise the containing file will be rejected.

• Sanitise: for MS Office formats, embedded MS Office files are processed as standalone files. If the embedded file is conforming, the embedded file will be regenerated; otherwise, both the containing and embedded file will be rejected. For all other container or embedded formats, embedded files are removed without being processed.
• Disallow: embedded files are forbidden. If one is found, both the embedded and the containing file are rejected.
• Allow: for MS Office formats, embedded MS Office files are processed as standalone files. If one is non-conforming, both the embedded and the containing file are rejected. For all other container or embedded formats, embedded files are regenerated without being processed.

The table below shows which embedded file formats we attempt to regenerate (✓) when "Embedded Files" is set to "Sanitise" versus those which are removed (✗):

[†]: Disallowed by container format

[‡]: Not removed by Embedded Files switch, but may be removed by All Actions switch. Embedded file is regenerated without being processed.

Embedded Images

For image file formats, the "Embedded Images" content management switch should be used. This has the following behaviour depending on switch setting:

• Sanitise: for MS Office, embedded images in supported formats are processed as standalone files. If the embedded image is conforming, the embedded file will be regenerated; otherwise, both the containing and embedded file will be rejected. Unsupported image formats are removed. In PDFs, embedded images are not processed and will always be regenerated if entry is structurally correct.
• Disallow: embedded images are forbidden. If one is found, the containing file is rejected.
• Allow: embedded images are not processed and are always regenerated as long as they are a supported file format.

The table below shows which image formats we attempt to regenerate (✓) when "Embedded Images" is set to "Sanitise" versus those which are removed (✗):

[⸸]: Will be converted to a different format by container file

Note: when the "Embedded Images" is set to "Disallow", any images being encountered will result in the rejection of the containing file. This includes thumbnails of the containing or embedded documents and so may supersede the "Embedded File" content management switch.

Macros

The macros content switch for MS Office files applies to both Microsoft Visual Basic for Applications (VBA) and Excel 4.0 macros.

Microsoft Visual Basic for Applications

VBA macros are written in the Visual Basic programming language and can be included in any MS Office file format. The handling of VBA macros can be configured as follows:

• Sanitise - VBA macros are removed from files.
• Disallow - VBA macros are forbidden. If one is found, the containing file is rejected.
• Allow - VBA macros are processed and regenerated as part of the containing file providing they conform to specification.

Excel 4.0 Macros

Excel 4.0 macros are a legacy feature included in XLSX and XLS files. XLSX files containing Excel 4.0 macros will be saved using the ".xlsm" file extension and will produce an error if this extension is modified. The handling of Excel 4.0 macros can be configured as follows:

• Sanitise: in XLS files, the file will be blocked and Excel 4.0 Macro found: Not supported reported as an issue item. In XLSX/XLSM files, sheets containing macros will be removed from the document and reported as a sanitisation item. If this causes the file to be malformed (i.e. reducing the number of visible sheets to zero), the file will be rejected and an appropriate issue item reported.
• Disallow: Excel 4.0 macros are forbidden. If one is found, the containing file is rejected.
• Allow: in XLS files, the file will be blocked and Excel 4.0 Macro found: Not supported reported as an issue item. In XLSX/XLSM files, the file will be regenerated with macros intact.