What this control covers
Develops, documents, and maintains a current baseline configuration under configuration control, updating it periodically or when components change. This control supports the Baseline Configuration System capability within the Configuration Management 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.
GCP
Org Policy Service for guardrails and Config Validator in CI to pre-check Terraform plans against policy as code (Rego).
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
infra_scan— See the iCompaas Evidence library for the canonical source for this evidence type.
Infrastructure posture tooling (AWS Config, Azure Policy, Nessus) verifies platform hardening. Focus: Baseline Configuration.
Quick checklist
- Security — Management / System
- Configuration — Management / System
- Network — Management / System
- System — Management / System
- Control — Management / System
- Baseline — Management / System
Related articles on this site
- Microsoft Cloud Security Posture Management (CSPM)
- Ensure a log metric filter and alarm exist for changes to Network Access Control Lists (NACL)
- 2.10 Ensure that Microsoft Cloud App Security (MCAS) integration with Security Center is selected
- Ensure Diagnostic Setting captures appropriate categories from the control/management plane