A financial institution is implementing a new policy for all remote access to its payment processing system. The system will generate a unique digital signature for each administrative action, and all actions will be recorded in a tamper-evident audit log that is replicated to an immutable storage location. The primary objective of this policy is to ensure that administrators who perform sensitive operations cannot later deny having executed them. Which security goal is this policy primarily intended to enforce?
Non-repudiation is a security service that provides cryptographic proof of the origin, authenticity, and integrity of a transaction or communication. In a financial institution's policy, mechanisms such as digital signatures, hash chaining, and tamper-evident audit logs ensure that an individual cannot plausibly deny having initiated or approved a specific action. This directly supports accountability and legal defensibility, making it the correct goal for preventing false denial.
Why this answer
The policy's use of unique digital signatures for each administrative action, combined with a tamper-evident audit log replicated to immutable storage, directly enforces non-repudiation. Non-repudiation ensures that an administrator cannot deny having performed a specific action because the digital signature cryptographically binds the action to the administrator's identity, and the immutable log prevents any subsequent alteration or deletion of the record. This is the primary security goal when the objective is to prevent denial of responsibility for sensitive operations.
Exam trap
The trap here is that candidates often confuse authentication (proving identity at login) with non-repudiation (proving identity for a specific action after the fact), but the question's focus on digital signatures and tamper-evident logs clearly points to non-repudiation, not just authentication.
Why the other options are wrong
The policy focuses on preventing denial of actions through digital signatures and tamper-evident logs, which is non-repudiation, not authorization. Authorization controls what actions a user is allowed to perform, but does not prevent denial of those actions.
The policy focuses on preventing denial of actions (non-repudiation) through digital signatures and tamper-evident logs, not on verifying identity (authentication). Authentication is about proving who you are, not proving that you performed a specific action.
The policy focuses on preventing denial of actions (non-repudiation), not ensuring system uptime or resource accessibility, which is the goal of availability.