Common Cyber
Cross Domain Solution Support and Accreditation Readiness
A Cross Domain Solution controls information transfer between security domains. Getting one fielded and accredited is one of the hardest things a program does.
Why is a CDS difficult?
Tight information-flow constraints, demanding architecture, exhaustive testing, accreditation evidence, and strict change control — and all of them have to line up at the same time.
Where do programs get stuck?
Architecture decisions that were not connected to the accreditation evidence. Test plans that were not connected to the architecture. Sustainment nobody planned for. The pieces exist but they do not talk to each other.
What does Common Cyber provide?
We provide execution support for CDS architecture, evidence development, test readiness, finding resolution, and sustainment planning.
Common Cyber does not accredit, authorize, approve, or guarantee approval of a CDS.
How does CDS work connect to RMF and ATO?
CDS evidence and engineering decisions feed the broader RMF package and shape what the authorizing official sees when making the ATO decision.
What background informs this work?
Anthony led cross domain solution engineering teams for Intelligence Community and Department of War customers at Everfox.
Chadd spent a decade on the information assurance and accreditation side of Special Access Program and Intelligence Community environments. This experience was gained at prior employers and is not presented as Common Cyber project history.
Frequently asked questions
Can Common Cyber accredit a Cross Domain Solution?
No. Common Cyber supports accreditation readiness and execution. The designated government authorities retain approval and authorization decisions.
What CDS work can you support?
Support can include architecture review, evidence development, testing readiness, engineering dependency management, finding resolution, and sustainment planning.
Can CDS support begin inside an existing RMF effort?
Yes. CDS work can be evaluated within the system boundary, current authorization package, open findings, and program schedule.
A clear next step
Establish what the authorization path requires.
The readiness review identifies missing evidence, engineering dependencies, and the critical path toward an authorization decision.
Discuss a Federal Requirement