What this control covers
This control requires the development, documentation, and dissemination of planning policies and procedures. These policies should address roles, responsibilities, and compliance, while aligning with applicable laws, regulations, and guidelines. The policies and procedures must be reviewed and updated regularly or after significant events. An organization-defined official is responsible for managing this process. This control supports the Planning Policy Management System capability within the Planning 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.
GitHub
Apply branch protection on default and release branches: require PR review, status checks, signed commits, linear history, and dismiss stale reviews on new commits. Use CODEOWNERS for required reviewers, Dependabot + CodeQL for SAST, and the Dependency graph / SBOM export for vendor disclosures.
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 And Procedures.
Quick checklist
- Policy — Procedures / Management
- Process — Procedures / Management
- System — Procedures / Management
- Control — Procedures / Management
- Compliance — Procedures / Management
- Address — Procedures / Management