CM.L2-3.4.4 Security Impact Analysis
Analyze the security impact of a proposed change before it is implemented.
3
artefacts
0
held by a system
2
at each review
hard
to go live
Cloud console / configuration management
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
- Security impact analysis recorded within change records · Cloud console / configuration management
- Evidence analysis occurs prior to implementation · Cloud console / configuration management
governing documentDocuments that govern the control
- Criteria defining when deeper analysis is required · Policy repository / GRC workspace
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
- Impact analysis performed after deployment
- Analysis reduced to a checkbox with no substance
- Changes deemed routine exempted without criteria
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 sheetCM.L2-3.4.3 System Change Management · CM.L2-3.4.5 Access Restrictions for Change