nonrepudiation
An assurance that the claimed sender or recipient is in fact the party who sent or received a given message.
nonrepudiation: proof that a transaction really happened
Nonrepudiation is a security property that makes it cryptographically impossible for a party to deny having sent or received a specific message, transaction, or instruction. In electrical engineering and industrial control systems, it serves as a defense against false claims: if a technician sends a command to shut down a critical process, that technician cannot later claim they never issued it. The assurance rests on digital signatures and authenticated encryption, not on trust or witness testimony.
The mechanism works through asymmetric cryptography. A sender signs a message using a private key that only they possess; recipients verify the signature using the sender's public key. Because only the private key can generate a valid signature for that specific message, the sender cannot credibly deny authorship without claiming their private key was compromised. In industrial systems, this is essential for audit trails in power distribution, manufacturing processes, and safety-critical operations where attribution matters legally and operationally.
Where nonrepudiation matters in practice
High-voltage dispatch centers, manufacturing execution systems, and smart grid controllers all rely on nonrepudiation to log commands and configuration changes. An operator who remotely modifies relay settings or authorizes equipment shutdown creates a signed record; disputes over whether the order was given can be resolved by examining the digital signature, which either validates or does not. Similarly, in SCADA systems and industrial IoT networks, nonrepudiation prevents an attacker who gained brief access from silently altering instructions and then claiming innocence.
The term itself reflects the legal and cryptographic double meaning: repudiation is the act of denying or disavowing something; nonrepudiation is the state of being unable to deny it. Unlike encryption, which protects confidentiality, nonrepudiation specifically addresses accountability. A message can be encrypted or plaintext; what matters for nonrepudiation is that its origin and integrity can be independently verified by a third party.
Implementation requires careful key management. If a private key is shared, stolen, or improperly secured, nonrepudiation fails. Industrial systems must store signing keys on hardware security modules or air-gapped systems, issue certificates with clear validity periods, and maintain revocation lists for compromised credentials. The strongest nonrepudiation also includes timestamps from a trusted time source, ensuring that a signed message cannot be antedated or postdated without detection.