Cross-domain (CDS)Imported files are the path into your internal network
Benefit
Every imported file judged in real time, in under 1 second · only clean or disarmed files reach the business network · disarm even HWP · HWPX
Overview
A separated internal network has no internet, so antivirus updates lag and cloud analysis is unavailable. Threats not stopped at import are hard to stop inside. Your cross-domain solution sends each file over REST API before import; Hyper Sandbox judges it and ZX CDR returns a copy with only the threats removed.
Integration
Cross-domain solution REST APIInbound · outbound inspectionDeployed on external network or DMZOn-premises
Technology
The problem with existing solutions
Existing cross-domain import checks rely on antivirus, partial sandboxing and CDR, so they miss new malicious documents. Files that pass move on to the business network and infect the PC the moment they are opened.
Internet networkExternal filesDocuments · archives · scripts from mail · web · USB
CDS storageTo business networkFiles that pass move to the internal network
Business PCInternal infectionRuns the moment the document is opened inside
Legacy sandboxes are slow and easy to evade
Legacy sandboxes take 60+ seconds per file, so they only check suspicious files after the fact and are weak against evasion. ZX judges every file in real time, in under 1 second, and disarms even HWP · HWPX.
Conventional sandboxVS ZX PLATFORM
60+ s per file; bottlenecks under load
Analysis time
Under 1 s (average per file)
Only selected suspicious files, checked afterwards
Operation
Every file judged in real time
Vulnerable to VM detection · delayed execution · user-interaction tricks
Evasion
Agentless hypervisor; environment changes on every run
Cannot reproduce the OS · app versions of company PCs
Environment
Behavior observed across multiple OS · app versions
OS · Office licenses for analysis, high-end servers
Infrastructure
$0 in licenses, from a standard 4-core server
Many overseas CDRs do not support HWP
Korean documents
CDR disarm for 87 extensions incl. HWP · HWPX
* Legacy sandbox items summarize common limitations and may vary by product and version.
The ZX solution
Cross-domain integration
ZX PLATFORM sits on the external network or DMZ; your cross-domain solution sends files over REST API before import. It receives the verdict and disarmed file, and passes only clean or disarmed files to the business network.
Internet network
User PC · mail · webFiles requested for import
↓
Cross-domain solution · externalImport approval · inspection · transfer
REST API→File submission
ZX PLATFORM analysis server (external network · DMZ)
1. Pre-filterReputation · signatures · YARA
2. Hyper SandboxSub-second behavior analysis · AI verdict
CDS storage · internalOnly clean or disarmed files imported
↓
Business PCMalicious files blocked · admin notified
Deployment principle ZX PLATFORM sits on the external network or DMZ and is called before import. No analysis server runs inside, so your network separation policy is unaffected. Outbound inspection uses the same API.
Import analysis flow and handling by verdict
Submitted files pass through pre-filter → Hyper Sandbox → ZX CDR and come back with a verdict. Based on the 0–10 risk score, your policy decides: block, import after disarm, or import the original.
01 · SUBMITFile submissionFiles requested for import sent via API (incl. archives · nested documents)
04 · DISARMZX CDRThreats removed and file rebuilt per policy
05 · RESPONSEResult returnedVerdict · report.json · disarmed file returned
Verdict
Risk
Meaning
CDS handling (recommended)
CRITICAL · HIGH
8 ~ 10
Malicious behavior detected (incl. possible false-positive points)
Block import · quarantine · notify admin
MEDIUM
4 ~ 7
Suspicious; deeper analysis needed
Import after CDR disarm, or hold approval
LOW · BENIGN
0 ~ 3
Clean, or only meaningful logs
Import original or disarmed copy per policy
Unsupported · error
—
Unsupported format, analysis timeout
Fail-safe: use existing check result · log it
Handling rules are set in your cross-domain solution's policy engine. Risk scale: based on the ZX-Core technical specification v1.4 · 6.1 classification.
ZX CDR: removes only the threats, keeps the document intact
It reads the document structure, removes only the threats, and handles 87+ formats including HWP · HWPX. It unpacks archives and documents within documents all the way down, and passes unsupported formats through as-is instead of deleting them.
01
Structure-based judgment
Identifies formats by their actual signatures, not extensions
Never converts whole documents to images or PDF
Removes only the elements that lead to threats
02
Broad format support, incl. HWP · HWPX
87+13 categories
Office · Hangul · PDF · RTF · OneNote
LNK · Visio/XPS · ODF · images
HTML/SVG · CSV/TSV
03
Recursive archive and nesting handling
19+archive formats
Archives within archives, all the way down
Documents within documents, all the way down
Built-in zip bomb protection
04
Safe failure · cross-verification
Unsupported formats are delivered as originals, not stripped
Work never stops
Disarmed files are re-analyzed in Hyper Sandbox to confirm
LINEUP
How the cross-domain (CDS) segment is configured
01ZX HUBIntegrated analysis server · 3-stage engineREST API integration · judged before import · only clean or disarmed files reach the business network
Add high-performance sandboxing and CDR to your product with REST API integration alone, no in-house development. Your customers stop new threats at the cross-domain boundary and precisely disarm even HWP documents.
Integration
REST API, no product changes
Supply model
ZX PLATFORM server bundle · analysis engine SDK license
The six questions we hear most before adoption. Answers on where the analysis server sits, integration method, import speed, HWP disarm, handling by verdict and outbound inspection.
Does the analysis server have to sit on the internal network?
No. Place it on the external network or DMZ and call it before import. With no analysis server on the internal network, your network separation policy is unaffected.
How does it integrate with our cross-domain solution?
Via REST API, with no changes to the product. Send a file before import and get back the verdict, report.json and the disarmed file.
Won't imports slow down?
Every imported file is judged in real time in under 1 s (average per file). It doesn't pick out only suspicious files for after-the-fact inspection.
Can HWP documents be disarmed too?
Yes. It disarms 87 file extensions including HWP · HWPX. It removes only the threats and delivers unsupported formats as the original without removing anything.
How are files handled by verdict?
Based on a risk score of 0–10, the cross-domain solution's policy engine decides whether to block, import after disarm or import the original. Malicious files are blocked and administrators are notified.