CRY-01 Policy for the use of encryption procedures and key management
Maintain and issue encryption and key management policies that mandate state-of-the-art algorithms and network protocols, tie encryption strength to the information classification scheme, cover the full key lifecycle, an
4
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
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
- Record of the legal and regulatory cryptographic constraints taken into account · Identity provider / directory
governing documentDocuments that govern the control
- Approved cryptography and key management policy carrying its last review date · Policy repository / GRC workspace
- Table linking each classification level to the required algorithm and minimum key length · Policy repository / GRC workspace
- List of permitted algorithms and protocol versions with the reasoning for their currency · 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
- Algorithms named without stating minimum key lengths or acceptable protocol versions
- No connection drawn between classified information and the encryption strength demanded of it
- Permitted algorithm list untouched while the ciphers it lists were being deprecated externally
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 sheetCOS-08 Policies for data transmission · CRY-02 Encryption of data for transmission (transport encryption)