CRY-03 Encryption of sensitive data for storage
Encrypt cloud customer data while it is stored and keep the private keys known only to the customer, handling any exception through a specified procedure that is contractually agreed with that customer.
4
artefacts
0
held by a system
1
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
- Signed terms covering key custody and any agreed departure from customer-only knowledge · Document repository
governing documentDocuments that govern the control
- Storage encryption design identifying where the customer holds the private key material · Document repository
- Written exception procedure together with the log of exceptions actually invoked · Policy repository / GRC workspace
- Demonstration that provider personnel cannot retrieve keys held by the customer · 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
- Provider-managed keys presented as customer keys while the provider retains full retrieval ability
- Departures from customer key custody practised operationally without any agreed basis
- Encryption switched on for primary storage but absent on replicas, snapshots and archives
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 sheetCRY-02 Encryption of data for transmission (transport encryption) · CRY-04 Secure key management