Skip to main content
Commerce Security Authority
Category: Cryptography Fundamentals

FIPS 186-4 (Digital Signature Standard)

Also known as: DSS, Digital Signature Standard, FIPS 186-4
Simply put

FIPS 186-4 is a U.S. government standard that defines approved methods for creating and checking digital signatures, which are used to confirm that a message or document is genuine and has not been altered. Unlike a handwritten signature, a digital signature is generated by a mathematical algorithm. This version specifies three signature techniques: DSA, ECDSA, and RSA.

Formal definition

FIPS 186-4, the Digital Signature Standard (DSS), specifies algorithms for applications requiring a digital signature rather than a written signature, and defines three techniques for the generation and verification of digital signatures: DSA, ECDSA, and RSA. Digital signatures produced under this standard are intended to help detect unauthorized modifications to data and to support authentication of the signer. Readers should note that FIPS 186-4 has been succeeded by FIPS 186-5 (finalized February 3, 2023), which specifies a revised suite of signature-generation algorithms; the applicable version should be confirmed against the current published standard.

Why it matters

Digital signatures are foundational to trust in payment and commerce systems. They provide a mathematical means to confirm that a message, certificate, or software artifact is genuine and has not been altered in transit or at rest. FIPS 186-4 matters because it defines U.S. government-approved techniques (DSA, ECDSA, and RSA) for generating and verifying those signatures, giving practitioners a common, validated reference for interoperable and defensible cryptographic implementations. Where regulatory or contractual obligations call for FIPS-approved algorithms, referencing the correct standard version is essential to compliance and to the assurance that signatures will be accepted across systems.

For security and compliance teams, the standard is relevant to any control that depends on integrity and authenticity rather than confidentiality alone, such as verifying signed code, validating certificate chains, or authenticating the origin of exchanged data. A digital signature is intended to help detect unauthorized modification and to support authentication of the signer, but it does not by itself provide encryption or guarantee that keys are managed correctly; its effectiveness depends on sound key generation, protection, and lifecycle management.

Readers should also note that FIPS 186-4 has been succeeded by FIPS 186-5, which was finalized on February 3, 2023 and specifies a revised suite of signature-generation algorithms. Because approved algorithm sets and their status can change over time, teams should confirm the applicable version against the current published standard rather than assuming FIPS 186-4 remains current for a given use case.

Who it's relevant to

Security Engineers
Engineers implementing or reviewing signing and verification functions rely on FIPS 186-4 to identify approved techniques (DSA, ECDSA, RSA) and to ensure integrity and signer-authentication controls are built on a recognized standard. They should confirm whether FIPS 186-4 or its successor FIPS 186-5 applies to their design and validate key management around the signature scheme.
Compliance Officers
Where obligations call for FIPS-approved algorithms, compliance teams need to reference the correct Digital Signature Standard version. Because FIPS 186-4 has been succeeded by FIPS 186-5 (finalized February 3, 2023), officers should confirm the applicable version against the current published standard rather than assuming a fixed reference remains current.
Payment Processors and Acquirers
Organizations that verify signed data, certificates, or software artifacts benefit from understanding which signature techniques are approved and how a valid signature supports detection of unauthorized modification and authentication of the signer. They should treat digital signatures as an integrity and authenticity control, distinct from encryption, and manage keys accordingly.

Inside DSS

Digital Signature Standard scope
FIPS 186-4 is a U.S. federal standard published by NIST that specifies approved algorithms for generating and verifying digital signatures. It defines the mechanics of signature schemes rather than governing payment card data storage, and is a separate document from PCI DSS and the PCI Software Security Framework.
Approved signature algorithms
The standard specifies digital signature algorithms including DSA, RSA-based signatures (by reference to other specifications), and ECDSA. It describes the algorithm families that may be used to produce and verify signatures under the standard.
Key pair generation
FIPS 186-4 addresses generation of the public and private key pairs used in the signature schemes, including domain parameter generation and validation for the applicable algorithms. Signing uses the private key; verification uses the corresponding public key.
Random number and entropy requirements
The standard relies on properly generated random values (for example per-signature secret values in DSA and ECDSA), which require an approved random bit generator. Weak or reused random values can compromise signing keys, so entropy sourcing is treated as integral to secure use.
Relationship to hash functions
Digital signatures under this standard are computed over a message digest produced by an approved hash function specified in a separate NIST standard (the Secure Hash Standard). The signature scheme and the hash function are distinct components that operate together.
Role in integrity and authenticity, not confidentiality
Digital signatures are intended to support data integrity, authentication of origin, and non-repudiation. They do not provide confidentiality; encryption, tokenization, truncation, and masking address data protection concerns separately and are not substitutes for signatures.

Common questions

Answers to the questions practitioners most commonly ask about DSS.

