Security+General concepts
Change management
Outline only. Change management is the controlled path from a request to a recorded result.
8 min read · Outline, not a finished note
Outline. This module is on the map so you can track it. The page below is a writing checklist, not finished study material.
Objectives
- List the ideas a finished note must define
- Keep emergency change from becoming an unwritten bypass
TODO
Write a short finished note. No ticket-system tutorial.
Checklist
- A change has a requester, a reason, an impact, a backout, an approval, and a record.
- Standard changes are pre-approved and low risk. Normal changes go through review. Emergency changes happen fast and are reviewed after. The exam likes that trio.
- Security cares because an unreviewed firewall or identity change is both an outage risk and a control failure.
- Separation of duties shows up when the person who asks should not be the only person who approves.
- Link the finished note to vulnerability management. A patch is a change.