Difference between revisions of "Non-repudiation"

From Clinfowiki
Jump to: navigation, search
 
(2 intermediate revisions by one user not shown)
Line 1: Line 1:
According to Baker and Cooper (1995), '''nonrepudiation''' functions provide evidence that a transaction or specific action actually happened.  An example is a system taking measures to ensure that a transferred message has been sent and received by the parties claiming to have sent and received the message. It is a way to guarantee that the sender of a message cannot later deny having sent the message and that the recipient cannot deny having received the message.  Non-repudiation is accomplished through functions such as electronic signatures, transmission encryption, or time stamping and transaction recording in an audit trail record (Maheu, et. al., 2001).
+
In digital security, '''nonrepudiation''' is a way to ensure that the sender of a message can’t deny having sent the message and that the recipient can’t deny the receipt of the message and provides the evidence that particular action has been taken [1].
  
== Sources ==
 
  
Baker, D. B., & Cooper, T. (1995). Information system security issues for health care. Manuscript in preparation, Science Applications International Corp. and Kaiser Permanente.
+
Non-repudiation provides protection against the false denial of having performed a particular action. Hence, it protects the sender against the false assertion of the receiver that the message has not been received and a receiver against the false assertion of the sender that the message has not been sent. It provides the capability to determine whether a given individual performed a particular action such as creating information, sending a message, approving information, and receiving a message. Non-repudiation is accomplished through functions such as electronic signatures, transmission [[encryption]], or time stamping and transaction recording in an audit trail record [2]. Nonrepudiation is often used for digital contracts, signatures and email messages.
Maheu, M., Whitten, P., and Allen, A. (2001) E-Health, Telehealth, and Telemedicine: A Guide to Startup and Success.  San Francisco: Jossey-Bass, p.120.
+
 
 +
 
 +
== References ==
 +
 
 +
# Baker, D. B., & Cooper, T. (1995). Information system security issues for health care. Manuscript in preparation, Science Applications International Corp. and Kaiser Permanente.
 +
# Maheu, M., Whitten, P., and Allen, A. (2001) E-Health, Telehealth, and Telemedicine: A Guide to Startup and Success.  San Francisco: Jossey-Bass, p.120.

Latest revision as of 00:41, 18 November 2012

In digital security, nonrepudiation is a way to ensure that the sender of a message can’t deny having sent the message and that the recipient can’t deny the receipt of the message and provides the evidence that particular action has been taken [1].


Non-repudiation provides protection against the false denial of having performed a particular action. Hence, it protects the sender against the false assertion of the receiver that the message has not been received and a receiver against the false assertion of the sender that the message has not been sent. It provides the capability to determine whether a given individual performed a particular action such as creating information, sending a message, approving information, and receiving a message. Non-repudiation is accomplished through functions such as electronic signatures, transmission encryption, or time stamping and transaction recording in an audit trail record [2]. Nonrepudiation is often used for digital contracts, signatures and email messages.


References

  1. Baker, D. B., & Cooper, T. (1995). Information system security issues for health care. Manuscript in preparation, Science Applications International Corp. and Kaiser Permanente.
  2. Maheu, M., Whitten, P., and Allen, A. (2001) E-Health, Telehealth, and Telemedicine: A Guide to Startup and Success. San Francisco: Jossey-Bass, p.120.