non-repudiation-privacy

Analyze source code for non-repudiation privacy threats from audit logging and digital signatures.

12|1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/florianbuetow/claude-code --skill non-repudiation-privacy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: non-repudiation-privacy
Source: https://github.com/florianbuetow/claude-code/tree/main/plugins/appsec/skills/non-repudiation-privacy
Command: npx skills add https://github.com/florianbuetow/claude-code --skill non-repudiation-privacy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses privacy concerns arising from excessive or inappropriate logging and digital signatures that create irrefutable proof of user actions, potentially violating the need for plausible deniability.

Core Features & Use Cases

  • Analyze Audit Logging: Identifies overly broad or sensitive data logging.
  • Assess Digital Signatures: Checks if signatures create unwanted irrefutable evidence for sensitive actions.
  • Detect Privacy Gaps: Pinpoints situations where plausible deniability is lost due to accountability mechanisms.
  • Use Case: Reviewing a healthcare application to ensure that patient queries are not logged in a way that could be subpoenaed, preserving user privacy.

Quick Start

Analyze the current code changes for non-repudiation privacy risks.

Frequently Asked Questions about non-repudiation-privacy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do audit logging and digital signatures create privacy risks?

Excessive audit logging and digital signatures create privacy risks by producing irrefutable proof of user actions, which eliminates plausible deniability and can expose sensitive user behavior to legal subpoena.

What is plausible deniability in software privacy design?

Plausible deniability in software privacy design is the ability to prevent accountability mechanisms from creating irrefutable evidence of sensitive user actions, thereby preserving user privacy against legal or unauthorized scrutiny.

How do I analyze source code for non-repudiation privacy threats?

Analyze source code for non-repudiation privacy threats by mapping LINDDUN category N to identify audit logging, digital signatures, and immutable record storage that eliminate plausible deniability for sensitive user activities.

Can I apply LINDDUN category N to assess privacy risks in healthcare applications?

Yes, you can apply LINDDUN category N to assess healthcare application privacy risks by identifying if patient queries are logged or signed in ways that create irrefutable proof and eliminate plausible deniability.

Does implementing immutable record storage violate privacy regulations?

Implementing immutable record storage can violate privacy regulations if it creates irrefutable proof of sensitive user actions without preserving plausible deniability, mapping to non-repudiation privacy threats under LINDDUN category N.

What is the difference between STRIDE repudiation and LINDDUN non-repudiation privacy?

STRIDE repudiation focuses on preventing users from denying malicious actions, whereas inverse STRIDE repudiation and LINDDUN non-repudiation privacy focus on preventing systems from creating irrefutable proof that eliminates user plausible deniability.