An information system owner has supplied a new requirement to the development team that calls for increased non-repudiation within the application. After undergoing several audits, the owner…

Transitive trust describes how trust relationships extend across multiple entities in a chain, which is related to authentication and authorization but does not directly provide non-repudiation for user actions within an application.

Symmetric encryption ensures confidentiality by scrambling data but does not provide non-repudiation because both parties share the same key, making it impossible to definitively prove who performed an action.

Two-factor authentication strengthens the login process by requiring multiple verification methods but does not inherently provide non-repudiation for specific actions taken by a user within the application after successful authentication.

Digital signatures leverage asymmetric cryptography to bind an individual's unique private key to data, creating a cryptographic hash that serves as verifiable proof of origin and integrity. This mechanism ensures non-repudiation by making it technically infeasible for the signer to later deny having signed a document or performed an action, as only their private key could have created the valid signature.

One-time passwords enhance authentication by using a unique password for each session, but they do not provide non-repudiation for actions performed by the user within the application once authenticated.