change management
The process of proposing, reviewing, approving and recording changes to systems, with a plan to undo them.
In more detail
A pull request can carry every part of it: approvers and owners, an impact analysis, test results as status checks, a backout plan and a maintenance window for risky edits. Signed artefacts and SBOMs then document exactly what was released.
Examples
git commit -qam "Lower maxauthtries to 3 (CHG-2291)"git log --date=short --format='%h %ad %an: %s'Related terms
- pull request — A request on a hosting service such as GitHub to merge one branch into another, with a page for review, discussion and automated checks.
- backout plan — The written steps for undoing a change if it goes wrong, prepared before the change is made.
- CODEOWNERS — A file in a repository that maps paths to the people or teams who must review changes to them.
- maintenance window — A pre-agreed time slot when risky changes may be made, chosen so any disruption affects as few people as possible.
- change request — A formal record asking to make a specific change, stating what will change, why, who owns it, and how it will be tested and undone.
- change advisory board — A group of people from technical and business teams who review proposed changes and approve, reject or reschedule them.
- configuration drift — The slow, unrecorded way machines end up with different versions and settings from each other.
Taught in
- Shift-Left Security Principles & Automated Pipeline Gates — Cloud Security & DevSecOps Engineering
- Supply Chain Security: SBOMs & Cosign Signing — Cloud Security & DevSecOps Engineering
- Security Governance vs Security Management — Cybersecurity Fundamentals, GRC & Cryptography
- Security Baselines, Policies & Hardening Standards — Cybersecurity Fundamentals, GRC & Cryptography