Study guide

3.1 Risk Concepts: Threat, Vulnerability, Attack, Exploit, and Privacy Risk

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

3.1 Risk Concepts: Threat, Vulnerability, Attack, Exploit, and Privacy Risk

Key Takeaways Explain This Topic AI

A threat is a potential cause of harm, a vulnerability is a weakness it can use, an exploit is the specific technique or code that takes advantage of the weakness, and an attack is the attempt itself.

Risk is a function of likelihood and impact; inherent risk is measured before controls and residual risk after them.

Privacy risk can exist with no attacker at all, because problematic data actions by authorized systems can harm people.

CVE identifies a specific vulnerability, CWE classifies the underlying weakness type, and CVSS scores severity; none of them measures harm to individuals.

Risk responses are avoid, mitigate, transfer (share), and accept; insurance can transfer an organization's financial loss but never the harm to the people whose data was exposed.

Last updated: October 2026

3.1 Risk Concepts: Threat, Vulnerability, Attack, Exploit, and Privacy Risk

Quick Summary: CIPT questions expect you to separate four terms that are often blurred: the threat (what could cause harm), the vulnerability (the weakness), the exploit (the way the weakness is used), and the attack (the attempt). Risk is the combination of how likely a harmful event is and how bad its impact would be. Privacy risk adds a twist: the harm can come from the system working exactly as designed.

Privacy technologists sit between security engineers, who speak in threats and vulnerabilities, and privacy lawyers, who speak in rights and harms. Using a shared vocabulary lets the two groups prioritize the same problems.

Core Definitions

The definitions below follow NIST usage (for example, NIST SP 800-30 Rev. 1 and the CNSSI 4009 glossary), which most security teams use.

Term Meaning Privacy-Flavored Example

Asset Something of value to protect A customer database, a model trained on user data, or a person's location history

Threat Any circumstance or event that could adversely affect operations, assets, or individuals A data broker scraping profiles; an insider browsing celebrity records

Threat source / actor The person, group, or condition behind a threat (adversarial, accidental, structural, or environmental) A criminal group, a careless engineer, a failed disk, a flood

Vulnerability A weakness in a system, procedure, control, or implementation that a threat source could use No multifactor authentication on an admin console; an API that returns full profiles

Exploit Code or a technique that takes advantage of a specific vulnerability A script that enumerates sequential user IDs on an unprotected endpoint

Attack An attempt to gain unauthorized access, cause harm, or misuse a system Running that script against production to harvest 500,000 records

Likelihood How probable it is that a threat event occurs and succeeds Often estimated from threat activity, exposure, and control strength

Impact The magnitude of harm if it happens Financial loss to the organization; dignity, economic, or physical harm to individuals

Risk A function of likelihood and impact "High likelihood, high impact" for an exposed endpoint holding health data

A useful chain to remember is: threat source → (uses) exploit → (against) vulnerability → (during an) attack → (causing an) impact on assets and people. A zero-day is a vulnerability for which no fix is available when it is first exploited.

Inherent and Residual Risk

Inherent risk is the risk before controls; residual risk is what remains after controls are applied. Assessments such as DPIAs record both, because the decision to proceed depends on residual risk. If residual risk to individuals stays high under the GDPR, the controller must consult the supervisory authority before processing (Article 36).

Risk Responses

  • Response Meaning Privacy Example
  • Avoid Stop or redesign the activity Drop a feature that needs precise location
  • Mitigate (reduce) Add controls to lower likelihood or impact Pseudonymize data, add MFA, shorten retention

Transfer (share) Shift part of the financial consequence to someone else Cyber insurance; contractual indemnities

Accept Proceed, with documented sign-off by an accountable owner A low residual risk accepted by the product owner

Transfer has a limit in privacy: insurance can pay for notification letters and legal costs, but it cannot undo the exposure of someone's medical history. That is why privacy programs favor avoidance and mitigation.

Vulnerability Vocabulary: CVE, CWE, CVSS, and KEV

CVE (Common Vulnerabilities and Exposures): a unique identifier for a specific publicly known vulnerability in a specific product, such as a library version.

CWE (Common Weakness Enumeration): a catalog of weakness types , such as CWE-200 (exposure of sensitive information to an unauthorized actor) or CWE-532 (insertion of sensitive information into log files). CWE is useful for privacy because many privacy bugs are weakness types rather than product-specific CVEs.

CVSS (Common Vulnerability Scoring System): a severity score from 0 to 10 (version 4.0 was released in November 2023). CVSS measures technical severity, not harm to individuals.

KEV (Known Exploited Vulnerabilities) catalog: a list maintained by the U.S. Cybersecurity and Infrastructure Security Agency (CISA) of vulnerabilities known to be exploited in the wild, often used to set patching priorities.

How Privacy Risk Differs from Security Risk

NIST's Privacy Framework draws two overlapping circles: cybersecurity risks arise from unauthorized loss of confidentiality, integrity, or availability, and privacy risks arise from data processing. They overlap in cybersecurity-related privacy events , such as a breach of personal data. But privacy risk also covers events with no attacker at all.

Concept Security View Privacy View

Threat source External attackers, insiders, accidents Also the organization itself, its partners, and its own authorized algorithms

Vulnerability Coding flaw, misconfiguration, missing patch Also design choices: collecting more than needed, keeping data forever, joining datasets that reveal new facts

Attack Intrusion, malware, denial of service Also re-identification, linkage, inference, membership inference, and insider snooping with valid credentials

Impact Loss to the organization Harm to individuals (dignity loss, discrimination, economic loss, loss of self-determination, loss of trust) plus organizational loss

Authorized-but-inappropriate access is the classic privacy threat that security tools miss. An employee with valid credentials who looks up an ex-partner's address triggers no intrusion alarm. Controls include purpose-based access, query logging with review, alerts on access to records of employees or public figures, and "break-glass" workflows that record a justification.

Privacy attacks on data and models also need their own vocabulary:

Re-identification: linking a de-identified record back to a person (Chapter 7).

Inference: deriving sensitive facts (health, sexuality, finances) from innocuous data.

Membership inference: determining whether a person's record was in a dataset or a model's training data.

Model inversion and training-data extraction: reconstructing attributes or verbatim training text from a model's outputs (Chapter 12).

Putting It Together: A Worked Example

A mobile banking app exposes GET /api/users/{id}/statements and checks only that the caller is logged in, not that id belongs to the caller.

Asset: customers' bank statements.

Vulnerability: broken object-level authorization (the API trusts the id in the URL).

Threat source: any logged-in user, including a fraudster with a cheap account.

Exploit: a loop that increments id values.

Attack: running the loop to download thousands of statements.

Impact: economic loss and dignity loss for customers; regulatory, legal, and reputational loss for the bank.

Risk response: mitigate by enforcing ownership checks server-side and rate limiting, then verify with tests; avoid storing statements in a form the API can return in bulk.

Notice that patching the bug lowers the likelihood , while minimization and short retention lower the impact if a similar flaw appears later. Privacy technologists push for both.