What this control covers

Documents encryption and key management policies per SP-01, specifying strong encryption, risk-based usage, and secure key lifecycle management. Aligns with data classification and legal requirements to protect cloud customer data confidentiality and integrity.

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.

GCP

Use Cloud KMS with customer-managed encryption keys (CMEK) for BigQuery, GCS, and Compute. Sensitive Data Protection (DLP API) inspects/de-identifies PII at scale.

Google Workspace

Enable client-side encryption for Drive/Docs and turn on Drive Labels + DLP rules to prevent external sharing of regulated data classes.

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: Policy for the use of encryption procedures and key management.

Quick checklist

  • Risk — Protection / Cloud Customer Data
  • Confidentiality — Protection / Cloud Customer Data
  • Protection — Protection / Cloud Customer Data
  • Data — Protection / Cloud Customer Data
  • Policy — Protection / Cloud Customer Data
  • Encryption — Protection / Cloud Customer Data

Related articles on this site