Every ingress path needs a different defense. File gateway and file server: SLF. On-premises email: SLE. Cloud email: DISARM. Sanitization and intelligence: SLCDR and ConTI — all powered by one MARS engine.
External content reaches your organization through two primary paths — the file path and the email path. Place the right product on each, then layer the cross-path options (SLCDR, ConTI) where you need them.
Inline file gateway for cross-network transfer, document repositories, web uploads, and OT segments. Before a file ever opens, MARS disassembles its structure — block if malicious, pass if clean.
On-premises mail server? Choose SLE. On Microsoft 365 or Google Workspace? Choose DISARM. Same MARS engine — different deployment shape.
Sits in front of the existing mail gateway. MARS inspects attachments and body URLs before they reach the recipient — 12-second average analysis with no perceptible mail delay.
API-native integration for Microsoft 365 and Google Workspace. Deployed in minutes — no MX changes, no servers to stand up. Covers password-protected archives, BEC impersonation, and retroactive inbox rescans from the cloud.
Plug SLCDR and ConTI into SLF, SLE, or DISARM as modules — or deploy them standalone.
Sanitization (path-agnostic option)
Strips macros, scripts, embedded OLE objects, ActiveX, DDE, and malicious links at the structural level, then reassembles with the original layout intact. Comments and hyperlink schemas preserved.
Threat intelligence (path-agnostic option)
Aggregates first-party detections across 100+ deployments to extract new techniques, IOCs, and campaigns. Integrates with national CERT and VirusTotal feeds and distributes automatic blocking rules.
| Capability | SLF | SLE | DISARM | SLCDR | ConTI |
|---|---|---|---|---|---|
| Primary ingress path | File gateway, file server, upload | In front of mail server | Microsoft 365 / Workspace | Web portal, public-service upload | Common to all paths |
| MARS engine | Included | Included | Included | Included | Data source |
| Detection (verdict) | Standard | Standard | Standard | Optional | — |
| Sanitization (CDR) | Optional | Optional | Standard | Standard | — |
| Throughput | 49K–315K/day | 160K–912K/day | API scale | 34 ms/file | — |
| Deployment shape | Appliance | Appliance | API (minutes) | Module or standalone | Module or standalone |
| Representative reference | National Health Insurance Service | LIG Nex1 | IMM Investment | KIDI | Security research team |
Whether the content arrives as a file or as an email, the same engine runs the same pipeline — disassemble, decide, sanitize, aggregate intel. The products are simply different deployment shapes of that pipeline.
We walk through your current file-transfer architecture, mail gateway, and cloud tenant — and draft which product goes where. In the same session we lock in the PoC and benchmark (BMT) schedule.
