
Our Technology
Proactive Neutralization
YazamTech's Content Disarm and Reconstruction (CDR) technology operates on a fundamental zero-trust methodology. Each original file and email undergo a systematic process: it is compared to the standard, meticulously deconstructed, and every component is analyzed at a granular level. A new, safe file is precisely reconstructed to its legitimate specifications, as similar to the original as possible. This advanced process effectively eliminates potential threats embedded within the original file's structure, ensuring maximum safety.
The Yazam Advantage: Inherent File Safety
-
Proactive Threat Neutralization.
-
Unrivalled File Formats Coverage.
-
Files and Emails protection at Every Possible Entrance.
-
Flexible & Customizable Policy Management.
Yazam Engine
The Intelligent Core
The Yazam proprietary filtering Engine, in-house development by YazamTech, based on CDR technology, is a collection of many dedicated engines that work as focused processing units, which are engineered to identify and neutralize sophisticated threats across an unparalleled spectrum of more than 200 file types belonging to a wide range of family formats: ● Adobe Acrobat (PDF) ● Microsoft Word ● Microsoft Excel ● Microsoft PowerPoint ● Microsoft Visio ● OASIS OpenDocument ● Plain Text ● Image ● Audio ● Video ● Messages ● Extensible Markup (XML) ● Hyper Text Markup (HTML) ● JavaScript Object Notation (JSON) ● Archives ● Macros ● Scripts ● Shortcuts ● Certificate Revocation List ● DICOM ● Bioinformatics ● CAD-CAM ● and more.
Proactive File Sanitization
Each file and email are meticulously deconstructed, analyzed at a granular level, and then a new, safe file or email is precisely reconstructed to its original, legitimate specifications. This advanced process effectively eliminates potential threats embedded within the file and email's structure, ensuring maximum safety.
Yazam Policy
Precise File Control
The Yazam Engine acts as defined by the filtering rules for each file type and its content.
The Yazam Policy is a comprehensive collection of many hundreds of rules that outline the allowed and forbidden file types, which embedded objects and content are permitted or forbidden, and which action should be taken if potentially malicious content is detected.
Yazam History
The Yazam solutions record the filtering findings and the actions taken in the Yazam History, and also move the quarantined files to this location.
The Yazam History records are stored in a range of SQL databases, including SQLite, PostgreSQL, Microsoft SQL Server (also local DB), and Azure SQL. The Yazam authorized administrators manage the Yazam History application.
Yazam Log
Each Yazam Engine records the filtering findings and the actions taken for each filtered file in the Yazam History Database.
Each filtering record contains relevant Information, such as the Yazam client type, filtering status, user name, computer name, sender address, recipient address, filtering duration, and the file ID.
Yazam Quarantine
Each Yazam Engine moves the quarantined files into the Yazam History DB. Extracting quarantined files, which may be malicious, from the Yazam History DB is possible only by authorized Yazam administrators.
Yazam Reports
Reports are the way by which authorized administrators receive practical outputs about the filtering findings and actions that have been taken.
Administrators can request that Yazam History issue manual reports for investigation, or predefine reports to be sent automatically and periodically.
Yazam URL
The Yazam Engine features a dedicated filter for Shortcuts that exist in various file types, such as PDF, Microsoft Office (Word, Excel, PowerPoint, Visio), HTML, XML, and Plain Text.
Part of the Shortcuts filter looks for malicious URLs in the files. It is achieved by utilizing the Yazam URL cloud service operated by YazamTech, which includes an updated database of hundreds of thousands of hostile URLs that is updated hourly.

Yazam Clients
Deployment Modules
These modules seamlessly integrate Yazam Engines into your diverse operational environments:









