QTS-04: Cryptographic Agility Risk Assessment (CARA)
Mechanisms exist to perform a Cryptographic Agility Risk Assessment (CARA) that analyzes Technology Assets, Applications, Services and Data (TAASD) to: (1) Identify TAASD most vulnerable to quantum-enabled cryptanalytic threats; and (2) Prioritize TAASD based on potential business impact.
Control Question: Does the organization perform a Cryptographic Agility Risk Assessment (CARA) that analyzes Technology Assets, Applications, Services and Data (TAASD) to: (1) Identify TAASD most vulnerable to quantum-enabled cryptanalytic threats; and (2) Prioritize TAASD based on potential business impact?
General (1)
| Framework | Mapping Values |
|---|---|
| NIST CSWP 39 | 5.0 |
EMEA (2)
| Framework | Mapping Values |
|---|---|
| EMEA Germany C5 2026 | CRY-01.03AC |
| EMEA EU DORA RTS 2024 | Article 6.4 |
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
Quantum Security (QTS) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with QTS domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Risk management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ IT and/or cybersecurity personnel use an informal process to identify, assess, remediate and report on quantum security-related risk.
Level 2 — Planned & Tracked
Quantum Security (QTS) 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 QTS domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with QTS domain capabilities are documented and maintained by process owners. ▪ Quantum security risk management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Risk management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
Level 3 — Well Defined
Quantum Security (QTS) 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 QTS 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 QTS domain capabilities are well-documented and kept current by process owners. ▪ A risk management team, or similar function, is appropriately staffed and supported to implement and maintain QTS domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of risk management operations (e.g., risk management solution, GRC platform and TPRM 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 QTS 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 perform a Cryptographic Agility Risk Assessment (CARA) that maps Technology Assets, Applications, Services and Data (TAASD) to: (1) Identify TAASD most vulnerable to quantum-enabled cryptanalytic threats; and (2) Prioritize TAASD based on potential business impact.
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
- QTS-04_A01 a Cryptographic Agility Risk Assessment (CARA) methodology is defined.
- QTS-04_A02 a CARA is performed to map Technology Assets, Applications, Services and Data (TAASD).
- QTS-04_A03 the CARA identifies TAASD most vulnerable to quantum-enabled cryptanalytic threats.
- QTS-04_A04 the CARA prioritizes TAASD based on potential business impact.
Evidence Requirements
- E-QTS-06 Cryptographic Agility Risk Assessment (CARA) Methodology
-
Documented evidence of a Cryptographic Agility Risk Assessment (CARA) methodology.
Quantum Security
Technology Recommendations
Micro/Small
- List where encryption is used (website TLS, VPN, email, backups) and note quantum-vulnerable algorithms (RSA, ECC)
Small
- Inventory of cryptographic algorithms in use
- Identification of quantum-vulnerable algorithms (RSA, ECDSA, DH)
Medium
- Structured CARA aligned to NIST guidance
- Asset-level mapping of cryptographic algorithm use
- Prioritization by business impact
Large
- Formal CARA process aligned to NIST IR 8547 or equivalent methodology
- Integration with risk register and PQC migration planning
Enterprise
- Enterprise CARA program with automated cryptographic discovery
- NIST IR 8547 methodology implementation
- Integration with GRC platform and PQC migration roadmap