ASD ISM 1990Prefer FIPS 140-3 Validated ML-DSA and ML-KEM Implementations
Official control statement
When using ML-DSA and ML-KEM, as per FIPS 204 and FIPS 203 respectively, adherence to pre-requisite FIPS 140-3 validation is preferred.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
When using the post-quantum algorithms ML-DSA (FIPS 204) and ML-KEM (FIPS 203), prefer implementations that meet the pre-requisite FIPS 140-3 validation.
What this means in practice
This control means that when your organisation deploys the post-quantum cryptographic algorithms ML-DSA (defined in FIPS 204) and ML-KEM (defined in FIPS 203), you should prefer implementations that have met the pre-requisite FIPS 140-3 validation. FIPS 140-3 validation confirms that a cryptographic module has been independently tested against a recognised security standard. Choosing validated implementations gives you assurance that these newer quantum-resistant algorithms are built and operating correctly, reducing the risk of weaknesses in how the cryptography is put into practice.
Framework
ASD Information Security Manual (ISM)
Control effect (Control Stack)
Proactive
Classifications
NC, OS, P, S, TS
ISM last updated
Mar 2026
Control Stack last updated
29 Sept 2026
E8 maturity levels
N/A
Guideline
Guidelines for cryptographySection
Cryptographic algorithmsTopic
Using post-quantum cryptographic algorithms
Why it matters
Without preferring FIPS 140-3 validated implementations, ML-DSA and ML-KEM may be deployed with unverified cryptography, undermining the protection these post-quantum algorithms are meant to provide.
Operational notes
Recheck CMVP listings periodically, as FIPS 140-3 validations and the availability of validated ML-DSA and ML-KEM modules change over time.
Implementation tips
- Have your cryptography or platform team confirm that any product or library offering ML-DSA or ML-KEM carries a current FIPS 140-3 validation before selecting it.
- Check the NIST Cryptographic Module Validation Program (CMVP) listings to verify the FIPS 140-3 validation covers the exact module and version you plan to deploy.
- Update procurement and product selection criteria so that FIPS 140-3 validated ML-DSA and ML-KEM implementations are preferred over unvalidated ones.
- Configure systems to use ML-DSA in line with FIPS 204 and ML-KEM in line with FIPS 203, disabling any non-conforming modes or parameters.
- Maintain an inventory of where ML-DSA and ML-KEM are used and record the FIPS 140-3 validation status of each implementation so validated options can be prioritised.
Audit / evidence tips
- AskAsk which systems and services use the ML-DSA and ML-KEM algorithms.Look atA cryptographic inventory or asset register showing where post-quantum algorithms are deployed.GoodA current inventory that identifies each system using ML-DSA or ML-KEM and the specific implementation or module in use.
- AskAsk for evidence that the deployed ML-DSA and ML-KEM implementations meet FIPS 140-3 validation.Look atFIPS 140-3 validation certificates and CMVP listings for the modules in use.GoodCurrent FIPS 140-3 validation records that match the exact module and version deployed.
- AskAsk how the organisation selects cryptographic products that provide these post-quantum algorithms.Look atProcurement or product selection criteria and vendor evaluation records.GoodDocumented criteria that give preference to FIPS 140-3 validated ML-DSA and ML-KEM implementations.
- AskAsk how ML-DSA and ML-KEM are configured to conform to FIPS 204 and FIPS 203.Look atSystem or application cryptographic configuration and settings.GoodConfiguration showing ML-DSA used as per FIPS 204 and ML-KEM as per FIPS 203 with conforming parameters.
- AskAsk what the organisation does when a FIPS 140-3 validated implementation is not yet available.Look atRisk decisions, exception records or roadmaps for adopting validated modules.GoodA documented rationale and a plan to move to a FIPS 140-3 validated implementation once one is available.
Cross-framework mappings
How ISM-1990 relates to controls across ISO/IEC 27001, ISO/IEC 42001, Essential Eight, and ASD ISM.
ISO 27001
| Control | Notes | Details |
|---|---|---|
layersPartially meets(1)expand_less | ||
| Annex A 8.24 | ISM-1990 requires that when implementing ML-DSA and ML-KEM, organisations should also follow the pre-requisite FIPS publications referenc... | |
These mappings show relationships between controls across frameworks. They do not imply full equivalence or certification.
Related ASD ISM controls in Cryptography
See all Guidelines for cryptography controls, or browse the full ASD ISM library.