Network securityConnect an ultra-fast sandbox analysis engine to your firewall
Benefit
Keep your equipment, just add an analysis layer · $0 analysis licenses · from a 4-core server, no transfer delay
Overview
NGFW · UTM · SWG · NDR inspect by signature and reputation, so new, never-seen files pass straight through. ZX HUB judges passing files with pre-filter → Hyper Sandbox → AI and returns the verdict, and the equipment blocks malicious ones.
Integration
ICAPREST APIFirewall · web gateway · NDR
Technology
The problem with existing solutions
NGFW · UTM · SWG · NDR inspect by signature and reputation and let new, never-seen files straight through. Malicious files that pass spread to PCs on both the internal network and the internet side.
TRAFFICNew files in trafficUNKNOWN malware in downloaded and transferred files
PassedNGFW · UTM · SWG · NDRExisting network equipmentSignature and reputation checks let never-seen files passNew file passes
ENDPOINTInternal PCSpreads across internal network and internet alike
ZX solution
When existing equipment hands files to ZX HUB via ICAP · REST API, they are judged in the order pre-filter → Hyper Sandbox → AI. Malicious files are blocked, and results go to SOAR · SIEM as report.json.
TRAFFICFiles in trafficWeb downloads · transferred files
NGFW · UTM · SWG · NDRExisting network equipmentSubmits to ZX HUB via ICAP · REST API
ZX PLATFORMPre-filter → Hyper Sandbox → AI verdictKnown threats fast, new threats in depth
RESPONSEVerdict returnedBlocks malicious files · report.json to SOAR · SIEM
Known threats fast, new threats in depth
Known threats are filtered out first and fast by reputation, signature and YARA pre-filters. Never-seen threats are actually executed in the Hyper Sandbox, and AI judges the risk.
File intakeMail · cross-domain · endpoint
01 · KNOWNPre-filterReputation · URL · signatures · YARA rules Known threats screened out here first
02 · UNKNOWNHyper SandboxForced button and hyperlink execution · memory analysis · vulnerability traps · anti-evasion Only remaining files analyzed in depth
03 · VERDICTAI risk verdictMITRE ATT&CK mapping
SecOps integrationreport.json → SOAR · SIEM
Detection targets: HWP · DOC · XLS · PPT · PDF · ONE · VBS · JS · HTML · HTA · LNK · archives
Keep your existing investment and add just one analysis layer
Keep the equipment you use today and attach only an analysis layer via MTA · ICAP · REST API. With $0 analysis licenses and servers from 4 cores, costs stay low and there's no transfer delay.
01 · SIMPLICITY
No technical barriers
Attach analysis that catches even evasive threats directly via MTA · ICAP · REST API.
02 · EFFICIENCY
Cost efficiency
No sandbox needed for each layer. $0 OS · Office licenses for analysis, from a 4-core server.
03 · CONTINUITY
Business continuity
No delay in mail or file transfer. ZXONE Agent adds ransomware blocking and recovery.
LINEUP
How the network segment is configured
01ZX HUBIntegrated analysis server · 3-stage engineICAP · REST API integration · judges files passed by your devices
The six questions we hear most before adoption. Answers on replacing equipment, supported equipment, transfer delay, how it differs from existing equipment, detection targets and per-layer purchase.
Do we have to replace our security equipment?
No. Keep your NGFW · UTM · SWG · NDR and other equipment as is, and add only an analysis layer via ICAP · REST API.
What equipment can it connect to?
It integrates via ICAP · REST API with equipment that can hand over files, such as firewalls, web gateways and NDR.
Won't transfers be delayed during analysis?
It averages 0.27 s per file (KBeT test). Even with execution hold as the default, the wait is barely noticeable.
Existing equipment inspects by signature and reputation and lets new, never-seen files through. ZX HUB actually runs them in the Hyper Sandbox and AI judges the risk.
Which files are analyzed?
HWP · DOC · XLS · PPT · PDF · ONE · VBS · JS · HTML · HTA · LNK and archives. Verdicts go to SOAR · SIEM as report.json.
Do we need to buy a sandbox for each layer?
No. A single ZX HUB analyzes email · network · cross-domain (CDS) · endpoint together (integration per layer required).