03.04.04 Impact Analyses
Analyze security impact of changes prior to implementation; test, validate, and document changes before deployment.
3
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Test results · Source control / CI pipeline
- Approval records · Document repository
governing documentDocuments that govern the control
- Change impact templates filled · Document repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- no test environment
- impact analysis perfunctory
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet03.04.03 Configuration Change Control · 03.04.05 Access Restrictions for Change