ISO 27001:2022 · Technological controls
ISO 27001:2022 8.32: Change management
ISO 27001:2022 8.32 covers Change management. The held text names 5 evidence records for it, the first being Statement of Applicability entry for control A.8.32, showing inclusion or justified exclusion, implementation status and the risks it.... The common gap an assessor flags is Changes are made directly in production without a change record.
Every change to information systems and processing facilities is to pass through the change management procedures. Purpose (stated in ISO/IEC 27002:2022): preserves information security when changes are executed. 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.32.
What evidence supports 8.32?
- Annex A technological controlStatement of Applicability entry for control A.8.32, showing inclusion or justified exclusion, implementation status and the risks it treats
- Annex A technological controlThe documented change management procedure covering infrastructure and software, integrated where practical
- Annex A technological controlChange records showing impact and dependency assessment, authorization, stakeholder communication, testing and acceptance, deployment plan and fallback
- Annex A technological controlEmergency change records with retrospective review and approval
- Annex A technological controlEvidence that operating documentation, user procedures and ICT continuity plans were updated after changes
Where this requirement comes from
This is our own statement of ISO 27001:2022 8.32, 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
- Changes are made directly in production without a change record
- Emergency changes are never reviewed after the fact
- Impact assessment ignores dependencies, causing unexpected outages
- Continuity plans and runbooks are not updated after infrastructure changes
How it maps to SOC 2
- CC3.4 medium Change management assesses change but not changes to the control environment generally.
- CC8.1 high Change management is this change criterion directly.
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.