eXtended Merkle Signature Scheme, or XMSS, is a hash-based digital signature scheme. It uses one-time signatures organised under a Merkle tree, which gives post-quantum security for signing firmware, software and other objects, but each private key state must be managed carefully to avoid signature reuse.
What XMSS Is Used For
XMSS is a stateful, hash-based digital signature scheme designed for post-quantum signing of firmware, software and other objects. It is best understood as a way to sign data with one-time signatures arranged in a Merkle tree, where the security model depends on never reusing a one-time key state.
That makes XMSS especially relevant where long-lived signing trust matters, such as code signing and secure boot. Its value is not just that it resists quantum attacks better than many classical signature schemes, but that it also changes how teams must manage signing state, key ceremonies and recovery procedures.
How XMSS Works
XMSS combines one-time signatures with a Merkle tree to let one private key sign multiple messages across a bounded set of uses. Each signature consumes a unique one-time leaf, and the tree root binds those leaves into a single public verification key. This is why XMSS is called stateful: the signer must track which one-time keys have already been used.
That statefulness is the central design trade-off. It gives strong security properties from hash-based primitives, but it also introduces operational discipline that is uncommon in many classical signing workflows. If the signer loses state, restores an old backup, or signs twice with the same leaf, the scheme's assumptions are undermined.
Where XMSS Fits in Post-Quantum Signing
XMSS sits in the broader post-quantum cryptography migration landscape, especially for organisations planning for firmware and software signing. It is most useful where verifiers need a conservative, well-understood signature primitive and where the signing process can be tightly controlled. NHIMG's Post-Quantum Cryptography Migration Guide is the best starting point for understanding how XMSS fits into a wider migration roadmap.
For code-signing use cases, XMSS is not just a cryptographic choice, it is an architectural choice. Teams need inventory of what is being signed, where the signing keys live, how signing state is protected, and whether the environment can tolerate a stateful signer. NHIMG's PQC Code Signing Guide covers those operational constraints, including HSM state management and boot ROM verification limits.
Operational Constraints and Verification
XMSS is not a drop-in replacement for every signature workflow. It is most practical when signing volume, recovery processes and trust boundaries are already well controlled. If the signing process depends on easy cloning, frequent rollback, or loosely governed key handling, the state requirement becomes a major risk factor rather than a minor implementation detail.
Verification is comparatively straightforward because the public verification key does not carry the same state burden as the signer. The hard part is protecting the signer's sequence of one-time uses, preserving continuity across failover, and ensuring the operational environment does not create accidental reuse. For readers who want a refresher on the underlying primitives, NHIMG's Cryptography Basics Guide helps connect XMSS to hash functions, digital signatures and Merkle-tree construction.
Risk and Threat Considerations
XMSS is secure only if its signing state is never reused. The main risk is not a classical break of the hash functions, but an operational failure that causes the same one-time signature material to sign more than once, which can expose the private key structure and weaken future signatures.
Failure mechanism: Backup restore, parallel signers, failover mistakes or unsynchronised state tracking can cause leaf reuse. That is especially dangerous in firmware and software signing pipelines where an unnoticed duplicate signature may survive for a long time.
Impact: A reused XMSS state can undermine trust in signed code, force key replacement, and create a broad remediation burden because every object signed under the compromised signing state may need review.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5, NIST SP 800-57 and NIST CSF 2.0 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | XMSS state must be controlled like sensitive signing authenticator material. |
| SC-12 — Cryptographic Key Establishment and Management | XMSS is a signing scheme whose security depends on disciplined cryptographic lifecycle management. | |
| SC-13 — Cryptographic Protection | XMSS is a cryptographic integrity mechanism used to protect signed objects. | |
| Recommendation — Protect signing state, rotate or revoke compromised material, and prevent duplicate use. Manage XMSS signing keys and state through controlled generation, storage, rotation and recovery. Use approved cryptographic protection for signed firmware and software artifacts. | ||
| NIST SP 800-57 | Key Management | XMSS depends on careful key and state lifecycle handling for secure signing. |
| Recommendation — Define cryptoperiods, state backup rules and recovery procedures for the signer. | ||
| NIST CSF 2.0 | PR.DS-1 — Data-at-Rest Is Protected | Signed firmware and software objects rely on cryptographic protection of integrity and authenticity. |
| Recommendation — Protect signing artifacts and associated state against tampering and unauthorized disclosure. | ||
| ISO/IEC 27001:2022 | A.8.24 — Use of cryptography | XMSS is a cryptographic control used to provide signed-object integrity and authenticity. |
| Recommendation — Specify approved cryptographic signing methods and govern their operational use. | ||
Practitioner Guidance
Why practitioners should care: XMSS is attractive when post-quantum signing assurance matters, but it shifts security effort from algorithm selection to lifecycle control. The signer's state becomes part of the security boundary, so ownership, recovery and auditability need to be explicit.
What to watch for: Treat backup and restore design, HSM state handling, multi-writer access and disaster recovery testing as core signing controls, not implementation details. If the operational model cannot prove unique use of each one-time signature state, XMSS is a poor fit for that deployment.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org