CEK-05 Encryption Change Management
Route changes to cryptographic, encryption and key management technology through a standard change procedure covering review, approval, implementation and communication, whether the change originates inside or outside th
4
artefacts
0
held by a system
3
at each review
hard
to go live
Ticketing / ITSM
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
- Change records for recent cryptographic changes with approvals · Ticketing / ITSM
- Evidence externally driven changes, such as a vendor deprecation, entered the same process · Ticketing / ITSM
- Communication records to affected parties · Ticketing / ITSM
governing documentDocuments that govern the control
- The change procedure covering cryptographic technology specifically · 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
- Cryptographic library upgrades treated as routine patching outside change control
- Vendor-driven changes accepted with no internal review
- Affected downstream consumers not told before the change lands
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-04 Encryption Algorithm · CEK-06 Encryption Change Cost Benefit Analysis