Study guide
4.2 Privacy Threat Models: LINDDUN and MITRE PANOPTIC
Certified Information Privacy Technologist CIPT
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: CIPT Exam Overview and Study Plan
1.1 CIPT Exam Facts, Blueprint, and Study Plan
2 Chapter 2: The Privacy Technologist's Legal and Procedural Role
2.1 Privacy Function Roles: DPO, Data Owner, Steward, Custodian, Legal, and Security 2.2 Translating Legal and Regulatory Requirements into Technical Controls 2.3 Notices, Policies, and Oversight of Privacy Operations, Audits, and Third Parties
3 Chapter 3: Technical Responsibilities: Risk Concepts and Incident Response
3.1 Risk Concepts: Threat, Vulnerability, Attack, Exploit, and Privacy Risk 3.2 Technical Support for Privacy Incident and Breach Response
4 Chapter 4: Privacy Risk Models, Frameworks, and Threat Models
4.1 Privacy Risk Models and Frameworks: Contextual Integrity, Calo, Solove, FIPPs, OECD, NIST, and FAIR 4.2 Privacy Threat Models: LINDDUN and MITRE PANOPTIC
5 Chapter 5: Data Ethics and Automated Decision-Making
5.1 Legal Versus Ethical Processing and the Social Impact of Privacy-Affecting Designs 5.2 Identifying and Minimizing Bias in Automated Decision-Making
6 Chapter 6: Minimizing Privacy Risk During Data Collection
6.1 Notice, Consent Management, and Choice Architecture 6.2 Managing Privacy Risk in Automatic Collection and Telemetry 6.3 Extracting Personal Data from Publicly Available Sources 6.4 Data Retention, Destruction, and Cryptographic Erasure 6.5 Data Minimization Techniques 6.6 Implementing Data Processing Segregation
7 Chapter 7: Minimizing Privacy Risk During Data Use: Aggregation, PETs, and Secondary Use
7.1 Minimizing Privacy Risk from Aggregation and Inference 7.2 De-identification, Pseudonymization, and Tokenization 7.3 Microdata Protection: k-Anonymity, l-Diversity, and t-Closeness 7.4 Advanced PETs: Differential Privacy, Secure Multi-Party Computation, and Homomorphic Encryption 7.5 Secondary Use, Function Creep, and Purpose Limitation Controls
8 Chapter 8: Minimizing Privacy Risk During Dissemination
8.1 Disclosure and Accessibility Controls: APIs, Egress, and Clean Rooms 8.2 Countering Distortion, Exposure, Breach of Confidentiality, Blackmail, and Appropriation 8.3 Defense in Depth: Identity, Access Management, and Authentication
9 Chapter 9: Intrusion, Decisional Interference, and Dark Patterns
9.1 Minimizing Intrusion and Decisional Interference: Behavioral Advertising, Profiling, Cyberbullying, and Social Engineering 9.2 Dark Patterns and Deceptive Design
10 Chapter 10: Privacy Risks Related to Software Security
10.1 Detecting and Fixing Software Privacy Vulnerabilities 10.2 Intrusion Detection and Prevention, and Privacy in Change Management 10.3 Service Providers, Third-Party SDKs, and Supply Chain Risk
11 Chapter 11: Tracking and Surveillance Technologies
11.1 Privacy Risks and Impacts of E-Commerce 11.2 Audio and Video Surveillance, Wearables, and IoT 11.3 Privacy Issues Around Biometrics: Facial, Voice, Fingerprint, and DNA Data 11.4 Privacy Risks and Impacts of Location Tracking 11.5 Internet Monitoring and Web Tracking: Cookies, Fingerprinting, and GPC
12 Chapter 12: Workplace Technologies: AI, Communications, and Monitoring
12.1 Identifying and Minimizing Privacy Risks in AI, Machine Learning, and Deep Learning 12.2 Privacy Risks of Communications Technologies: Video Calls, Messaging, Mobile Devices, Social Media, and Gaming 12.3 Workplace Monitoring and BYOD Privacy
13 Chapter 13: Monitoring and Managing Privacy Risk
13.1 Privacy Audits, IT Control Reviews, KRIs, and KPIs 13.2 Completing Privacy and Data Protection Impact Assessments
14 Chapter 14: Implementing Privacy by Design
14.1 Cavoukian's Seven Foundational Principles of Privacy by Design 14.2 Privacy Goals, Objectives, and Translating High-Level Specifications into Low-Level Specifications 14.3 Hoepman's Privacy Design Strategies: Data-Oriented Strategies 14.4 Hoepman's Privacy Design Strategies: Process-Oriented Strategies
15 Chapter 15: Evaluating Privacy Risks in User Experiences
15.1 Privacy in User Experience: UX Concepts and Usability Testing 15.2 Value Sensitive Design
16 Chapter 16: Privacy Engineering Objectives, Architecture, and the Development Life Cycle
16.1 NIST Privacy Engineering Objectives: Predictability, Manageability, and Disassociability 16.2 Enterprise Architecture, Data Flow Mapping, Lineage, and Cross-Border Transfers 16.3 Managing Privacy Risk in the Software Development Life Cycle 16.4 Applying LINDDUN Threat Modeling in Engineering
17 Chapter 17: Managing and Monitoring Privacy Controls
17.1 Data Inventories, Records of Processing Activities, and Asset Discovery 17.2 Privacy Code Review and Runtime Behavior Monitoring
4.2 Privacy Threat Models: LINDDUN and MITRE PANOPTIC
Key Takeaways Explain This Topic AI
LINDDUN's seven threat types are Linking, Identifying, Non-repudiation, Detecting, Data Disclosure, Unawareness and Unintervenability, and Non-compliance.
LINDDUN's first five threat types are hard privacy threats (anonymity, unlinkability, confidentiality); unawareness and non-compliance are soft privacy threats (transparency, control, compliance).
LINDDUN comes in variants: LINDDUN GO (a card-based workshop method), LINDDUN PRO (systematic analysis of each DFD element), and LINDDUN MAESTRO (in-depth analysis).
MITRE PANOPTIC (Pattern and Action Nomenclature Of Privacy Threats In Context) combines Contextual Domains with Privacy Activities made up of privacy threat actions.
PANOPTIC was built from real non-breach privacy cases, counts inactions such as missing notice or consent as threats, and treats the system itself as a possible threat agent.
Last updated: October 2026
4.2 Privacy Threat Models: LINDDUN and MITRE PANOPTIC
Quick Summary: A threat model is a structured catalog of what can go wrong. Security teams use STRIDE or MITRE ATT&CK; the CIPT BoK names two privacy threat models: LINDDUN , from KU Leuven, which walks through a system design element by element, and MITRE PANOPTIC , which describes how real privacy attacks unfold in context. Both treat privacy harms that are not security breaches as first-class threats.
Risk frameworks (Section 4.1) tell you how to manage privacy risk; threat models help you find the risks in a specific system. A privacy threat model has to cover things security models ignore: the organization's own processing, people who do not know what is happening to their data, and failures to act, such as never giving notice.
LINDDUN: Seven Privacy Threat Types
LINDDUN was first published in 2011 by researchers at KU Leuven's DistriNet group and has been revised several times. Its acronym lists seven threat types, using the current names:
Threat Type What Goes Wrong Example
Linking Data items or actions can be linked to the same person, even without knowing who that person is Two "anonymous" app sessions are linked because both send the same device fingerprint
Identifying A person's identity can be learned from data or actions A rare combination of ZIP code, birth date, and sex points to one patient
Non-repudiation A person cannot deny having done something, where deniability matters A whistleblowing portal logs signed, timestamped submissions tied to user accounts
Detecting Someone can tell whether a person or item of interest exists, without seeing its content A login form responds faster for registered email addresses than unregistered ones
Data Disclosure Personal data is disclosed to parties who should not have it An API returns full profiles to any authenticated caller
Unawareness and Unintervenability People are not informed about, or cannot influence, how their data is processed No dashboard to see or delete inferred interests
Non-compliance Processing does not follow legislation, regulation, or policy Data kept far beyond the retention period in the published notice
Older study materials use the earlier names Linkability, Identifiability, Detectability, Disclosure of information, and Unawareness. The meaning is the same; the current version renamed them as actions and folded "unintervenability" (the inability to intervene) into the sixth category.
Hard and Soft Privacy
LINDDUN groups its types into two families:
Hard privacy threats (linking, identifying, non-repudiation, detecting, data disclosure) concern properties such as anonymity, unlinkability, plausible deniability, undetectability, and confidentiality. Mitigations tend to be technical: pseudonyms, anonymous credentials, encryption, noise.
Soft privacy threats (unawareness and unintervenability, non-compliance) concern transparency, user control, and compliance. Mitigations tend to combine design and governance: notices, dashboards, consent and rights tooling, retention enforcement.
How LINDDUN Is Applied
LINDDUN starts from a data flow diagram (DFD) of the system, made of external entities, processes, data stores, and data flows. Analysts walk through each element and ask which threat types apply, using threat trees that break each type into concrete conditions. Section 16.4 walks through this process step by step, including the classic mapping table of threat types to DFD elements.
LINDDUN offers three variants to fit different teams:
LINDDUN GO: a lightweight, card-based method for workshops. Each card describes a common threat; teams walk through the cards against a whiteboard sketch.
LINDDUN PRO: a systematic method that analyzes each DFD element (or each flow) against the threat trees.
LINDDUN MAESTRO: the most in-depth variant, for detailed, high-assurance analyses.
LINDDUN also pairs threats with mitigation strategies and privacy-enhancing technologies, such as pseudonymous identifiers against linking or differential privacy against detecting.
MITRE PANOPTIC: Privacy Threats in Context
PANOPTIC stands for Pattern and Action Nomenclature Of Privacy Threats In Context . MITRE released it publicly in late 2023, and version 2.0 followed in 2024. Where LINDDUN starts from a system design, PANOPTIC starts from how privacy attacks actually happen : it was built by deconstructing hundreds of documented non-breach privacy cases, mostly U.S. Federal Trade Commission and Federal Communications Commission matters, and cataloging their components. It plays a role for privacy similar to the one MITRE ATT&CK plays for cyberattacks, but its structure is different.
PANOPTIC combines two taxonomies :
Loading diagram...
Contextual Domains (Environment, Distribution, Interaction, Engagement, and Data Type) describe the circumstances of an attack, such as whether it happens in a physical store or online and whether it involves location, biometric, or health data.
Privacy Activities describe the attack itself. Version 2.0 lists Notice, Consent, Collection, Insecurity, Identification, Quality Assurance, Manageability, Aggregation, Processing, Sharing, Use, Retention and Destruction, and Deviations. Each activity contains specific privacy threat actions with identifiers (for example, an absent notice, an out-of-sequence consent request, or profiling).
What Makes PANOPTIC Different
Actions and inactions. A privacy attack can be something an organization fails to do, such as never giving notice or offering no opt-out. Security threat models rarely treat inaction as an attack.
The system as threat agent. The organization's own system, operating as designed, can be the source of the threat.
Benign and malicious intent. Privacy harm can result from well-intentioned actions.
No duplication of security models. PANOPTIC deliberately leaves out attacks covered by cybersecurity threat models, such as breaches of confidentiality, and focuses on privacy harms beyond them.
Example: MITRE's tutorial maps the FTC's case against Nomi Technologies , which tracked shoppers' phones inside retail stores. The context includes a physical environment and location data; the activities include collection by tracking, aggregation into reports for retailers, and a notice failure, because the promised in-store opt-out did not exist.
Uses of PANOPTIC
Privacy threat assessment of systems and environments, integrated into the systems engineering life cycle.
Privacy risk modeling , combining threats with vulnerability and consequence models (most privacy risk models only address consequences).
Privacy red teaming , emulating privacy adversaries to find gaps before real ones do.
LINDDUN and PANOPTIC Side by Side
- Dimension LINDDUN MITRE PANOPTIC
- Starting point The system's data flow diagram Real-world privacy attacks and their context
- Structure Seven threat types with threat trees Contextual Domains plus Privacy Activities and threat actions
Typical use Design-time threat elicitation by engineering teams Threat assessment, risk modeling, and privacy red teaming
- Inactions Covered indirectly (unawareness, non-compliance) Explicitly modeled as threat actions
- Origin KU Leuven DistriNet (academic) MITRE (empirical, from FTC and FCC cases)
The two are complementary: LINDDUN helps engineers ask the right questions about a specific design, while PANOPTIC reminds them how similar systems have actually harmed people.