What it is
FIPS 186-5, the Digital Signature Standard (DSS), is the NIST publication that specifies how to generate and verify digital signatures with approved public-key algorithms. A valid signature tells the receiver that the signed bytes still match what was signed and that the signer used the private key matching a known public key. NIST wrote it for U.S. federal systems. Automotive programs use it as a clear, public list of signature algorithms when they protect electronic control units (ECUs), factory tools, and cloud backends.
The standard approves algorithms and the matching key-pair generation methods. That approval does not validate a product. A library, hardware security module (HSM), or ECU image can implement an approved algorithm and still be wrong because of key storage, encoding, or a missed check. Product claims belong to cryptographic-module requirements and to the tests you actually run.
Who it applies to
DSS applies wherever a policy requires NIST-approved digital signatures. On a vehicle program that is the cybersecurity engineer who selects the scheme, the software and basic-software engineers who invoke it, and the teams who sign software, calibration data, diagnostic credentials, or backend messages.
An OEM or supplier is not automatically required to follow FIPS. The obligation comes from a customer crypto specification, a federal or procurement rule, or an internal policy that points at NIST’s approved set. ISO/SAE 21434 and the UNECE vehicle-cybersecurity and software-update regulations require authenticity and integrity of software. They do not name this document as the only allowed signature standard.
What it covers
FIPS 186-5 specifies three signature families and how to generate keys for them.
| Family | Typical vehicle use | What must match on both sides |
|---|---|---|
| RSA signatures (PKCS #1 v1.5 and PSS) | Secure boot, update packages, certificates | Modulus size, padding mode, and hash |
| ECDSA | Certificates, boot and update, many V2X-style credentials | Curve and hash |
| EdDSA, including Ed25519 and Ed448 | Compact signatures where the stack supports Edwards curves | Curve, public-key format, and pure versus pre-hashed mode |
The finite-field Digital Signature Algorithm (DSA) from earlier editions of this standard is not specified here for new signatures. Hash functions are not defined in DSS. RSA and ECDSA signatures are computed over a hash from an approved hash standard (the Secure Hash Standard or SHA-3). EdDSA can sign the message itself or a pre-hash, and the two modes are not interchangeable.
DSS does not specify encryption, key agreement, message authentication codes, certificate formats (such as X.509), or how a private key is stored. Those choices sit in other NIST publications and in the vehicle security architecture.
How it fits with other documents
FIPS 186-5 supersedes FIPS 186-4. The previous edition specified DSA, RSA, and ECDSA. This edition keeps RSA and ECDSA, adds EdDSA, and no longer specifies DSA for generating signatures. Elliptic-curve parameter recommendations that accompany the revision are published separately (NIST SP 800-186). Rules for retiring older sizes and algorithms are transition guidance, not part of the algorithm text.
FIPS 140 sets requirements for cryptographic modules. An implementation can follow DSS and still fail module validation if roles, self-tests, or key protection are weak. AUTOSAR crypto-service interfaces can offer RSA, ECDSA, and EdDSA jobs; the AUTOSAR documents define the software interface, not the signature mathematics. Secure on-board communication in the vehicle mostly uses symmetric message authentication, so DSS shows up there mainly through certificates and provisioning, not through every frame.
In practice
Choose a scheme that the boot ROM, HSM, update agent, and signing backend all implement, then confirm it is still inside the approved set. RSA with PKCS #1 v1.5 remains common where a ROM only verifies that padding. PSS and Ed25519 are frequent choices for new designs when every verifier supports them. The signing service and the ECU must use the same padding, curve, hash, and encoding.
Verify over the same bytes the signer covered, including the metadata that is supposed to be protected. Hash the image once, in the step the scheme requires. Treat Ed25519 as EdDSA, not as a pre-hashed ECDSA signature. Fail closed on an unknown algorithm identifier.
Generate and keep private keys in an HSM or an equivalent controlled environment. The ECU only needs the public key or a trust anchor provisioned in a protected store. Write the scheme, size or curve, hash, and padding into the cybersecurity work product so a later variant does not change them quietly.
Approval of the algorithm still leaves room for implementation faults: bad range checks, reused one-time values in ECDSA, and loose parsing of signature encodings. Exercise the verifier with known-answer tests before production keys are used to sign software that vehicles will trust.