A sanitized file is a file which has been gone through a process to strip any embedded objects and exploits while preserving the usability of a file. The sanitized file will still have the format and file extension of the original file (unless its been explicitly set up to be converted to another type of file). For example, a sanitized PDF will still contain the PDF format, contain the .PDF extension, and be accessible by a PDF reader.
Some of the actions performed as part of santization can include:
Removing all attachments and document action
Removing all annotations
Removing java script
Making the form fields present in PDF file un-editable/in-accessible so that the user cannot update the values
Recent versions of MetaDefender Core v3 allow administrators to create sanitization processes as part of the file type conversion process. For more information refer to the user manual:
For MetaDefender Core v3, read about it in the Online MetaDefender Core v3 Documentation
at Configuring MetaDefender Core v3 > Workflow Profile Configuration -> Creating a New Workflow Profile
MetaDefender Core v3 supports file type sanitization for many of the most common types of document files. If you have a request for a file type that we do not support, log a ticket with us on the OPSWAT portal to let us know. Though we cannot make any commitments as to when we will add support, we are always looking to add new file types that are commonly used by our customers.
This article pertains to MetaDefender Core v3
This article was last updated on 2017-12-21