A Cross-Domain Transfer is the controlled movement of information or an information-bearing Artifact from one Security Domain to another Security Domain.
The source and destination Security Domains can differ in:
A Cross-Domain Transfer can move information:
A transfer between domains at the same Security Classification remains a Cross-Domain Transfer when different security policies, compartments, authorities, or release rules govern the domains.
A Cross-Domain Transfer can use:
A Cross-Domain Transfer can include:
Transfer from a higher-classification domain to a lower-classification domain requires an authorized release, downgrading, declassification, sanitization, or review process. The transfer mechanism does not itself grant authority to release the information.
Transfer into a higher-classification domain can also require validation because imported information or software can introduce:
Within Crucible, Cross-Domain Transfer can apply to:
controlled movement of information or an information-bearing Artifact from one Security Domain to another
A Cross-Domain Transfer is not equivalent to ordinary network transmission.
The transfer must account for the security policies and Information Handling Rules of both the source and destination Security Domains.
A Cross-Domain Transfer can occur without a direct network connection. For example, approved removable media can carry information between two Air-Gapped Environments.
A Cross-Domain Solution is a technical or procedural mechanism used to perform or control a Cross-Domain Transfer. The solution and the transfer are distinct:
A successful technical transfer does not establish that the transfer was authorized or compliant. The transfer record must demonstrate satisfaction of the governing Information Handling Rules.
A Crucible Infrastructure Baseline moves from a Connected Unclassified Environment to an Air-Gapped Classified Environment.
The Cross-Domain Transfer process:
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.