What Is Non-Repudiation?

Non-repudiation, also written non repudiation, is a security service that prevents a party from credibly denying having performed an action, such as originating a message, approving a transaction, or receiving a delivery. NIST defines it in its glossary as protection against an individual falsely denying having performed a particular action, providing the capability to determine whether a given individual created information, sent a message, approved information, or received a message. It builds on data integrity and origin authentication but adds a distinct requirement: the evidence must be verifiable by a third party who was not present when the action occurred, and who does not trust either of the parties involved.

That third-party requirement is what separates non-repudiation from ordinary authentication. A message authentication code proves to a recipient that a message came from someone holding the shared key, but because the recipient holds that same key, the recipient could have forged the message. Symmetric techniques therefore cannot support non-repudiation on their own.

The Cryptographic Basis

Digital signatures supply the asymmetry that non-repudiation needs. A signer generates a signature using a private key that only the signer holds, and anyone with the corresponding public key can verify it. Since verification does not require the ability to sign, a verifier cannot manufacture a signature that a judge or auditor would accept. NIST specifies the approved algorithms in FIPS 186-5, the Digital Signature Standard, which covers RSA signatures, the Elliptic Curve Digital Signature Algorithm, and the Edwards-Curve Digital Signature Algorithm.

The cryptographic guarantee is narrow and precise: it binds the signature to the key, not to a person. Turning key-level evidence into person-level evidence requires a public key infrastructure that binds a public key to an identity through a certificate issued by a certification authority, together with a registration process that verified the identity, and controls that keep the private key under the signer's exclusive control. Hardware security modules, smart cards, and secure elements exist largely to make the claim of exclusive control defensible.

Timestamps, Evidence, and Trusted Third Parties

Signature evidence decays over time. Keys are revoked, certificates expire, and hash functions weaken. A signature that verified in 2010 may be unverifiable or untrustworthy a decade later unless the moment of signing is fixed. Trusted timestamping services solve this by signing a hash of the document together with an authoritative time value, establishing that the signature existed before a given instant and therefore before any revocation. Long-term archival formats extend this with periodic re-timestamping under fresh algorithms and by embedding the revocation status information gathered at validation time.

Delivery-side services address the reciprocal problem. Non-repudiation of receipt requires the recipient to return a signed acknowledgment, and fair exchange protocols use a trusted third party or a gradual release mechanism so that neither side can obtain the other's evidence without surrendering its own. The Internet Security Glossary, Version 2 published as RFC 4949 catalogs these variants alongside the related services of data origin authentication and accountability. Secure audit logs, append-only ledgers, and blockchain records serve a similar function for sequences of actions rather than single messages.

Limits of the Guarantee

The service is evidentiary rather than absolute. A signer whose private key was stolen genuinely did not authorize the signature, so legal frameworks including the eIDAS regulation in the European Union and electronic signature statutes elsewhere allocate the burden of proof rather than declaring signatures irrebuttable. Key compromise, coerced signing, malware that alters a document between display and signature, and weak identity proofing at enrollment all break the chain between the mathematics and the person. Security engineers accordingly treat non-repudiation as a property of a whole system: cryptography, key management, device integrity, identity verification, and record retention together.

Applications

Non-repudiation has applications in a range of fields, including:

• Electronic contracts and digital signature platforms
• Financial transaction authorization and interbank messaging
• Code signing and software supply chain attestation
• Secure email and document exchange under S/MIME or comparable schemes
• Regulatory audit trails and records management
• Electronic health record access logging
• Certificate transparency and public ledger systems