During a weekly IT governance meeting, the operations manager notes that multiple unplanned configuration tweaks made by junior administrators have caused intermittent outages on the company's ERP servers. Senior leadership wants a formal procedure that requires documenting every proposed modification, obtaining approvals, scheduling implementation windows, and verifying rollback plans so that future updates occur in a consistent, auditable, and low-risk manner. Which type of procedure should the security team recommend to meet this requirement?
A change-management procedure controls the entire lifecycle of modifications to IT systems. By mandating documentation, approval, testing, scheduling, and rollback planning, it ensures changes are introduced in a controlled and coordinated way, minimizing disruptions to services. Onboarding procedures focus on bringing new employees or assets into service, an incident-response playbook guides containment and recovery after a security event, and an access-control standard defines permissions but does not manage the change process itself.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
Why is a change-management procedure important in IT operations?
Open an interactive chat with Bash
What steps are typically involved in a change-management procedure?
Open an interactive chat with Bash
How is change management different from incident response?