Skip to content

Non-Repudiation

What is Non-Repudiation?

A security property that ensures a party cannot deny having performed an action, such as sending a message or authorising a transaction. Non-repudiation is typically achieved through digital signatures and audit trails.

Information Security

Each of these is named in at least one of the same controls as non-repudiation. The number is how many controls name both.

What the standards actually require on non-repudiation

Requirements naming non-repudiation across 6 standards, quoted from the control text.

Security Dimension 3 Non-Repudiation per X.805 Clause 6.3: Non-repudiation stops a person or entity from credibly denying that it carried out a given action on data, by keeping evidence of network-related actions available (for example evidence of an obligatio...

X805-Dim3-Non-Repudiation-Proof-Origin-Delivery-Sender-Receiver-Denial-Prevention · ITU-T X.805 Security Dimension 3 - Non-Repudiation + Proof of Origin + Proof of Delivery + Sender + Receiver Denial Prevention + Digital Signatures + Timestamping + Audit Logs + Forensic Evidence + Court-Admissible Records →

Maintain reviewer or releaser credentials within the established chain of custody for information reviewed or released.

NIST800-AU-10(3) · AU-10(3) Non-repudiation | Chain of Custody →
IEC 624432 controls

It shall be possible for the control system to establish whether a particular action was performed by a given human user. RE 1 extends non-repudiation to all users including software processes and devices. It applies from SL 3.

iec-62443::SR 2.12 · Non-repudiation →
API 11641 control

The plan must require risk-appropriate access non-repudiation protections and identity proofing, and the binding of assigned unique digital identities (non-shared accounts, tokens, session keys) to real-life identities;

api-1164::PR.AC-6 · PR.AC-6 Non-repudiation, identity proofing and binding of digital identities to real identities →

Accountability and non-repudiation. Implements CyFun PR.PT-1 / PR.AC-1: actions are attributable to individual users to provide accountability and non-repudiation.

BE-CF-32 · Accountability and non-repudiation →

The system provides irrefutable evidence that an individual, or a process acting for one, performed defined actions. 5 enhancements.

canada-itsp-10-033-security-and-privacy-controls-and-assurance-activities-catalogue::AU-10 · AU-10 Non-repudiation →

Questions people ask about non-repudiation

What is Non-Repudiation?
A security property that ensures a party cannot deny having performed an action, such as sending a message or authorising a transaction. Non-repudiation is typically achieved through digital signatures and audit trails.
Why is Non-Repudiation important for compliance?
Non-Repudiation is a key concept in Information Security. Understanding non-repudiation helps organizations meet regulatory requirements, reduce risk, and demonstrate due diligence during audits. Our compliance platform maps 1,016 frameworks with 316K cross-framework control mappings.
Which compliance frameworks address Non-Repudiation?
Non-Repudiation appears in the requirement text of ITU-T X.805 - Security Architecture for End-to-End Communications, NIST SP 800-53 Rev 5, IEC 62443, API 1164, Belgium CyberFundamentals. Across these standards we have identified 18 controls that name it directly, each linked to the control text on the compliance platform.
Where can I learn more about Non-Repudiation?
Explore our compliance framework pages to see how non-repudiation applies across different standards and regulations. Our implementation guides provide step-by-step guidance, and the compliance platform offers AI-powered analysis of how this concept maps across 1,016 frameworks.

See how Non-Repudiation applies across compliance frameworks

Our platform maps 1,016 frameworks with 316K cross-framework control mappings. Explore how this concept is addressed across standards.

Written and maintained by Gerard Blokdyk, The Art of Service.