CC ยท Core security concepts
Non-repudiation
What it means, how digital signatures, logs and audit trails provide it, and how it differs from authentication.
Key points
- Non-repudiation means a person or system cannot credibly deny an action they performed, such as sending a message or approving a payment.
- It rests on evidence tied uniquely to the actor: digital signatures made with a private key, protected logs and audit trails.
Source: https://csrc.nist.gov/glossary/term/non_repudiation
Practice questions
Which mechanism most directly provides non-repudiation for a document?
- A digital signature
- File compression
- A firewall rule
- A shared team password
Show answer
Answer: A. A digital signature
A digital signature is created with the signer's private key, so a third party can verify who signed. Compression, a firewall rule or a shared password cannot tie the action to one person.
Which measures help provide non-repudiation?
- Digitally signing approvals
- Letting staff share one login
- Writing tamper-protected audit logs per user
- Compressing log files
- Deleting logs after each shift
Show answer
Answer: A. Digitally signing approvals, C. Writing tamper-protected audit logs per user
Signatures and protected, individually attributed logs create evidence that holds up. Sharing credentials breaks attribution, and compression adds no evidence.
True or false: non-repudiation and authentication are the same, since both establish who someone is.
Show answer
Answer: False
False. Authentication verifies identity at the moment of access. Non-repudiation preserves evidence afterwards so the person cannot later deny the action.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
