What this control covers
Information security policy and topic-specific policies shall be defined, approved by management, published, communicated to and acknowledged by relevant personnel and relevant interested parties, and reviewed at planned intervals and if significant changes occur.
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.
Signed policy or standard documents the safeguard. Focus: Policies for information security.
Quick checklist
- Policy — Information Security / Management
- Information — Information Security / Management
- Management — Information Security / Management
- Security — Information Security / Management
Related articles on this site
- NIST 800-171 3.1.15 Authorize remote execution of privileged commands and remote access to security-relevant information.
- NIST 800-171 3.2.2 Ensure that personnel are trained to carry out their assigned information security-related duties and responsibilities.
- CMMC 2.0 AC.3.021 Authorize remote execution of privileged commands and remote access to security-relevant information.
- CMMC 2.0 AT.2.057 Ensure that personnel are trained to carry out their assigned information security-related duties and responsibilities.