What this control covers

This control requires implementing cryptographic mechanisms to protect the confidentiality of Controlled Unclassified Information (CUI). The cryptography must align with applicable laws, regulations, and standards, with FIPS-validated cryptography recommended for CUI protection. This control supports the Cryptographic Protection capability within the Situational Awareness (3.13) family.

Why it matters

Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.

How to implement

AWS

Codify the policy intent as SCPs, AWS Config conformance packs, and Security Hub standards so the cloud enforces what the document says.

Azure

Codify in Azure Policy initiatives (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.

On-premises

Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.

Evidence to collect

  • policy_document — A signed, version-controlled policy stating leadership intent and the named owner.
  • infra_scan — See the iCompaas Evidence library for the canonical source for this evidence type.

Signed policy or standard documents the safeguard. Focus: Cryptographic Protection.

Quick checklist

  • Information — Management / Cui
  • Protection — Management / Cui
  • Risk — Management / Cui
  • Cryptographic — Management / Cui
  • Policy — Management / Cui

Related articles on this site