CEK-06 Encryption Change Cost Benefit Analysis
Assess the downstream effect of any proposed cryptography or key management change, including residual risk, cost and benefit, before adopting it.
4
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Impact analyses for recent cryptographic changes · Document repository
- Residual risk statement and cost benefit reasoning per change · Document repository
- Identification of dependent systems and data affected · Document repository
- Approval that references the analysis · 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
- Analysis limited to the changed component with dependents unexamined
- Cost considered and residual risk omitted
- Analysis produced after the decision was already taken
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 sheetCEK-05 Encryption Change Management · CEK-07 Encryption Risk Management