CRY-10.3: Cryptographic Key Loss or Change
Mechanisms exist to ensure the availability of information in the event of the loss of cryptographic keys by individual users.
Renumbered: Formerly CRY-09.3 in SCF 2025.4.
Control Question: Does the organization ensure the availability of information in the event of the loss of cryptographic keys by individual users?
General (21)
| Framework | Mapping Values |
|---|---|
| AICPA TSC 2017:2022 (used for SOC 2) (source) | CC6.1-POF11 |
| CSA CCM 4.1.0 | CEK-12 CEK-13 CEK-14 CEK-15 CEK-16 CEK-17 CEK-19 |
| CSA IoT SCF 2 | IAM-10 IAM-11 IAM-13 |
| GovRAMP | SC-12(01) |
| GovRAMP High | SC-12(01) |
| ISO 27002 2022 | 8.24 |
| ISO 27017 2015 | 10.1.2 |
| ISO 27018 2025 | 8.24 |
| NIST 800-53 R4 | SC-12(1) |
| NIST 800-53 R5.2 | SC-12(01) |
| NIST 800-53B R5 (high) (source) | SC-12(01) |
| NIST 800-82 R3 | SC-12(01) |
| NIST 800-82 R3 HIGH OT Overlay | SC-12(01) |
| NIST 800-171 R3 (source) | 03.13.10 |
| NIST 800-171A R3 (source) | A.03.13.10[02] |
| PCI DSS 4.0.1 (source) | 2.3.2 3.6.1 3.7.5 |
| PCI DSS 4.0.1 SAQ B-IP (source) | 2.3.2 |
| PCI DSS 4.0.1 SAQ C (source) | 2.3.2 |
| PCI DSS 4.0.1 SAQ C-VT (source) | 2.3.2 |
| PCI DSS 4.0.1 SAQ D Merchant (source) | 2.3.2 3.6.1 3.7.5 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 2.3.2 3.6.1 3.7.5 |
US (1)
| Framework | Mapping Values |
|---|---|
| USA Federal FedRAMP R5 (high) | SC-12(01) |
EMEA (4)
| Framework | Mapping Values |
|---|---|
| EMEA Germany C5 2026 | CRY-11.01B.3 CRY-16.01B CRY-16.02B |
| EMEA Spain CCN-STIC 825 | op.exp.10 mp.si.2 mp.info.3 |
| EMEA EU DORA RTS 2024 | Article 7.3 |
| EMEA EU NIS2 Annex 2024 | 9.2(c)(v) |
APAC (4)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2026 | ISM-0455 ISM-0462 |
| APAC Malaysia RMiT 2025 | 10.20(e) |
| APAC New Zealand NZISM 3.9 | 7.2.24.C.01 |
| APAC Singapore MAS TRM 2021 | 10.2.7 10.2.9 |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 2025 | 03.13.10 |
Capability Maturity Model
Level 0 — Not Performed
Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.
Level 1 — Performed Informally
SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.
Level 2 — Planned & Tracked
Cryptographic Protections (CRY) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with CRY domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with CRY domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with CRY domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Cryptographic management controls-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Cryptographic management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ Technology Assets, Applications and/or Services (TAAS) that store, process or transmit sensitive/regulated data use cryptographic mechanisms to prevent unauthorized disclosure of information as an alternate to physical safeguards.
Level 3 — Well Defined
Cryptographic Protections (CRY) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with CRY domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with CRY domain capabilities are well-documented and kept current by process owners. ▪ A security engineering team, or similar function, is appropriately staffed and supported to implement and maintain CRY domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of cryptographic protections operations (e.g., PKI management tool). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with CRY domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to ensure the availability of information in the event of the loss of cryptographic keys by individual users.
Level 4 — Quantitatively Controlled
Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.
Level 5 — Continuously Improving
Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.
Assessment Objectives
- CRY-10.3_A01 information availability is maintained in the event of the loss of cryptographic keys by users.
Technology Recommendations
Micro/Small
- Cryptographic governance program
Small
- Cryptographic governance program
Medium
- Cryptographic governance program
Large
- Cryptographic governance program
Enterprise
- Cryptographic governance program