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.
In more detail
The request carries an impact analysis, test results and a backout plan, and it gets approved before the work is done. Its reference number goes into the commit message or configuration history, so the ticket and the edit point at each other. Auditors sample these records to check that every change was approved before it happened.
Example
git commit -qam "Lower maxauthtries to 3 (CHG-2291)"Related terms
- change management — The process of proposing, reviewing, approving and recording changes to systems, with a plan to undo them.
- change advisory board — A group of people from technical and business teams who review proposed changes and approve, reject or reschedule them.
- backout plan — The written steps for undoing a change if it goes wrong, prepared before the change is made.
- audit sample — A subset of items picked from a complete population, such as change tickets, that an auditor tests to reach a conclusion about the whole population.
Taught in
- Security Baselines, Policies & Hardening Standards — Cybersecurity Fundamentals, GRC & Cryptography
- Post-Quantum Cryptography & Key Lifecycles — Cybersecurity Fundamentals, GRC & Cryptography
- Internal Audits, Sampling & Evidence Chains — Cybersecurity Fundamentals, GRC & Cryptography