This article applies to all MetaDefender Core releases deployed on Windows and Linux systems.
Summary:
This article explains how MetaDefender Core handles recursive processing and reporting when Content Disarm and Reconstruction (CDR) is enabled. It clarifies how embedded or internal files within a processed file are processed and displayed in the scan history.
Issue
During a CDR-enabled process, a file may contain other embedded or internal objects (for example, documents within archives, or images containing embedded files). It may be unclear whether these extracted components are also processed by CDR and whether the results are shown in the scan report.
Cause
While CDR can reconstruct and sanitize embedded content, recursive sanitization and detailed reporting depend on configuration settings and supported file types. If certain options are disabled, internal or embedded files may not be sanitized or reported individually.
Resolution
To ensure that embedded or internal files are recursively processed and reported during CDR processing:
- Enable Recursive Scanning for Embedded File Types Verify that recursion of embedded file types is enabled in the configuration. This allows CDR to sanitize internal files..
- Enable Detailed Sanitization Reporting Turn on the “Include Sanitisation Details / Processed Objects” option. This ensures that the scan history includes detailed information about the sanitization actions and results of internal components.
- Confirm Supported File Types Make sure the file types being processed support recursive scanning and sanitization. Some formats may not support deep recursion or detailed reporting. If a file type is not supported, CDR will act based on the “Remove embedded object” configuration to decide whether to remove the embedded file or not
When all of these settings are correctly configured, the CDR process will:
- Recursively scan embedded or internal files.
- Include the results and sanitization details of those components in the scan history report.
If Further Assistance is required, please proceed to log a support case or chatting with our support engineer.
