System & Communications Protection
How CUI is protected in motion and where the boundary sits — segmentation, cryptography, and denial-of-service protection.
The 16 requirements, in plain language.
Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems
Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems
Separate user functionality from system management functionality
Prevent unauthorized and unintended information transfer via shared system resources
Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks
Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception)
Prevent remote devices from simultaneously establishing non-remote connections with organizational systems and communicating via some other connection to resources in external networks (i.e., split tunneling)
Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards
Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity
Establish and manage cryptographic keys for cryptography employed in organizational systems
Employ FIPS-validated cryptography when used to protect the confidentiality of CUI
Prohibit remote activation of collaborative computing devices and provide indication of devices in use to users present at the device
Control and monitor the use of mobile code
Control and monitor the use of Voice over Internet Protocol (VoIP) technologies
Protect the authenticity of communications sessions
Protect the confidentiality of CUI at rest
One owner across the whole family — built, run, and proven.
Enclave builds these controls into the boundary as code; Cadence keeps them enforced between assessments; Attest proves them to the C3PAO against every objective.
See all fourteen families →Not sure which families your contract puts in scope?
A readiness check maps your environment to all 110 controls and tells you exactly where you stand.