ASD ISM 1990 Prefer FIPS 140-3 validated ML-DSA and ML-KEM implementations
What it says
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
Where ML-DSA (FIPS 204) and ML-KEM (FIPS 203) are used, prefer implementations of each that hold FIPS 140-3 validation; validation is preferred, not required.
Where ML-DSA and ML-KEM are used, implementations of each with FIPS 140-3 validation are preferred. ML-DSA (FIPS 204) is a signature algorithm and ML-KEM (FIPS 203) a key encapsulation mechanism for sharing session keys, both post-quantum (built to resist attack by future quantum computers). Both standards treat FIPS 140-3 validation as a prerequisite: independent testing and certification of the cryptographic module, the hardware or software that performs the cryptography. The ISM prefers validation but does not require it, so an unvalidated implementation does not breach this control.
Free. Save your status, tasks and notes.
Why it matters
ML-DSA and ML-KEM are more complex to implement than traditional algorithms, so implementation mistakes are a real risk. Independent FIPS 140-3 testing of the module makes it less likely that such a flaw quietly weakens signatures or key exchange built on sound algorithms.
How to implement
Find every use of ML-DSA and ML-KEM.
Check certificates and code signing, TLS, SSH and VPN key exchange, hardware security modules and libraries in your software, using cryptographic bills of materials where suppliers provide them. Record the implementation and version behind each, and confirm it follows FIPS 204 or FIPS 203, not a pre-standard version (Dilithium or Kyber).
Check each implementation's FIPS 140-3 status.
Look up its certificate on the official list of validated modules, not a vendor's claim. Confirm the certificate lists ML-DSA or ML-KEM as approved and covers the version and platform you run, and that the module runs in its approved mode. FIPS 140-2 certificates and 'in process' listings do not count.
Favour validated modules when buying or building.
Ask vendors for FIPS 140-3 certificate numbers covering ML-DSA and ML-KEM when buying the new cryptographic equipment, applications and libraries that ISM-1917 requires to support ML-DSA-87 and ML-KEM-1024 by 2030. In your own software, use a validated library build and run it in its approved mode.
Record each unvalidated implementation and why it stays.
Typical reasons are no validated module for that platform yet, or a bought service whose provider has none. Validation does not replace the products evaluated against an ASD-endorsed Protection Profile (ISM-0457, ISM-0465) or the High Assurance Cryptographic Equipment (ISM-0460, ISM-0467) that some uses require.
Keep it running
Recheck an implementation's validation whenever it is upgraded, because a certificate covers specific versions, and when its certificate moves to the historical list. Revisit each unvalidated choice when a validated module becomes available for that platform.
Evidence and audit
- Check 1 of 3What an auditor asks for
Ask for
The list of ML-DSA and ML-KEM implementations, and an independent source such as cryptographic bills of materials or a scan of TLS, SSH and VPN settings.
Look at
Whether every use the independent source shows is on the list, with its implementation, version and FIPS 140-3 status.
Good evidence
Every ML-DSA and ML-KEM use found is listed with its implementation, version and FIPS 140-3 status, and each follows FIPS 204 or FIPS 203 rather than a pre-standard version.
- Check 2 of 3What an auditor asks for
Ask for
The FIPS 140-3 certificate claimed for each sampled implementation, with its deployed version and configuration.
Look at
Whether the certificate is on the official list, names ML-DSA or ML-KEM as approved and matches the deployed version and platform, and whether the module runs in its approved mode.
Good evidence
Each claimed validation is a FIPS 140-3 certificate on the official list covering ML-DSA or ML-KEM for the deployed version and platform, the module runs in its approved mode, and no vendor statement, FIPS 140-2 certificate or 'in process' listing is counted as validation.
- Check 3 of 3What an auditor asks for
Ask for
The purchase and design records for products and software that use ML-DSA or ML-KEM.
Look at
Whether FIPS 140-3 validation was considered, and the reason given wherever an unvalidated implementation was chosen.
Good evidence
Each record shows FIPS 140-3 validation was considered, and each unvalidated choice gives a reason, such as no validated module for that platform, so the preference was weighed rather than ignored.
Mappings
Closest match in ISO/IEC 27001: A.8.24, Use of cryptography, which this control partially meets.
ISO/IEC 27001: 1 mapping
This control partially meets A.8.24.
Annex A 8.24 covers defining and implementing rules for the effective use of cryptography, including cryptographic key management, across every algorithm an organisation uses. ISM-1990 is one specific case within that scope, stating a preference for FIPS 140-3 validated implementations when ML-DSA and ML-KEM are used, as set out in FIPS 204 and FIPS 203.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




