Skip to content
Log inRegister

NIST Finalises IR 8547: Your Cryptographic Inventory Is Now the Critical Path

Dr. Abeer Alshammari · Published 11/7/2026

IntermediateProfessionalsCISOsExecutives

On 27 October 2026 NIST announced the final version of NIST IR 8547, its roadmap for moving from quantum-vulnerable public-key cryptography to the post-quantum standards. Most coverage has focused on the dates. For a governance team the more useful question is about sequence: what has to exist before any date can be met.

What NIST actually says

NIST describes the report as a high-level roadmap, not a list of formal requirements. It identifies quantum-vulnerable algorithms in NIST's existing standards and sets out a transition plan for them, and it states that the plan supports the timelines in Executive Order 14412. Under that order, federal high-value assets and high-impact systems are to migrate key establishment by 2030 and digital signatures by 2031. The wider 2035 target for federal systems comes from National Security Memorandum 10.

The report asks organisations to plan around two possible futures for any given algorithm: it may be disallowed in federal systems after a certain date, or it may remain usable at the user's own risk. It also points to the whole cryptographic supply chain, not only the systems you run yourself.

A note on the finer detail

Secondary analyses, including a Cloud Security Alliance research note, report more specific terms: that RSA, ECDSA, EdDSA and finite-field and elliptic-curve Diffie-Hellman are deprecated after 2030 and disallowed after 2035, and that ML-KEM-768 is the recommended default parameter set. I could not confirm those specifics against NIST's own text, and the CSA note itself flags an inconsistency in how key sizes are scoped. Treat them as likely, and read the primary document before writing them into policy.

Why the inventory comes first

Nobody can migrate what they cannot find. Public-key cryptography sits in TLS termination, VPNs, SSH, code signing, certificate authorities, identity providers, hardware security modules and embedded firmware, and a good share of it sits inside vendor products where it is invisible to you. A cryptographic inventory turns the statement "we use encryption" into a register: which algorithm, which key size, which system, which owner, how long the protected data must stay confidential, and who is able to change it. Vendors are increasingly being asked for a cryptographic bill of materials (CBOM) for exactly this reason.

Prioritise by data lifetime, not system size

The driving threat is "harvest now, decrypt later": an adversary records encrypted traffic today and waits for a capable quantum computer. Risk therefore follows how long confidentiality must last. Health records, legal files, identity data, state secrets and intellectual property with a 15 or 20 year horizon matter more than ordinary session traffic. NIST's guidance points toward prioritising sensitive, long-lived data, possibly by moving to FIPS 203 (ML-KEM) first, and toward evaluating hybrid approaches that pair conventional and post-quantum algorithms. Hybrids are the more conservative choice, at the cost of extra computation.

Signatures are a different problem. A forged signature only matters if a verifier still trusts it, so the urgent items are long-lived roots of trust, firmware signing keys and code-signing certificates. Those are the hardest to replace once devices are in the field.

The supply chain is the control surface

Most organisations will receive post-quantum protection through their vendors rather than build it. That makes procurement a security control. Ask critical suppliers for a dated post-quantum roadmap. Distinguish between a capability that is "supported" and one that is "enabled by default". Write crypto-agility into contracts, so an algorithm can be swapped without a platform rebuild, and ask for CBOM data where it is available.

A practical sequence for the next quarter

First, name an owner and put quantum-vulnerable cryptography on the risk register with a review date. Second, run discovery across network, application and vendor layers, and accept that the first pass will be incomplete. Third, classify what you find by data lifetime and replacement difficulty. Fourth, send the supplier questions above to your ten most critical vendors. Fifth, pilot hybrid key establishment on one external-facing service, so the team learns the operational cost before it is urgent. Sixth, set internal milestones. Organisations outside the federal sphere are not bound by the executive order, but the 2030 to 2035 window is a defensible planning anchor, particularly for long-lived data.

The dates will keep moving at the edges. The inventory will not become less necessary. A team that can answer "where is our RSA, and who owns it?" in an afternoon is ready for whichever timeline is finally adopted.

This article is general information, not legal advice. NIST IR 8547 and Executive Order 14412 are the authoritative sources; check them against your own obligations.

Try it yourself

An interactive CyberAbeer experience for this topic is in development.

Coming soon
Back to insights