CEK-15 Key Activation
Create keys in a pre-activated state so a generated key cannot be used until it has been explicitly authorised for use.
4
artefacts
1
held by a system
2
at each review
moderate
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
- System configuration showing keys default to inactive on generation · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Authorisation records moving keys into active use · Document repository
- Evidence a key cannot be used while pre-activated · Document repository
governing documentDocuments that govern the control
- The procedure describing the pre-activated state and the authorisation step · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Keys immediately active on generation with no authorisation gate
- Pre-activation state exists in the procedure but not in the system
- Authorisation performed by the same person who generated the key
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 sheet