Compliance infrastructure for classified environments

Because it does not collapse the three security objectives into a single high-water mark. Under CNSSI 1253 a national security system is categorised separately for confidentiality, integrity and availability, so a system can be High for confidentiality and Low for availability, and the baseline it receives reflects that shape. The practical effect is that a system categorised as though it were a single level either carries controls it does not need or misses controls it does — and on the confidentiality axis, the second is the one that matters.

How much separation the system has to enforce between what different users are cleared and authorised to see. Protection Levels are assigned by comparing the clearance and formal access approvals of the user population against the sensitivity of the data on the system, and the level then drives the technical control requirements. It is a property of the relationship between users and data, which is why adding a user population with different accesses can change the Protection Level of a system that has not otherwise been modified.

Not where the evidence itself is classified and the environment is disconnected, which is the ordinary case in compartmented programmes. The constraint is not the platform's security posture but the boundary: evidence describing a classified system is generally classified, and moving it to a service outside the accreditation boundary is a spillage question rather than a procurement one. That is why the deployment model matters more than the feature set in this environment.

ICD 503 sets risk management and authorization policy for intelligence community systems using terminology aligned to the NIST risk management framework, which is what makes reciprocal acceptance of assessments across compatible standards possible at all. The alignment is deliberate and it is also partial — the control baselines come from CNSSI 1253 rather than from the civil baselines, and the community's own supplemental requirements sit on top. Alignment enables reciprocity; it does not make the packages interchangeable.

Evidence inherits the classification of what it describes, and it accumulates. A screenshot of a configuration, an assessment result, a scan output and a POA&M entry can each be classified, and together they form a concentration of information about the system's weaknesses. That means chain of custody, storage at level, controlled access and disposal are part of the compliance workflow rather than surrounding it — and it is why an air-gapped programme cannot simply adopt the tooling used on the unclassified side.