Contents
StandardNIST

FIPS 186-5 (DSS)

Digital Signature Standard (DSS)

FIPS 186-5 is NIST’s Digital Signature Standard: the approved methods for creating and checking RSA, ECDSA, and EdDSA signatures (including Ed25519) so a receiver can detect tampering and confirm who signed.

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.

What it means for your discipline

  • CybersecurityCore

    You own which signature family, parameters, and hash a vehicle program may use, and you record that choice in the cybersecurity concept. Algorithm approval is the starting claim; module testing and key-handling evidence still have to be produced for the real ECU or backend.

  • HPC & application softwareCore

    Bootloaders, update agents, and security services call sign and verify on exact byte ranges. Your daily mistakes are hashing twice, covering the wrong image region, or pairing a padding mode or curve the signer did not use.

  • Base softwarePartial

    The crypto service stack must expose the chosen RSA, ECDSA, or EdDSA job with the right key element sizes and algorithm identifiers. You configure jobs and key storage; the security engineer still owns whether that algorithm is approved.

  • Hardware & siliconPartial

    HSMs and secure elements generate keys and compute signatures without exporting the private key. You confirm the silicon or firmware actually implements the scheme and curve the software will request.

  • Software update & OTAPartial

    Package authenticity rests on a signature the vehicle can verify with a provisioned trust anchor. You align the signing backend, the metadata that names the algorithm, and the verifier in the update agent.

  • Networks & communicationPartial

    TLS and other authenticated sessions rely on certificates whose signatures must use an approved scheme. You match the certificate profile to what the ECU stack verifies, rather than treating the signature algorithm as an interchangeable detail.

  • E/E architecturePartial

    You place trust anchors, signing roles, and verification points (boot, update, diagnostics, backend) so each uses a scheme both ends implement. The standard does not decide the E/E topology; it constrains the algorithms on those paths.

  • Diagnostics & lifecyclePartial

    Certificate-based diagnostic authentication fails closed when the tester certificate uses a scheme or curve the ECU does not verify. You keep tester PKI and in-vehicle trust stores on the same approved algorithms.

  • Functional safetyPartial

    Safety cases often rely on a signature check to show that safety-related software was not swapped. FIPS 186-5 does not replace ISO 26262; it only defines the signature math that check may use.