In general,
non-repudiation involves associating actions or changes with a unique individual. For example, a secure area may use a
key card access system where non-repudiation would be violated if key cards were shared or if lost and stolen cards were not immediately reported. Similarly, the owner of a computer account must not allow others to use it, such as by giving away their password, and a policy should be implemented to enforce this.
In digital security In
digital security, non-repudiation means: • A service that provides proof of the
integrity and
origin of data. • An authentication that can be said to be genuine with high confidence. • An authentication that the data is available under specific circumstances, or for a period of time: data availability. Proof of data integrity is typically the easiest of these requirements to accomplish. A data
hash such as
SHA2 usually ensures that the data will not be changed undetectably. Even with this safeguard, it is possible to tamper with
data in transit, either through a
man-in-the-middle attack or
phishing. Because of this, data integrity is best assessed when the recipient already possesses the necessary verification information, such as after being
mutually authenticated. The common method to provide non-repudiation in the context of digital communications or storage is
Digital Signatures, a more powerful tool that provides non-repudiation in a
publicly verifiable manner.
Message Authentication Codes (MAC), useful when the communicating parties have arranged to use a shared secret that they both possess, does not give non-repudiation. A misconception is that encrypting, per se, provides authentication "If the message decrypts properly then it is authentic", which is not the case. MAC can be subject to several types of attacks, like: message reordering, block substitution, block repetition, .... Thus just providing message integrity and authentication, but not non-repudiation. To achieve non-repudiation one must trust a service (a certificate generated by a trusted third party (TTP) called certificate authority (CA)) which prevents an entity from denying previous commitments or actions (e.g. sending message A to B). The difference between MAC and
Digital Signatures, one uses symmetric keys and the other asymmetric keys (provided by the CA). Note that the goal is not to achieve confidentiality: in both cases (MAC or digital signature), one simply appends a tag to the otherwise plaintext, visible message. If confidentiality is also required, then an
encryption scheme can be combined with the digital signature, or some form of
authenticated encryption could be used. Verifying the digital origin means that the certified/signed data likely came from someone who possesses the private key corresponding to the signing certificate. If the key used to digitally sign a message is not properly safeguarded by the original owner, digital forgery can occur. ==Trusted third parties (TTPs)==