Definition: Nonrepudiation is an IT non-functional requirement that ensures that the sender and the receiver cannot deny the sending or reception of a message. It is a security measure that provides proof of the authenticity and integrity of a message, ensuring that it cannot be altered or tampered with during transmission. Nonrepudiation is essential in situations where legal or financial transactions are involved, as it provides evidence that can be used to resolve disputes or prove compliance with regulations. Source: TOGAF Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html Additional information: Nonrepudiation is an IT non-functional requirement that ensures that the sender of a message cannot deny sending it and the receiver cannot deny receiving it. This requirement is essential in situations where there is a need to establish accountability and traceability of communication between parties. According to the TOGAF specification, nonrepudiation is a security requirement that is achieved through the use of digital signatures, timestamps, and other cryptographic techniques. These techniques ensure that messages are tamper-proof and that their origin and integrity can be verified. Nonrepudiation is an important requirement in many industries, including finance, healthcare, and legal services. It helps to prevent fraud, disputes, and other legal issues that may arise from disputes over the authenticity of messages. To ensure nonrepudiation, IT systems must be designed with security in mind. This includes implementing strong authentication and access controls, using encryption to protect data in transit and at rest, and monitoring systems for suspicious activity. Additionally, organizations must have policies and procedures in place to ensure that nonrepudiation requirements are met and that any violations are addressed promptly. Overall, nonrepudiation is a critical IT non-functional requirement that helps to ensure the integrity and accountability of communication between parties. By following the TOGAF guidelines and documentation, organizations can design and implement systems that meet this requirement and provide a secure and reliable platform for communication and collaboration. Example: Nonrepudiation is an IT non-functional requirement that ensures that a user cannot deny having performed a particular action or transaction. For example, in an online banking system, nonrepudiation ensures that a user cannot deny having made a particular transaction, such as transferring funds to another account. This is achieved through the use of digital signatures and other cryptographic techniques that provide evidence of the user's identity and the authenticity of the transaction. LOST view: Digital Solution Non-Functional Requirements Catalogue view Identifier: http://data.europa.eu/dr8/egovera/NonrepudiationRequirement EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement ABB name: egovera:NonrepudiationRequirement EIRA concept: eira:ArchitectureBuildingBlock Last modification: 2023-05-16 dct:identifier: http://data.europa.eu/dr8/egovera/NonrepudiationRequirement dct:title: Nonrepudiation Non-Functional Requirement