What is change management?
Change management is the process of planning, approving, testing, and recording changes to systems or services.
Simple example
A firewall rule change is documented and reviewed before being applied to production systems.
Why it matters
Poorly controlled changes can create outages, security gaps, or confusion during incidents.
Common warning signs
- The activity is unexpected or unusual for the business context.
- The request or system behaviour creates pressure to act quickly.
- Normal approval, verification, or security processes are bypassed.
- There are signs of unauthorised access, data exposure, or system change.
- Staff are unsure whether the request, message, or system behaviour is legitimate.
Cyber Doc view
This term should be understood in business context, not only as a technical issue. Good protection usually combines clear processes, appropriate technical controls, staff awareness, and a calm response plan.
What to do
Proactive steps
- Record important technical changes.
- Review high-risk changes before implementation.
- Test changes where practical.
- Keep rollback plans for important systems.
- Communicate changes to affected people.
Reactive steps
- Check recent changes when troubleshooting incidents.
- Rollback unsafe changes if appropriate.
- Preserve change records for investigation.
- Identify whether a change exposed a system or account.
- Improve approval steps after change-related issues.
Related terms
- Secure configuration
- Logging
- Risk