Does FIPS 186-4 provide encryption for cardholder data?
No. FIPS 186-4, the Digital Signature Standard, specifies mechanisms for generating and verifying digital signatures, not for encrypting data. It addresses data integrity and authenticity of a signed message, not confidentiality. If you need to render cardholder data unreadable in storage, you would look to encryption, truncation, tokenization, or hashing under the relevant PCI DSS requirements, and confirm the applicable control and validation against the current published standard. Do not treat a digital signature standard as a substitute for encryption of stored account data.
Is FIPS 186-4 a PCI standard that governs how I protect payments?
No. FIPS 186-4 is a U.S. federal standard published by NIST, not a PCI Security Standards Council document. It is separate from PCI DSS, PA-DSS, the PCI Software Security Framework, PCI PIN, PCI P2PE, and PCI 3DS. A PCI standard or an implementation may reference approved cryptographic algorithms, and FIPS 186-4 may be relevant where digital signatures are used, but the obligation to apply a given control comes from the applicable PCI standard, not from FIPS 186-4 itself. Confirm which standard governs your specific control against its current published text.
Which digital signature algorithms does FIPS 186-4 cover?
FIPS 186-4 specifies approaches for digital signature generation and verification, including RSA-based, DSA-based, and elliptic-curve-based (ECDSA) signature methods, along with associated key-generation and parameter requirements. When selecting an algorithm for an implementation, confirm the specific mechanisms, key sizes, and any deprecations against the current published version of the standard and any superseding NIST guidance rather than assuming a fixed set.
How does FIPS 186-4 relate to key management in a payment environment?
FIPS 186-4 addresses key-pair generation and parameters used for digital signatures, but broader key-management practices such as secure generation, distribution, storage, rotation, and destruction are governed by your applicable requirements and supporting guidance. In a payment context, confirm cryptographic and key-management obligations against the current PCI DSS text and, where relevant, PCI PIN or PCI P2PE requirements, and treat FIPS 186-4 as one input to algorithm and parameter selection rather than a complete key-management framework.
Where might digital signatures based on FIPS 186-4 appear in a transaction flow?
Digital signatures can support integrity and authenticity in areas such as code signing, message authentication between systems, certificate issuance, and verification of firmware or software. Note that EMV chip authentication, 3-D Secure, strong customer authentication, and multi-factor authentication address different risks at different points in a transaction and are not interchangeable with a general digital signature standard. Identify the specific control you are implementing and the standard that governs it before assuming FIPS 186-4 applies.
How do I validate that an implementation conforms to FIPS 186-4?
Conformance to cryptographic standards is typically demonstrated through the relevant NIST validation programs and testing rather than by self-assertion. If a control in a payment environment depends on FIPS 186-4-based signatures, verify the algorithm, key parameters, and validation status against the current published standard and any applicable program requirements, and confirm how that control is assessed under the governing PCI standard rather than relying on the label alone.

Common misconceptions

FIPS 186-4 encrypts data or protects cardholder data at rest.
The standard specifies digital signature algorithms for integrity and authenticity, not encryption. It does not encrypt or otherwise render cardholder data unreadable. Protecting stored cardholder data and ensuring sensitive authentication data is not stored after authorization are governed by PCI DSS controls, which are separate from this standard.
Using a FIPS 186-4 digital signature is the same as tokenization or hashing for reducing PCI DSS scope.
Digital signatures serve a different purpose than tokenization, encryption, truncation, masking, or hashing, which reduce or transform data in different ways. A signature does not remove or obscure a PAN, and any effect on PCI DSS scope depends on the overall implementation and validation, not on the presence of a signature.
FIPS 186-4 is a payment or authentication standard like 3-D Secure or EMV chip authentication.
FIPS 186-4 is a NIST cryptographic algorithm standard and is distinct from payment-specific standards and from transaction authentication mechanisms such as EMV chip authentication, 3-D Secure, and strong customer authentication, which address fraud risks at different points in a transaction.

Best practices

Use only the digital signature algorithms and parameter choices approved in the current published version of the standard, and confirm requirements against the version in force rather than assuming fixed values.
Pair signature operations with an approved hash function as specified in the corresponding NIST hash standard, since the signature is computed over a message digest.
Source per-signature secret values and key material from an approved random bit generator with adequate entropy, as weak or reused random values can expose signing keys.
Treat digital signatures as controls for integrity, authenticity, and non-repudiation only, and apply separate mechanisms such as encryption or tokenization where confidentiality of data is required.
Do not rely on a digital signature to satisfy PCI DSS obligations for protecting stored cardholder data or for ensuring sensitive authentication data is not retained after authorization; validate those controls under PCI DSS separately.
Protect private signing keys throughout their lifecycle and verify signatures using validated public keys, keeping this cryptographic control distinct from transaction authentication measures like EMV, 3-D Secure, and multi-factor authentication.