ISO 27001A.8 — Configuration management
A.8.9
Configuration management
ISO 27001 · ISO/IEC 27001:2022 · Last verified July 2026
Objective
Establish, document, implement, monitor, and review configurations — including security baselines — for hardware, software, services, and networks.
Points of focus
- Define scope and requirements for configuration management
- Assign ownership and operating cadence
- Integrate with risk treatment and SoA status
- Retain dated records proving operation
Implementation notes
Codify baselines in IaC and MDM; detect drift; ban snowflake production hosts without change control. Tie the SoA implementation summary to the systems of record engineers already use, and keep dated samples ready for Stage 2 sampling.
Audit tip: Present the SoA line for A.8.9, the current procedure, and one recent dated operating sample with a named owner.
Evidence auditors typically request:
- System configuration export or IaC policy screenshots
- Ticket samples with approver, date, and change outcome
- Monitoring or scan report covering the observation window
- Runbook or SOP linked from the SoA implementation summary
Common gaps
- SoA marks configuration management applicable without dated operating samples
- Procedure exists but interviews describe a different tribal process
- Owner unclear or last review older than the stated cadence
Cross-Framework Mapping
| Framework | Requirement | Implementation note |
|---|---|---|
| ISO 27001 | A.8.9 | This control |
| SOC 2 | CC8.1 | Related Trust Services Criteria themes — map in your crosswalk; not identical requirements. |
Primary sources
- ISO/IEC 27001:2022 Annex A: ISO/IEC 27001:2022 Annex A (A.8.9)
Frequently Asked Questions
Applicability depends on risk and scope. Many cloud-native SoAs still include organizational and technological controls; physical themes may be partially inherited from providers with documented shared responsibility.
Applicability decision, brief implementation summary, and justification if excluded. Vague 'N/A — cloud' without rationale is a common Stage 1 finding.
Name the owner, the system of record, and the cadence. Auditors sample reality — tickets, configs, and interviews — not synonym-rewritten ISO text.