Ruggedized Cross Domain Solution
In tactical environments, mission-critical information needs to be shared between people, organizations, locations, communities of interest, and security domains, while ensuring exchange of correct and authorized data with authorized recipients.
SafeNet Assured Technologies’ Multi Domain eXchange (MDeX) System for Tactical Environments, an assured information sharing and cross domain solution, provides a reliable, secure, and configurable means of transferring information between domains.
The MTS-R, the MDeX System’s core appliance for tactical environments, provides consistent Multi-Level Security (MLS) services regardless of application protocols and data content filtering needs. It establishes a stable and verifiable framework in which mission managers can implement concurrent yet controlled information flows with various communities of interest and security domains.
Small Form Factor
The MTS-R is based on a MIL-SPEC 810 ruggedized Small Form Factor (SFF) platform that has been optimized to operate within SWAP-constrained vehicle and aircraft platform configurations and harsh environments. Through SFF, the MTS-R provides all MDeX System enterprise capabilities.
Plug and Play Architecture
Diverse protocol-based edge interfaces, (Security Domain Intermediary (SDI) agents), supply the edge interface for connectivity between security domains and the MTS-R, allowing for ready integration of the MTS-R within existing mission UDP streaming, standard file sharing, or other protocol-based exchanges.
The MDeX System’s protocol and content filter APIs enable missions to add new protocols or content filters without changes in the security support structure. As a result, missions can deploy MTS-R configurations with minimal certification impact and minimize accreditation timeframes.
Memory Based Operations
The MTS-R’s memory mode operations enable rapid ingest and delivery of transferred content. Log data is off-loaded to external repository and policy content is maintained on removable media. Policy is instantiated at boot. All content is cleared as part of post-operation sanitization.