ASD ISM 1995 Use ML-KEM for secure key encapsulation
What it says
When using ML-KEM for encapsulating encryption session keys (and similar keys), ML-KEM-768 or ML-KEM-1024 is used, preferably ML-KEM-1024.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishEnsure encryption keys are protected using recommended ML-KEM-768 or ML-KEM-1024 methods.
Using strong methods to protect digital keys that encrypt your data is crucial. If these keys aren't properly secured, your sensitive information could be exposed to hackers, leading to data breaches, financial loss, or damage to your reputation. This control ensures you use the best available methods to keep your encryption keys safe.
Free. Save your status, tasks and notes.
Why it matters
Using weaker or non-approved KEMs instead of ML-KEM-768/1024 can enable session key compromise, exposing encrypted data and services.
How to implement
The IT team should ensure that ML-KEM-1024 is used for encrypting keys.
This involves updating any software or systems that still use older methods. They should start by identifying existing systems and consult with experts if needed to replace outdated practices.
Managers should schedule regular training sessions for their staff.
These sessions should explain the importance of using recommended methods like ML-KEM-1024 to protect digital keys. Managers should coordinate with the IT team to provide easy-to-understand training materials.
Procurement should ensure that any new encryption-related software purchased is compatible with ML-KEM-1024.
During purchasing, they should require vendors to confirm this compatibility and get written assurance.
The cyber security officer should create a policy that mandates the use of ML-KEM-1024 for all new projects.
This policy should be shared with all team leaders to ensure everyone is on the same page and avoids using weaker methods.
System owners should conduct a review of existing systems to identify where encryption keys are not secured using ML-KEM-1024.
They can create a checklist to systematically audit each system and liaise with IT to make necessary changes.
Keep it running
Verify key encapsulation uses ML-KEM-768 or preferably ML-KEM-1024, and block non-approved KEM parameter sets in crypto policies.
Evidence and audit
- Check 1 of 5What an auditor asks for
Ask for
The encryption method documentation: Request records showing what encryption techniques are employed across systems.
Look at
Mentions of ML-KEM-768 or ML-KEM-1024.
Good evidence
Has clear documentation showing ML-KEM-1024 as the standard method.
- Check 2 of 5What an auditor asks for
Ask for
To see recent training material: Request any slides, videos, or documents used to train staff on ML-KEM-1024.
Look at
Clear explanations and relevance to current practices.
Good evidence
Shows up-to-date material that staff can understand and apply.
- Check 3 of 5What an auditor asks for
Ask for
Procurement records: Request to see purchase orders or contracts with software vendors.
Look at
Clauses requiring ML-KEM-1024 compatibility.
Good evidence
Includes contracts specifying compliance with this standard.
- Check 4 of 5What an auditor asks for
Ask for
Policy documents: Request to see formal policies regarding encryption methods.
Look at
A mandate for ML-KEM-1024 use.
Good evidence
Has a signed policy dated recently with clear requirements.
- Check 5 of 5What an auditor asks for
Ask for
System review reports: Request evidence of the latest system audits for encryption key security.
Look at
Checklists or reports detailing current encryption methods.
Good evidence
Indicates thorough audits aligned with ML-KEM-1024 standards.
Mappings
Closest match in ISO/IEC 27001: A.8.24, Effective use of cryptography and key management, which this control partially meets.
ISO/IEC 27001: 1 mapping
This control partially meets A.8.24.
Annex A 8.24 requires organisations to define and implement rules for effective cryptography use and cryptographic key management. ISM-1995 specifies an approved post-quantum key encapsulation mechanism (ML-KEM-768/1024) for encapsulating session keys, which is one concrete cryptographic rule an organisation may mandate under Annex A 8.24. ISM-1995 is algorithm-specific, while Annex A 8.24 also covers broader key lifecycle requirements (generation, storage, rotation, revocation, recovery and governance).
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.