A8.32 Change management
Change management is essential to ensure that all modifications to systems, applications, and infrastructure are performed in a controlled, secure, and documented manner. Without proper change management, organizations risk service disruptions, security vulnerabilities, and loss of data integrity.
ISO 27001 A8.32 Change management emphasizes the need for a formal process to manage all types of changes—whether they are technical (e.g., system updates), procedural (e.g., process adjustments), or operational (e.g., changes in roles or access). The goal is to reduce risk, improve coordination, and ensure accountability during the change lifecycle.
Implementation Guide #
Step 1: Define a Change Management Policy
- Develop and document a policy outlining how changes are requested, reviewed, approved, implemented, and reviewed.
- Classify changes (e.g., standard, emergency, major, minor) with corresponding handling procedures.
→ Tool Recommendation: Confluence or Notion for policy documentation and distribution.
Step 2: Use a Centralized Change Management System
- All changes must be submitted, tracked, and reviewed via a centralized platform.
- Include fields for change description, impact assessment, rollback plan, and approvals.
→ Tool Recommendation:
- ServiceNow, Jira Service Management, or Freshservice for change request tracking and workflow automation.
Step 3: Conduct Impact and Risk Assessments
- Evaluate the technical, operational, and security implications of each change.
- Perform risk assessments for high-impact changes.
→ Tool Recommendation: RiskLens, LogicManager, or manual risk scoring templates for structured risk evaluation.
Step 4: Approvals and Scheduling
- Ensure changes are reviewed and approved by the appropriate authority based on impact level.
- Schedule changes during predefined maintenance windows to minimize disruption.
→ Tool Recommendation: Use Jira workflows, ServiceNow, or com for multi-tier approvals.
Step 5: Communication and Notification
- Notify all impacted stakeholders in advance of scheduled changes.
- Use automated alerts for reminders and post-change confirmation.
→ Tool Recommendation: Slack, Microsoft Teams, PagerDuty, or Opsgenie for real-time communication.
Step 6: Implementation and Validation
- Execute the change according to a defined plan, including fallback or rollback steps.
- Post-change testing and validation should confirm successful outcomes.
→ Tool Recommendation: Use CI/CD tools like Jenkins, GitLab, or Azure DevOps to deploy and validate changes safely.
Step 7: Maintain a Change Log and Audit Trail
- Document every change, including request date, approvers, outcomes, and incidents (if any).
- Retain this documentation for audits and incident investigations.
→ Tool Recommendation: Splunk, ELK Stack, or Wazuh for change log collection and analysis.
Templates #
- Change Management Policy
- Change Request Form
- Risk and Impact Assessment Template
- Change Log Register
- Change Approval Matrix
- Rollback Plan Template
Example #
A SaaS company was deploying updates to its production servers without a formal review process. This led to a major outage caused by an incompatible software patch. After implementing a structured change management process using ServiceNow and GitLab CI/CD, all changes were logged, risk-assessed, and tested in staging before live deployment. The new process eliminated unexpected downtimes and enabled better compliance with audit requirements.
How to Comply #
To comply with ISO 27001 A.8.32, organizations should:
- Establish and enforce a formal change management policy.
- Require approval and risk assessment before implementing changes.
- Use automation tools to track, log, and verify changes.
- Maintain complete documentation for all changes and outcomes.
- Ensure all changes follow a structured lifecycle from request to post-implementation review.
How to Pass an Audit #
Key Documents to Prepare:
- Change Management Policy
- Recent Change Logs with Approvals
- Risk/Impact Assessment Forms
- Evidence of Testing and Rollbacks
- Change Meeting Minutes or Communication Records
What the Auditor Will Check:
- Is there a structured change management policy in place?
- Are all changes logged, risk-assessed, and approved?
- Is there evidence of rollback plans and validation steps?
- Are stakeholders informed and changes tracked?
Top 3 Mistakes People Make #
- Bypassing the change process for “quick fixes” or emergency changes
- Failing to communicate changes to impacted users or teams
- Not keeping a centralized, auditable change log
ISO 27001 Change Management FAQ #
Q1: Is emergency maintenance exempt from the change management process?
No. Emergency changes can be expedited but must still be logged, justified, and reviewed after execution.
Q2: Who should approve a change?
Approval depends on the scope and risk. Major changes typically require IT leadership and risk/compliance sign-off, while minor ones may be approved by a change manager.
Q3: Can automation tools handle change validation?
Yes. Automated pipelines (e.g., Jenkins, GitHub Actions) can execute tests, validate outcomes, and log results as part of change workflows.
ISO 27001 Controls and Attribute Values #
| Control | Attribute Value |
| A.8.32 Change Management | Preventive, Risk-Based, Administrative, Operational |
| Purpose | Ensure all changes are controlled, secure, and auditable |
| Applicability | All departments making changes to information systems, infrastructure, or policies |
| ISO 27001 Domains | Operations Security, System Development and Maintenance |
Robust change management mitigates disruption risks, supports compliance, and promotes safer IT operations.