03 · CDS

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.

  1. Internet networkExternal filesDocuments · archives · scripts from mail · web · USB
  2. PassedExisting CDSImport checkAntivirus · partial sandbox · CDRNew malicious docs pass
  3. CDS storageTo business networkFiles that pass move to the internal network
  4. 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
ZX PLATFORM analysis server (external network · DMZ)
1. Pre-filterReputation · signatures · YARA
2. Hyper SandboxSub-second behavior analysis · AI verdict
3. ZX CDRThreat removal · rebuild
Response: verdict (risk 0–10) + report.json + disarmed file
Business network (internal)
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.

  1. 01 · SUBMITFile submissionFiles requested for import sent via API (incl. archives · nested documents)
  2. 02 · KNOWNPre-filterKnown threats judged instantly by reputation · signatures · YARA
  3. 03 · UNKNOWNHyper SandboxReal execution · behavior observation · AI risk score 0–10
  4. 04 · DISARMZX CDRThreats removed and file rebuilt per policy
  5. 05 · RESPONSEResult returnedVerdict · report.json · disarmed file returned
VerdictRiskMeaningCDS handling (recommended)
CRITICAL · HIGH8 ~ 10Malicious behavior detected (incl. possible false-positive points)Block import · quarantine · notify admin
MEDIUM4 ~ 7Suspicious; deeper analysis neededImport after CDR disarm, or hold approval
LOW · BENIGN0 ~ 3Clean, or only meaningful logsImport original or disarmed copy per policy
Unsupported · error—Unsupported format, analysis timeoutFail-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.

  1. 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
  2. 02

    Broad format support, incl. HWP · HWPX

    87+13 categories

    • Office · Hangul · PDF · RTF · OneNote
    • LNK · Visio/XPS · ODF · images
    • HTML/SVG · CSV/TSV
  3. 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
  4. 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

Building a cross-domain solution?

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

Frequently asked questions

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.

Are outgoing files inspected too?

Yes. Outbound inspection uses the same REST API.

Other layers can join the same analysis server

Let's decide together where to start

Tell us about your current infrastructure and we'll propose an integration approach.
Talk to sales