QTS-09.3: Approved Post-Quantum Cryptography (PQC) Algorithm Use
Mechanisms exist to define: (1) Approved Post-Quantum Cryptography (PQC) algorithms, including asymmetric and symmetric algorithms; and (2) Required validation levels for approved algorithms (e.g., FIPS 140-3 validated).
Control Question: Does the organization define: (1) Approved Post-Quantum Cryptography (PQC) algorithms, including asymmetric and symmetric algorithms; and (2) Required validation levels for approved algorithms (e.g., FIPS 140-3 validated)?
APAC (1)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2026 | ISM-1990 ISM-1991 ISM-1992 ISM-1993 ISM-1994 ISM-1995 |
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:
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.
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 define: (1) Approved Post-Quantum Cryptography (PQC) algorithms, including asymmetric and symmetric algorithms; and (2) Required validation levels for approved algorithms (e.g., FIPS 140-3 validated).
Level 4 — Quantitatively Controlled
Quantum Security (QTS) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs). ▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs). ▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties. ▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review). ▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes. ▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.
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-09.3_A01 Post-Quantum Cryptography (PQC) algorithms are approved.
- QTS-09.3_A02 required validation levels for approved algorithms (e.g., FIPS 140-3 validated) are defined.
Evidence Requirements
- E-QTS-08 Approved / Deprecated Algorithm List
-
Documented evidence of an approved / deprecated algorithm list.
Quantum Security
Technology Recommendations
Micro/Small
- Monitor NIST PQC algorithm approvals (https://csrc.nist.gov/pqc)
- Adopt approved PQC algorithms as available in consumed services
Small
- Reference NIST PQC approved algorithms in cryptography policy
- NIST FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), FIPS 205 (SLH-DSA)
Medium
- Define approved PQC algorithm list
- NIST FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), FIPS 205 (SLH-DSA) adoption
- FIPS 140-3 validated module requirements
Large
- Formal approved PQC algorithm standard
- NIST FIPS 203/204/205 compliant implementations
- Required validation levels in cryptography policy
- Algorithm approval workflow for exceptions
Enterprise
- Enterprise approved PQC algorithm governance
- NIST FIPS 203/204/205 and CNSA 2.0 alignment
- Automated algorithm compliance enforcement
- Integration with cryptographic exception register