AMVLET's Cross Domain Solution enables classified and unclassified environments to exchange information with precision — every transfer inspected, sanitised, and policy-controlled before it crosses the line.
Every transfer between your classified and unclassified environments passes through the Cross Domain Gateway — inspected, sanitised, and logged before delivery.
The Cross Domain Solution connects what must be connected — while structurally preventing what must never cross.
No direct network path exists between your classified and unclassified environments. The originating connection terminates at the CDS. After inspection, an entirely new connection delivers only the approved, sanitised content to the destination. The two networks never touch.
Every transfer is scanned against your security policy before crossing the boundary — keywords, file types, size limits, embedded metadata. Content that fails any inspection step is quarantined instantly and logged in full. Nothing reaches the destination domain uninspected.
Configure strictly one-way export, strictly one-way import, or controlled bidirectional exchange — with independent security policies applied to each direction. Most deployments begin with one-way and expand as operational confidence grows.
Unlike a conventional firewall, the Cross Domain Solution understands and re-constructs data at the application layer. Here is what that means in practice.
The CDS is built to specification and embedded in dedicated hardware that sits at the physical edge of your classified network. This is not a software proxy — it is a purpose-built device. AMVLET works with all major cross-domain hardware vendors, providing the Matrix software layer that runs on top of your hardware infrastructure.
The sending system connects to the CDS — not to the destination. The CDS receives the data, closes the inbound connection, and inspects the content in an isolated environment. If the content is approved, the CDS opens a brand-new, independent connection to the destination and delivers only the sanitised content. No TCP session is ever shared between the two domains.
Each transfer passes through a configurable inspection pipeline: keyword scanning, file type verification, structural analysis, metadata stripping, and size enforcement. Transfers that fail any step are quarantined before they reach the destination. The quarantine log is timestamped, attributed, and available for audit — every blocked transfer is a record, not just a rejection.
Your CDS operates according to a security policy agreed with your data controller on a case-by-case basis. Every permitted content type, every direction of transfer, every keyword on the blocklist is explicitly defined. Policy updates are deployed through a controlled change process, take effect without service interruption, and every change is logged with a timestamp for audit purposes.
AMVLET's Cross Domain Solution integrates with all cross-domain hardware vendors. Whether your organisation has existing CDS infrastructure or is commissioning a new deployment, AMVLET provides the Matrix protocol layer that enables your CDS hardware to handle Matrix-based communications natively — with full support for federation, rooms, and events.
A classified network is only as secure as its weakest connection to the outside. Cross Domain Solutions replace that weakness with a controlled, policy-enforced channel — not a door left open, but a letter box with a guard.
High-side environments exist because some information is too sensitive to risk on ordinary networks. The intelligence agency. The defence contractor. The financial regulator with systems holding restricted supervisory data. Each operates a classified domain — physically or logically separated from the outside world by design. For decades, that separation meant isolation. If a message needed to cross the boundary, it was printed, reviewed, hand-carried, and re-entered. The risk was managed by removing the connection entirely.
Isolation works. It also has costs. Even the most classified environments need to communicate externally — briefings delivered to oversight bodies, status reports shared with liaison teams, field reports ingested from less-secure partner networks. Doing this securely, at the pace modern operations require, is not possible with manual processes. Organisations that cannot move information quickly pay for it in operational speed.
The answer is not to lower the security bar — it is to build a controlled channel precise enough to maintain it. That is what a Cross Domain Solution does.
Most people understand a firewall: it looks at the envelope and decides whether to let the packet through. A Cross Domain Solution does something fundamentally different. It opens the envelope, reads everything inside, decides whether the content meets the agreed security policy, and if it does — writes a new envelope on the other side and sends a fresh copy. The original connection is gone. The original packet never crossed. Only approved, sanitised content reached the destination.
In technical terms: when a Matrix message is sent from the classified domain, the Matrix client connects to the CDS — not to the low-side homeserver. The CDS terminates the connection, extracts the message content, runs it through the inspection pipeline. If it passes, the CDS opens a new connection to the low-side homeserver and delivers the approved content as a new Matrix event. The two Matrix deployments are never in direct federation. The protocol break is complete.
What a Cross Domain Solution gives classified environments is the ability to define precisely what can move between worlds. Which content types are permitted. Which direction each type can travel. Which senders are trusted. Which words trigger quarantine. Organisations that deploy a CDS gain a controlled, auditable channel — not an open door, but a precisely-specified interface that lets the right information through while keeping everything else contained. For environments that operate at classification level, that precision is the only kind of external communication that is acceptable.
What security, compliance, and engineering teams ask when evaluating a Cross Domain Solution for Matrix.
See how AMVLET's Cross Domain Solution gives your regulated environment a controlled, auditable channel to the outside world — without compromising the integrity of your classified domain.