Product launch

Glasswall Genesis: the new CDR engine, memory-safe and up to 2x faster.

Insights About Docs

Book a demo

Partners Insights About Docs

Book a demo

English Bahasa Indonesia 日本語 한국어 Bahasa Melayu ไทย Tiếng Việt 简体中文繁體中文

What is CDR?

Content Disarm & Reconstruction

Detection misses what it has never seen. Content Disarm and Reconstruction takes a Zero Trust, prevention-first approach: rather than trying to spot malware, it removes active content and rebuilds every file into a safe, usable version before it reaches a user, neutralising file-based malware and ransomware without needing to predict attacker behaviour. CDR is the deterministic core of Glasswall's file security engine, delivered and supported by Safeware across APAC.

The evidence

100%

of malicious files neutralised across 8.27M tested (Glasswall)

42%

of ransomware began with a malicious file or link (Glasswall)

1 in 6

malicious files evade sandboxing: 1 in 8 for antivirus (Glasswall)

The Problem

Every file entering your organisation introduces risk

Glasswall reports that 42% of ransomware incidents began with a malicious file or link, and one in three data breaches begins with a malicious file. Regulated APAC organisations, banks under MAS oversight, government agencies, hospitals handling patient data, need a preventive control at the file boundary, not only detection after the fact.

Antivirus, sandboxing, and EDR all share one assumption: that a threat can be recognised. They detect known and observable threats, but they cannot vouch for an unknown file before it crosses a trust boundary. Glasswall CDR can. It validates the file against its format specification, removes anything non-conformant, macros, scripts, embedded objects, and rebuilds a clean copy that still opens and works.

How CDR Works

Every file rebuilt to a known-good standard

01

Inspect

Parse the file against its format specification, mapping every element, embedded object, and piece of active content.
02

Remediate

Remove macros, embedded scripts, OLE objects, and any structure that does not conform to the file specification.
03

Rebuild

Reconstruct the file from conformant elements to a known-good template. The rebuilt document keeps its content and formatting; active code is removed unless policy explicitly allows it.
04

Deliver

Return the rebuilt file to the original workflow, email, portal, repository, with a Glasswall remediation report recording each item removed and the policy applied.

Glasswall's patented four-step CDR runs the same way every time: same input, same policy, same output. The file is never executed, so there is nothing to evade. Each file produces a per-file remediation record, what was removed and against which policy, that audit and SOC teams can retain as evidence.

Worked examples

What a rebuild looks like on real files

Three files through the same policy, and the record each one leaves behind.

Q3-board-pack.pdf

Rebuilt

Two non-conforming structures found and repaired against the PDF specification.

supplier-invoice.xlsx

Macros removed by policy

The workbook arrives intact; the macro project does not survive the rebuild.

tender-response.docx

Two broken structures repaired

Malformed structures corrected, so the document opens cleanly downstream.

Glasswall CDR removes the risk of malware by rebuilding each file to a known-good standard

Technical documentation

For technical specifications, the full supported-file-type list, and API references, visit Glasswall directly: product documentation.

Book a Demo

See Glasswall CDR run against your own file workflows

Safeware delivers and supports Glasswall CDR across APAC: architecture, deployment, integration and ongoing support. Book a demo to see CDR applied to your own email, upload and transfer workflows.