SAMMY works best on screens 1024px wide or larger.
Cloud Controls Matrix
Browse Cloud Controls...
CEK-01: Encryption and Key Management Policy and Procedures
Encryption and Key Management Policy and Procedures
CEK-01: Are cryptography, encryption, and key management policies and procedures established, documented, approved, communicated, applied, evaluated, and maintained?

Policies and procedures on the use, protection, and lifetime of cryptographic keys should be developed and implemented through their full lifecycle.


Policies and procedures include but are not limited to the following considerations:


A. Policies and procedures relating to organization/management.
a. Roles and responsibilities (See GRM for general considerations)
b. Data protection (DSP domain for general considerations)



  1. Data encryption

  2. Algorithm
    c. Change management (See CCC domain for general considerations)

  3. Cost-Benefit analysis
    d. Risk management (See BCR/GRC domains for general considerations)
    e. Monitoring and reporting (see LOG and monitoring domain for general considerations )
    f. Transaction/activity logging (see LOG and monitoring domain for general considerations)
    g. Incident handling (see SEF domain for general considerations)
    h. Audit (See A&A domain for general considerations)


B. Policies and procedures relating to key management.
a. Key generation
b. Key distribution
c. Key rotation
d. Key revocation
e. Key destruction
f. Key activation
g. Key suspension
h. Key deactivation
i. Key archival
j. Key compromise
k. Key recovery
l. Key inventory management
m. Key purposes
n. Key access


Not applicable - A “N/A” answer indicates that the portion of the control in question is out of scope of the assessment. The “SSRM control ownership” column is to be left blank (e.g., greyed out), and optionally the CSP may explain why it is the case (“CSP Implementation Description”).
No - A “No” answer indicates that the portion of the control in question is not implemented, while in scope of the assessment. The CSP has to assign the implementation responsibility of the control to the relevant party under column “SSRM control ownership”, and optionally elaborate on the “why” (has not been implemented), and “what” has to be done for its implementation by that party.
Yes - A “Yes” answer indicates that the portion of the control in question is implemented. The CSP indicates the responsible and accountable parties (SSRM control ownership), and optionally elaborates on the implementation “how-to” per relevant party CSP and/or CSC.
CSP-owned - The CSP is entirely responsible and accountable for the CCM control implementation.
CSC-owned - The Cloud Service Customer (CSC) is entirely responsible and accountable for the CCM control implementation.
Third-party - The third-party CSP in the supply chain (e.g., an IaaS provider) is responsible for CCM control implementation, while the CSP is fully accountable.
Shared CSP and CSC - Both the CSP and CSC share CCM control implementation responsibility and accountability.
Shared CSP and third party - Any CCM control implementation responsibility is shared between CSP and the third party, but the CSP remains fully accountable.
Description

Establish, document, approve, communicate, apply, evaluate and maintain policies and procedures for Cryptography, Encryption and Key Management. Review and update the policies and procedures at least annually.

Encryption and Key Management Policy and Procedures
CEK-01: Are cryptography, encryption, and key management policies and procedures reviewed and updated at least annually?

Policies and procedures on the use, protection, and lifetime of cryptographic keys should be developed and implemented through their full lifecycle.


Policies and procedures include but are not limited to the following considerations:


A. Policies and procedures relating to organization/management.
a. Roles and responsibilities (See GRM for general considerations)
b. Data protection (DSP domain for general considerations)



  1. Data encryption

  2. Algorithm
    c. Change management (See CCC domain for general considerations)

  3. Cost-Benefit analysis
    d. Risk management (See BCR/GRC domains for general considerations)
    e. Monitoring and reporting (see LOG and monitoring domain for general considerations )
    f. Transaction/activity logging (see LOG and monitoring domain for general considerations)
    g. Incident handling (see SEF domain for general considerations)
    h. Audit (See A&A domain for general considerations)


B. Policies and procedures relating to key management.
a. Key generation
b. Key distribution
c. Key rotation
d. Key revocation
e. Key destruction
f. Key activation
g. Key suspension
h. Key deactivation
i. Key archival
j. Key compromise
k. Key recovery
l. Key inventory management
m. Key purposes
n. Key access


Not applicable - A “N/A” answer indicates that the portion of the control in question is out of scope of the assessment. The “SSRM control ownership” column is to be left blank (e.g., greyed out), and optionally the CSP may explain why it is the case (“CSP Implementation Description”).
No - A “No” answer indicates that the portion of the control in question is not implemented, while in scope of the assessment. The CSP has to assign the implementation responsibility of the control to the relevant party under column “SSRM control ownership”, and optionally elaborate on the “why” (has not been implemented), and “what” has to be done for its implementation by that party.
Yes - A “Yes” answer indicates that the portion of the control in question is implemented. The CSP indicates the responsible and accountable parties (SSRM control ownership), and optionally elaborates on the implementation “how-to” per relevant party CSP and/or CSC.
CSP-owned - The CSP is entirely responsible and accountable for the CCM control implementation.
CSC-owned - The Cloud Service Customer (CSC) is entirely responsible and accountable for the CCM control implementation.
Third-party - The third-party CSP in the supply chain (e.g., an IaaS provider) is responsible for CCM control implementation, while the CSP is fully accountable.
Shared CSP and CSC - Both the CSP and CSC share CCM control implementation responsibility and accountability.
Shared CSP and third party - Any CCM control implementation responsibility is shared between CSP and the third party, but the CSP remains fully accountable.
Description

Establish, document, approve, communicate, apply, evaluate and maintain policies and procedures for Cryptography, Encryption and Key Management. Review and update the policies and procedures at least annually.