ISO 27001:2022 · Technological controls
ISO 27001:2022 8.9: Configuration management
ISO 27001:2022 8.9 covers Configuration management. The held text names 5 evidence records for it, the first being Statement of Applicability entry for control A.8.9, showing inclusion or justified exclusion, implementation status and the risks it.... The common gap an assessor flags is Baselines exist on paper but systems are never measured against them.
The organization is to set, record, apply, watch and review how its hardware, software, services and networks are configured, security settings included. Purpose (stated in ISO/IEC 27002:2022): ensures systems and networks work correctly with required security settings and are not changed without approval or by mistake. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 8.9.
What evidence supports 8.9?
- Annex A technological controlStatement of Applicability entry for control A.8.9, showing inclusion or justified exclusion, implementation status and the risks it treats
- Annex A technological controlApproved secure configuration templates or baselines for each platform, derived from vendor or independent guidance, with review dates
- Annex A technological controlConfiguration records or a CMDB showing owner, last change date, template version and relationships between assets
- Annex A technological controlChange records showing configuration changes passed through change management
- Annex A technological controlConfiguration compliance scan results comparing actual settings with templates, and records of deviations corrected
Where this requirement comes from
This is our own statement of ISO 27001:2022 8.9, read from the copy we hold (licensed complete copy) and stated in our words, not the standard verbatim. The framework as we hold it.
Common gaps an assessor flags
- Baselines exist on paper but systems are never measured against them
- Cloud service configurations are outside configuration management
- Templates are not updated when new software versions are introduced
- Emergency configuration changes bypass change management and are never reconciled
How it maps to SOC 2
- CC7.1 high Configuration management detects deviations that introduce vulnerabilities.
A link is a topical overlap with a confidence and a reason. It does not establish that meeting one requirement satisfies the other, and it is not certification.