What this control covers
Documents security requirements for premises per SP-01, addressing risks like unauthorized access, fire, and power failure based on risk assessments. Ensures data center compliance with technical standards and verifies third-party facilities to protect cloud infrastructure.
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
vendor_risk_management— See the iCompaas Evidence library for the canonical source for this evidence type.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.
Third-party risk management evidence (assessments, contracts, due diligence) shows supplier oversight. Signed policy or standard documents the safeguard. Focus: Physical Security and Environmental Control Requirements.
Quick checklist
- Risk — Management
- Security — Management
- Physical — Management
- Data — Management
- Access — Management
- Technical — Management