Nonrepudiation
Nonrepudiation is the security property of providing evidence linking an action or message to its purported originator, limiting credible denial.
Software Security for Developers
Nonrepudiation is the legal and technical property that provides proof that a specific action or message was performed or sent by a specific party.
- How it is used
- Establishes proof of message origin or transaction responsibility when ordinary integrity and authentication are insufficient.
- How deep it goes
- Defines the property and contrasts HMAC with digital signatures, but does not develop legal procedures or protocol internals.
- Examples
- Uses e-commerce transactions and warehouse-to-payment service messages to illustrate signing and verification.
- What you can do after
- Evaluate when digital signatures are preferable to HMACs because proving the signer matters more than maximum performance.
Read how Software Security for Developers explains nonrepudiation →
Secure APIs
Nonrepudiation is the property that prevents a party from credibly denying authorship or approval of an action or message.
- How it is used
- Protects high-risk API actions by linking authorization, tokens, and message use to a legitimate user.
- How deep it goes
- Explains the failure of account attribution and lists signature points, but stops short of implementation details.
- Examples
- Uses a disputed nonrefundable e-commerce order and signatures on authorization requests, responses, introspection results, and ID tokens.
- What you can do after
- Apply it via FAPI 2.0 message signing to produce signature proofs for high-risk API actions.
API Design Patterns
Nonrepudiation is assurance that an actor cannot credibly deny having originated a request or message after its origin has been established.
- How it is used
- Authenticates API requests when later denial by the requester or independent third-party verification matters.
- How deep it goes
- Explains the symmetric-credential failure, asymmetric remedy, request fingerprint, and selection trade-offs without detailing cryptographic implementation.
- Examples
- Uses user 1234, a potentially forging API server, third-party verification, and signed HTTP request components.
- What you can do after
- Evaluate authentication designs and choose signed requests when independent verification or durable audit evidence is required.
100 SQL Server Mistakes and How to Avoid Them
Nonrepudiation is the property that provides evidence linking an action to its originator so the originator cannot credibly deny performing it.
- How it is used
- Uses administrative auditing to establish accountability and detect misuse of privileged SQL Server accounts.
- How deep it goes
- Explains the operational rationale, Windows prerequisites, audit destination, and administrative event groups without detailing investigation workflows.
- Examples
- Demonstrates SQL Server audit creation, audit specification configuration, and a compromised administrative account scenario.
- What you can do after
- Operate SQL Server Audit to preserve administrative evidence and identify accounts requiring containment.
Read how 100 SQL Server Mistakes and How to Avoid Them explains nonrepudiation →
Hacking Cryptography
Nonrepudiation is the security property that provides evidence linking an action or signed data to its purported originator so that the originator cannot plausibly deny it.
- How it is used
- Establishes evidence linking signed messages to their purported originators for trust, contracts, software, and other applications.
- How deep it goes
- Defines the security claim and its private-key caveat, but does not develop a complete signing or verification implementation.
- Examples
- Uses signed messages, digital contracts, software signatures, blockchains, and digital certificates as concrete application examples.
- What you can do after
- Evaluate whether a signature supports nonrepudiation by checking private-key security and the underlying scheme’s resistance to forgery.
Related concepts
- digital signatureproduced by · A digital signature is cryptographic data generated with a private key and verified with corresponding public information to authenticate data or its signer and detect alteration.
- cryptographyaddressed by · Cryptography is the study and application of mathematical techniques for protecting information and communications through confidentiality, integrity, authentication, and related security properties.
- SQL Server auditaddressed by · SQL Server Audit is a SQL Server feature that records specified database and server events for review and compliance.
- public-private key pairaddressed by · A public-private key pair is a mathematically related public key and private key used together for asymmetric cryptographic operations.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.