What it is
FIPS 205 is NIST’s standard for SLH-DSA, the Stateless Hash-Based Digital Signature Algorithm, standardized from SPHINCS+. It specifies key generation, signing, and verification for signatures whose security rests on cryptographic hash functions. An attacker, including one with a large quantum computer, has to break those hash functions in order to forge a signature.
Stateless means the signer stores no one-time secret that must change after every signature. In stateful hash-based schemes, reuse of that secret makes signatures forgeable. Reuse can follow a restore from backup, a key copied onto two production stations, or a second signature from an ECU image that still holds the old state. SLH-DSA derives each signature from the private key and the message only.
Signatures are much larger, and signing is slower, than with NIST’s lattice-based signature for general post-quantum use. In a vehicle, SLH-DSA suits a long-lived root or software signature when the security argument should rest on hash functions.
Who it applies to
It applies to people who specify, implement, or verify signatures that must remain trustworthy for the life of a key or a software image. Cybersecurity engineers own the algorithm choice. Software, basic-software, and hardware engineers meet it when a bootloader, crypto library, or security module must verify the signature. Update engineers meet it when a production or over-the-air package carries that signature for years.
OEMs, suppliers, and tool vendors are included once a project names SLH-DSA in a trust anchor or crypto catalog. Adoption is a project decision, recorded in a requirement or a profile. Safety, network, and diagnostic standards still govern their own work and use this document only when authenticity depends on a digital signature.
What it covers
The standard covers the SLH-DSA procedures, the hash functions they call, and parameter sets that trade signature size for signing speed at more than one security strength. Key and signature layouts are defined so two implementations can interoperate.
Factory provisioning, certificate and manifest formats, and AUTOSAR crypto-job configuration are specified in other documents.
| Topic | What FIPS 205 decides |
|---|---|
| Signing state | No one-time index to store or advance |
| Security basis | Cryptographic hash functions |
| Variants | Size-versus-speed parameter sets at several strengths |
| Outside scope | Protocols, certificates, provisioning, timing |
How it fits with other documents
NIST paired SLH-DSA with a lattice key-encapsulation mechanism and a lattice signature aimed at general use. The lattice signature is the usual choice when signature size and speed dominate. SLH-DSA is the choice when a trust anchor should rest on hash functions. LMS and XMSS, the stateful hash-based signatures, still fit a hardware security module that can enforce a monotonic counter. SLH-DSA removes that state-tracking duty from the signer.
ISO/SAE 21434 and the UN vehicle cybersecurity regulation require a cybersecurity process and risk treatment. Software-update regulation requires a controlled update path and integrity of the installed software. The crypto catalog, the secure-boot specification, and the update or certificate profile are the documents that cite FIPS 205 and lock the parameter set. Verifiers accept an SLH-DSA signature when that profile names the algorithm and the parameter set they implement.
In practice
Add SLH-DSA to the crypto catalog as an explicit option. On the ECU, reserve flash, RAM, and boot or update time for a large signature, and make sure transfer and package layouts can hold it intact. Keep signing on a controlled backend or production module. A stateless key can be backed up and restored because there is no one-time index to collide; the signing key still needs the same strict access control as any code-signing key.
Pin one parameter set, hash family included, in the trust-anchor record. A verifier set up for SHA-2 accepts the SHA-2 family; a SHAKE parameter set needs a SHAKE verifier. When a classical signature and SLH-DSA travel on the same artifact, follow the profile that states where each value sits and which checks must pass. Retest verification after every crypto-library or security-module update, because the parameter-set name is part of what the verifier accepts.