Study guide

13.2 Completing Privacy and Data Protection Impact Assessments

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

13.2 Completing Privacy and Data Protection Impact Assessments

Key Takeaways Explain This Topic AI

GDPR Article 35 requires a DPIA before processing likely to result in a high risk, including systematic profiling with significant effects, large-scale special-category data, and large-scale monitoring of public areas.

European guidance lists nine criteria (such as evaluation or scoring, sensitive data, large scale, matching datasets, vulnerable people, and innovative technology); processing meeting two or more usually needs a DPIA.

A DPIA must describe the processing, assess necessity and proportionality, assess risks to individuals, and set out measures to address them (Article 35(7)).

If high residual risk remains, the controller must consult the supervisory authority before processing; the authority has up to eight weeks, extendable by six, to give advice (Article 36).

In the US, federal agencies conduct PIAs under the E-Government Act of 2002, many state laws require data protection assessments, and California's risk assessment rules have applied since January 1, 2026.

Last updated: October 2026

13.2 Completing Privacy and Data Protection Impact Assessments

Quick Summary: A privacy impact assessment (PIA) is a structured analysis of how a project collects, uses, shares, and protects personal data, what could harm individuals, and how to reduce that harm. The GDPR version, the data protection impact assessment (DPIA) , is mandatory for high-risk processing. Privacy technologists supply the system description, data flows, threat analysis, and technical controls, and they verify that mitigations are actually built.

PIAs work best early, when design choices are still cheap to change. A PIA completed the week before launch can only document risk; one completed during design can remove it.

When Is an Assessment Required?

Under the GDPR

Article 35(1) requires a DPIA before processing that is "likely to result in a high risk to the rights and freedoms of natural persons," especially when using new technologies. Article 35(3) names three cases that always require one:

(a) systematic and extensive evaluation of personal aspects based on automated processing, including profiling, that produces legal or similarly significant effects;

(b) large-scale processing of special categories of data or criminal-offence data;

(c) systematic monitoring of a publicly accessible area on a large scale.

Supervisory authorities also publish lists of processing types that require a DPIA. European guidance (WP29's WP248, endorsed by the EDPB) gives nine criteria ; processing that meets two or more usually requires a DPIA:

  • # Criterion Example
  • 1 Evaluation or scoring, including profiling and prediction Credit scoring, behavioral profiling
  • 2 Automated decision-making with legal or similar effect Automatic loan rejection
  • 3 Systematic monitoring Employee monitoring, public CCTV
  • 4 Sensitive data or data of a highly personal nature Health, biometric, location, financial data
  • 5 Data processed on a large scale National customer base
  • 6 Matching or combining datasets Joining purchase and location data
  • 7 Data concerning vulnerable data subjects Children, employees, patients
  • 8 Innovative use or new technological solutions Facial recognition, generative AI, IoT
  • 9 Processing that prevents people from exercising a right or using a service Blocklisting that denies service

A threshold assessment (a short screening questionnaire) decides whether a full DPIA is needed and documents the decision either way.

In the United States

Federal agencies must conduct PIAs for new or substantially changed systems that collect personally identifiable information under Section 208 of the E-Government Act of 2002 , and usually publish them.

State comprehensive privacy laws (for example, Virginia and Colorado) require data protection assessments before processing for targeted advertising, sale of personal data, certain profiling, and sensitive data, and regulators can request them. Colorado's rules specify detailed contents.

California's CCPA regulations , effective January 1, 2026, require risk assessments for processing that presents significant risk, such as selling or sharing personal information, processing sensitive personal information, and using automated decision-making technology for significant decisions; businesses must submit summary information to the California Privacy Protection Agency, with the first submissions due by April 1, 2028.

Related Assessments

Transfer impact assessments (TIAs) evaluate international transfers (Section 16.2).

Fundamental rights impact assessments (FRIAs) are required by the EU AI Act for certain deployers of high-risk AI systems and can be combined with a DPIA.

Legitimate interests assessments (LIAs) test whether legitimate interests can justify processing.

What a DPIA Must Contain

Under Article 35(7) , a DPIA contains at least:

A systematic description of the processing and its purposes, including any legitimate interest pursued.

An assessment of the necessity and proportionality of the processing in relation to its purposes.

An assessment of the risks to the rights and freedoms of data subjects.

The measures envisaged to address the risks, including safeguards, security measures, and mechanisms to demonstrate compliance.

The controller must seek the advice of the DPO (Article 35(2)) and, where appropriate, the views of data subjects or their representatives (Article 35(9)). If the DPIA shows a high residual risk that the controller cannot mitigate, Article 36 requires prior consultation with the supervisory authority, which has up to eight weeks to give written advice, extendable by six weeks for complex cases.

A Practical PIA Workflow

Loading diagram...

Where the technologist contributes:

Describe: data inventories, data flow diagrams, and lists of fields, systems, vendors, and retention periods.

Identify risks: threat modeling with LINDDUN or PANOPTIC (Section 4.2), NIST's problematic data actions (Section 16.1), and attack scenarios such as re-identification or insider misuse.

Evaluate: rate likelihood and severity of harm to individuals, not just to the organization.

Mitigate: propose concrete controls such as minimization, pseudonymization, access restrictions, retention limits, consent flows, and transparency features, and estimate their effect on residual risk.

Verify: confirm that controls were built and tested before launch, and link the DPIA to tickets and test results.

Review: reassess when the processing changes, such as new data types, purposes, vendors, or AI features. A DPIA is a living document.

Useful tools include the UK ICO's DPIA template, the French CNIL's open-source PIA software, and NIST's Privacy Risk Assessment Methodology (PRAM) worksheets.