Skip to content

Reference

Security, data and compliance in Cross-Domain Solution (CDS) Transfer Agent

Security controls, supported requirements, hosting and limitations of Cross-Domain Solution (CDS) Transfer Agent.

Applies to Cross-Domain Solution (CDS) Transfer Agent as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.

Last reviewed 2 min readReport a problem
On this page
  1. Security controls
  2. Single sign-on
  3. Role-based access
  4. No execution
  5. Encryption and keys
  6. Complete audit trail
  7. Your authority, cleared support
  8. Requirements it supports
  9. Where it runs
  10. Limitations

How Cross-Domain Solution (CDS) Transfer Agent protects data and supports your compliance obligations.

Security controls

Single sign-on

Users sign in through your identity provider, so your authentication and multi-factor policies apply.

Role-based access

What each person can see and do follows their role; requesting a transfer is separate from approving it.

No execution

Files are parsed and rebuilt, never opened in their native applications or executed during inspection.

Encryption and keys

Files at rest and in transit are encrypted, with keys Moraph staff cannot use without explicit, time-bound authorization.

Complete audit trail

Every request, inspection, removal, review and release is logged with the person and time, and cannot be edited.

Your authority, cleared support

On classified networks the Agent is installed and operated under your authority. Support tickets for defense and intelligence clients are handled only by US citizens with active clearances.

Requirements it supports

  • DoD Instruction 8540.01, Cross Domain (CD) Policy
  • NCDSMO Raise the Bar cross domain solution design and implementation requirements
  • CNSSI 1253, Security Categorization and Control Selection for National Security Systems
  • NIST SP 800-53 Rev. 5, including AC-4 Information Flow Enforcement
  • Intelligence Community Directive 503, IC Information Technology Systems Security Risk Management
  • DoD Instruction 8510.01, Risk Management Framework for DoD Systems

The product supports these requirements; meeting them remains your organization's responsibility.

Where it runs

  • Client-hosted across domains: Installed in your environment on each side of an approved transfer path, operated under your authority and within your cross-domain approval.
  • Unclassified boundary: For files entering an unclassified network from the internet or from partners, available hosted in Moraph's United States region.
  • With a managed service: Optionally supported by a Moraph managed service for rule maintenance and administration, with staff who hold the clearances your environment requires.

Limitations

  • Moraph does not claim that the Transfer Agent is listed on the NCDSMO Baseline or accredited for any classified environment. Using it on a path between classification levels requires your organization's own cross-domain approval and authorization.
  • It is a software sanitization and review component. It does not replace the cross-domain guard, data diode or network controls that enforce the boundary.
  • Sanitization reduces risk but cannot guarantee that every hidden channel is removed. Data concealed in the visible content of an image or document can survive re-encoding, which is why human review remains part of the process.
  • File types outside the supported list are blocked rather than passed through; formats that cannot be rebuilt cannot be sanitized.
  • Malware detection depends on the engines your organization provides and how current their signatures are.
  • Keyword and marking checks support reviewers; they do not make classification or release decisions. Those remain with your trained reviewers and security officers.
  • Rebuilt documents may lose features such as macros, form logic, embedded media and some formatting, by design.
  • Encrypted or password-protected files cannot be inspected and are blocked unless your rules provide another route.
Note

Company-wide controls, independent audits (SOC 2 Type II and ISO/IEC 27001) and data residency are described in the Moraph Trust Center, where you can request the evidence pack.

Was this page helpful?

Report a problem with this page
What’s the problem?
Quote the step or heading if you can. Don’t include passwords or personal records.
Only if you’d like a reply. We use it for this report and nothing else.

Need help with your own setup rather than this page? Raise a support ticket.