Change management is a controlled, documented way to modify systems without losing track of security or disrupting operations. A change management policy sets the rules for modifying systems, applications, processes, and infrastructure. Instead of making changes ad hoc, an organization requests, assesses, approves, tests, implements, and reviews them. section 15.6 section 16.7
Even a well-hardened system can drift away from its approved security state as software and configurations change. Security baselines provide a reference for judging a proposed change and checking the result. A documented process helps catch risks before deployment and provides a way back if something goes wrong. section 15.6 section 15.7
The change management lifecycle has six steps:
- Request the change. Describe its purpose, benefits, resources, risks, and a preliminary rollback plan. section 15.7
- Analyze its impact. Check security risks, costs, dependencies, and effects on connected systems against the approved baseline. section 15.7
- Review and approve it. Authorized stakeholders, such as a Change Advisory Board, may approve, reject, or request more analysis. section 15.7
- Test it in a controlled environment before production deployment to check its intended function and unintended effects. section 15.7
- Implement it after approval, often during a maintenance window, with the rollback plan available. section 15.7
- Review the result. Check whether the change met its goals, caused unexpected issues, or moved the system away from its approved configuration. section 15.7
A change that cannot wait
A patch for an actively exploited vulnerability may need to be deployed too quickly for the standard approval process. An emergency change procedure allows rapid action while retaining documentation and review. If a change fails, rollback aims to restore the system to its previous state. section 16.7 section 15.11




