GDPR EU privacy regulation with DPIA and data subject rights
- version
- 0.1.0
- GitHub stars
- 436
Install
/plugin install gdpr@grc-engineering-suiteRun it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.
Contents
Discovered from sourceSkills 1
GDPR Expert
Deep expertise in the General Data Protection Regulation (GDPR) - the European Union's comprehensive data protection law.
Expertise Areas
GDPR Overview
Regulation (EU) 2016/679: General Data Protection Regulation Effective Date: May 25, 2018 Scope: Protection of natural persons with regard to processing of personal data and free movement of such data Articles: 99 (11 chapters) Recitals: 173 (interpretive guidance)
Territorial Scope (Article 3):
- Establishment: Controller/processor established in EU (regardless of where processing occurs)
- Targeting: Offering goods/services to EU data subjects (even if free)
- Monitoring: Monitoring behavior of EU data subjects
- Applies: Even if organization not in EU
Material Scope:
- Automated processing of personal data
- Non-automated processing in filing systems
- Exemptions: National security, law enforcement (LED applies), purely personal/household
Key Definitions (Article 4)
Personal Data:
- Any information relating to identified/identifiable natural person
- Direct identifiers: Name, ID number, email
- Indirect identifiers: Location data, IP address, cookie ID, device ID
- Combination of factors: Age + ZIP code + occupation
Special Categories of Personal Data (Article 9 - "Sensitive Data"):
- Racial or ethnic origin
- Political opinions
- Religious or philosophical beliefs
- Trade union membership
- Genetic data
- Biometric data (for uniquely identifying a person)
- Health data
- Sex life or sexual orientation
Processing:
- Any operation on personal data
- Collection, recording, storage, retrieval, use, disclosure, erasure, destruction
- Automated or manual
Controller:
- Determines purposes and means of processing
- Makes decisions about why and how to process
- Primary responsibility for compliance
Processor:
- Processes on behalf of controller
- Acts on controller instructions
- Limited independent decision-making
Joint Controllers:
- Two or more controllers jointly determine purposes and means
- Must arrange responsibilities via agreement
- Each liable for entire processing
Data Subject:
- Identified or identifiable natural person
- Individual whose data is processed
- Rights holder under GDPR
Supervisory Authority:
- Independent public authority (Data Protection Authority/DPA)
- Each EU Member State has one or more
- Enforces GDPR in jurisdiction
Lead Supervisory Authority (Article 56):
- For cross-border processing
- Main establishment's DPA
- One-stop-shop mechanism
7 Principles of Data Processing (Article 5)
1. Lawfulness, Fairness, and Transparency
Lawfulness: Must have lawful basis (Article 6) Fairness: No deceptive, misleading, or detrimental processing Transparency: Clear, plain language communication to data subjects
Implementation:
- Privacy notices at collection
- Layered notices (short + full)
- Just-in-time notices
- Clear language (no legalese)
- Accessible information
2. Purpose Limitation
Requirements:
- Specified purposes (documented, clear)
- Explicit purposes (communicated to data subjects)
- Legitimate purposes (lawful, ethical)
- No processing for incompatible purposes
Compatible Processing:
- Same or closely related purpose
- Consider: Link between purposes, context, nature of data, consequences, safeguards
Exceptions:
- Archiving in public interest
- Scientific/historical research
- Statistical purposes
3. Data Minimization
"Adequate, relevant, and limited to what is necessary"
Implementation:
- Collect only what you need
- Justify each data element
- Regular review and purge
- Limit access (need-to-know)
- Pseudonymization/anonymization where possible
Common Violations:
- "Nice to have" data collection
- Speculative future use
- Excessive profiling data
4. Accuracy
Requirements:
- Personal data must be accurate
- Kept up to date where necessary
- Inaccurate data erased or rectified
Implementation:
- Verification at collection
- Regular reviews and updates
- Easy rectification process
- Notify recipients of changes
- Quality control procedures
5. Storage Limitation
"Kept no longer than necessary for the purposes"
Implementation:
- Retention schedules (per purpose)
- Regular deletion reviews
- Automated deletion where possible
- Document retention rationale
- Legal hold procedures
Exceptions (can retain longer):
- Archiving in public interest
- Scientific/historical research
- Statistical purposes
- With appropriate safeguards
6. Integrity and Confidentiality (Security)
"Appropriate security... including protection against unauthorized/unlawful processing and accidental loss, destruction or damage"
Implementation: See Article 32 (Security of Processing)
7. Accountability
"Controller shall be responsible for and able to demonstrate compliance"
Demonstration Requirements:
- Documentation (policies, procedures, records)
- Data Protection Impact Assessments (DPIAs)
- Privacy by Design and Default
- Data Processing Agreements (DPAs)
- Records of Processing Activities
- Training and awareness programs
- Regular audits and reviews
- Incident response and breach records
6 Lawful Bases for Processing (Article 6)
Must identify ONE for each processing purpose
1. Consent (Article 6(1)(a))
Requirements:
- Freely given: No coercion, imbalance of power consideration
- Specific: Separate consent for separate purposes
- Informed: Identity, purposes, data types, rights, withdrawal
- Unambiguous: Clear affirmative action (no pre-ticked boxes, silence, inactivity)
Additional for Consent:
- Easy to withdraw (as easy as to give)
- Withdrawal does not affect lawfulness of prior processing
- Burden of proof on controller
- Record of consent (who, when, what, how)
When Problematic:
- Employment context (power imbalance)
- Public authorities (no free choice)
- Service bundling (cannot refuse)
Children's Consent (Article 8):
- Under 16: Parental consent required (Member States can lower to 13)
- Controller must make reasonable efforts to verify
2. Contract (Article 6(1)(b))
Two scenarios:
- Processing necessary to perform a contract with data subject
- Processing necessary to enter into contract (pre-contractual steps)
"Necessary":
- Objectively essential to contract
- Not just "helpful" or "customary"
- Direct relationship to contract performance
Examples:
- Shipping address for product delivery
- Credit card for payment processing
- Account credentials for service access
Not Sufficient:
- Marketing to customers (use consent or legitimate interests)
- Analytics not integral to service (use legitimate interests)
3. Legal Obligation (Article 6(1)(c))
Requirements:
- Processing required by EU law or Member State law
- Obligation on the controller
- Must identify specific legal provision
Examples:
- Tax records (legal retention requirements)
- Employment records (labor law)
- AML/KYC checks (financial regulations)
- Health and safety reporting
Not Sufficient:
- Contractual obligations (use contract basis)
- Best practices or industry standards
- Non-EU legal obligations
4. Vital Interests (Article 6(1)(d))
"Necessary to protect the vital interests of the data subject or another"
Scope:
- Life or death situations
- Serious health threats
- Last resort when other bases not available
Examples:
- Emergency medical treatment (unconscious patient)
- Humanitarian crises
- Pandemic response (in some cases)
Rarely Appropriate: Most organizations won't use this basis
5. Public Task (Article 6(1)(e))
"Necessary for task carried out in the public interest or in exercise of official authority"
Scope:
- Public authorities
- Private entities exercising official authority
- Task must have basis in EU/Member State law
Examples:
- Government agencies
- Regulators
- Educational institutions (public tasks)
Not Available: Commercial organizations (use legitimate interests)
6. Legitimate Interests (Article 6(1)(f))
"Necessary for purposes of legitimate interests pursued by controller or third party, except where overridden by interests, rights and freedoms of data subject"
Three-Part Test:
- Purpose Test: Is interest legitimate?
- Necessity Test: Is processing necessary?
- Balancing Test: Do data subject's interests override?
Legitimate Interest Assessment (LIA) Required:
- Identify legitimate interest
- Necessity assessment (no less intrusive means)
- Balancing test (impact on data subjects)
- Document LIA
Examples of Legitimate Interests:
- Fraud prevention
- Network and information security
- Direct marketing (subject to right to object)
- Intra-group transfers
- Employee monitoring (limited)
- Analytics for service improvement
Cannot Use:
- Public authorities (for official tasks)
- When data subject's interests clearly override
Right to Object (Article 21):
- Data subjects can object to legitimate interests processing
- Controller must demonstrate compelling legitimate grounds to continue
Special Category Data (Article 9)
General Prohibition: Processing of special categories prohibited
Exceptions (Must meet Article 6 basis PLUS Article 9 exception):
- Explicit consent (9(2)(a))
- Employment, social security, social protection law (9(2)(b))
- Vital interests (cannot obtain consent) (9(2)(c))
- Not-for-profit body (political, philosophical, religious, trade union) (9(2)(d))
- Made public by data subject (9(2)(e))
- Legal claims (9(2)(f))
- Substantial public interest (with basis in law) (9(2)(g))
- Health/social care (professional secrecy) (9(2)(h))
- Public health (9(2)(i))
- Archiving, research, statistics (safeguards) (9(2)(j))
Criminal Conviction Data (Article 10):
- Only under control of official authority, OR
- Authorized by EU/Member State law (safeguards)
Data Subject Rights (Articles 12-22)
Covered in detail in rights-check.md command. Summary:
- Right to be Informed (Articles 13-14)
- Right of Access (Article 15)
- Right to Rectification (Article 16)
- Right to Erasure (Article 17)
- Right to Restriction (Article 18)
- Right to Data Portability (Article 20)
- Right to Object (Article 21)
- Rights re: Automated Decision-Making (Article 22)
General Requirements (Article 12):
- Free of charge (generally)
- Within 1 month (+2 months if complex)
- Concise, transparent, intelligible, plain language
Security of Processing (Article 32)
"Appropriate technical and organizational measures"
State of the Art: Current best practices Cost: Balanced against risk and impact Risk: Likelihood and severity of harm
Technical Measures
Pseudonymization:
- Separate identity from data
- Cannot attribute to individual without additional information
- Additional information kept separately with security
Encryption:
- At rest (storage encryption, database encryption, file encryption)
- In transit (TLS 1.2+, VPN, encrypted email)
- End-to-end (messaging, file sharing)
Access Controls:
- Authentication (passwords, MFA, biometrics)
- Authorization (RBAC, least privilege)
- Identity and Access Management (IAM)
Network Security:
- Firewalls and segmentation
- Intrusion detection/prevention
- DDoS protection
- Secure configurations
Monitoring and Logging:
- Security information and event management (SIEM)
- Audit logs (access, changes, deletions)
- Anomaly detection
- Log retention and protection
Resilience:
- Backup and recovery
- Redundancy and failover
- Disaster recovery
- Business continuity
Testing:
- Vulnerability scanning
- Penetration testing
- Security assessments
- Red team exercises
Organizational Measures
Policies and Procedures:
- Information security policy
- Data protection policy
- Acceptable use policy
- Incident response plan
- Business continuity plan
Staff Management:
- Background checks (proportionate)
- Confidentiality agreements
- Security awareness training
- Role-based training
- Termination procedures
Vendor Management:
- Due diligence assessments
- Data Processing Agreements (Article 28)
- Ongoing monitoring
- Audit rights
Governance:
- Security roles and responsibilities
- Management oversight
- Compliance monitoring
- Regular reviews
Physical Security:
- Facility access controls
- Visitor management
- Equipment security
- Secure disposal
Privacy by Design and Default (Article 25)
Privacy by Design (Article 25(1)):
- Implement appropriate technical and organizational measures
- At the time of determining means of processing
- At the time of processing itself
- Designed to implement principles (minimization, etc.)
- Integrate safeguards into processing
7 Foundational Principles (Cavoukian):
- Proactive not reactive
- Privacy as default setting
- Privacy embedded into design
- Full functionality (positive-sum, not zero-sum)
- End-to-end security
- Visibility and transparency
- Respect for user privacy
Privacy by Default (Article 25(2)):
- Only process data necessary for each purpose
- By default (without user action)
- Applies to: Amount collected, extent of processing, retention period, accessibility
Examples:
- Collect only necessary data
- Default privacy settings (most protective)
- Anonymization/pseudonymization
- Short retention periods
- Limited access
Data Protection Officer (DPO) (Articles 37-39)
When DPO Required (Article 37)
Mandatory DPO:
- Public authority (except courts acting in judicial capacity)
- Core activities require regular and systematic monitoring of data subjects on large scale
- Core activities consist of large-scale processing of special categories (Article 9) or criminal data (Article 10)
"Core Activities":
- Essential to organization's operations
- Not ancillary functions
"Large Scale":
- WP29 factors: Number of subjects, volume of data, duration, geographic extent
- No specific threshold
- Examples: Hospital, insurance company, search engine, telecom
"Regular and Systematic Monitoring":
- Ongoing or recurring
- Planned or organized
- Examples: Online advertising, profiling, location tracking, CCTV
Voluntary DPO:
- Any organization can appoint
- Once appointed, same requirements apply
DPO Qualities and Position (Article 37)
Professional Qualities:
- Expert knowledge of data protection law and practices
- Understanding of processing operations
- Ability to fulfill tasks
Position Requirements:
- Designated on basis of professional qualities and expertise
- Adequate resources (time, budget, staff)
- Access to personal data and processing operations
- Report directly to highest management level
- Independent (no instruction on how to perform tasks)
- No conflict of interest (cannot have position determining purposes/means)
Protection:
- Cannot be dismissed or penalized for DPO tasks
- Minimum 2-year term recommended
DPO Tasks (Article 39)
- Inform and advise controller, processor, employees
- Monitor compliance with GDPR and policies
- Advise on DPIAs and monitor performance
- Cooperate with supervisory authority
- Act as contact point for authority and data subjects
Independence:
- No instructions on performing tasks
- Controller must not interfere
- DPO decides how to perform tasks
Records of Processing Activities (Article 30)
Controller Records Must Include:
- Name and contact of controller, joint controllers, representative, DPO
- Purposes of processing
- Description of categories of data subjects and data
- Categories of recipients (including third countries)
- Transfers to third countries (documentation of safeguards)
- Retention periods (or criteria)
- Description of technical and organizational security measures (general)
Processor Records Must Include:
- Name and contact of processor, controllers, representative, DPO
- Categories of processing on behalf of each controller
- Transfers to third countries (documentation)
- Security measures description (general)
Exemptions (Article 30(5)):
- Organization with <250 employees, UNLESS:
- Processing likely to result in risk to rights and freedoms
- Not occasional processing
- Special categories or criminal data
Practical Approach: Most organizations should maintain records
Format: Written, electronic form
Data Protection Impact Assessment (Article 35)
Covered in detail in dpia.md command.
When Required:
- Processing likely to result in high risk
- Particularly: Systematic profiling, large-scale special categories, systematic public monitoring
Content:
- Systematic description of processing and purposes
- Assessment of necessity and proportionality
- Assessment of risks to data subjects
- Measures to address risks
Consultation:
- Seek advice of DPO
- Seek views of data subjects (where appropriate)
- Consult supervisory authority if high residual risk (Article 36)
Data Processing Agreements (Article 28)
When Required: Controller uses processor
Mandatory Content:
- Subject matter and duration of processing
- Nature and purpose of processing
- Type of personal data and categories of data subjects
- Obligations and rights of controller
Processor Obligations:
- Process only on documented instructions
- Ensure confidentiality of persons authorized to process
- Implement Article 32 security measures
- Respect conditions for sub-processors
- Assist controller with data subject rights
- Assist controller with Articles 32-36 obligations (security, breach, DPIA, consultation)
- Delete or return data at end of services
- Make available information for demonstrating compliance
- Allow and contribute to audits/inspections
Sub-Processors:
- Specific or general written authorization
- If general, inform of changes, opportunity to object
- Same obligations on sub-processor (via contract)
- Processor remains liable to controller
Liability: Processor directly liable under GDPR (not just to controller)
Cross-Border Data Transfers (Chapter V)
General Principle: Personal data can flow freely within EU/EEA
Transfers to Third Countries: Require safeguards (Article 44-50)
Transfer Mechanisms
1. Adequacy Decision (Article 45):
- European Commission determines third country has adequate protection
- No additional safeguards needed
- Adequate Countries: Andorra, Argentina, Canada (commercial orgs), Faroe Islands, Guernsey, Israel, Isle of Man, Japan, Jersey, New Zealand, South Korea, Switzerland, UK, Uruguay
- US: No general adequacy (Privacy Shield invalidated by Schrems II)
2. Standard Contractual Clauses (SCCs) (Article 46(2)(c)):
- EU Commission approved contract clauses
- 2021 SCCs (modernized post-Schrems II)
- Four modules: C2C, C2P, P2C, P2P
- Transfer Impact Assessment (TIA) required
- Supplementary measures if laws in third country may impinge on SCCs
3. Binding Corporate Rules (BCRs) (Article 46(2)(b)):
- Multinational groups
- Binding internal policies
- Approved by competent supervisory authority
- Complex, resource-intensive
4. Certification Mechanisms (Article 46(2)(f)):
- Approved certification + binding enforceable commitments
- Limited use to date
5. Ad Hoc Contractual Clauses (Article 46(3)(a)):
- Custom contracts
- Require supervisory authority approval
- Rarely used
6. Derogations for Specific Situations (Article 49):
- Explicit consent (informed of risks)
- Performance of contract with data subject
- Important reasons of public interest
- Legal claims
- Vital interests
- Public register (within conditions)
- Legitimate interests (not repetitive, limited subjects, appropriate safeguards)
- Use only when transfer mechanisms not available
- Not for regular transfers
Schrems II Impact
CJEU Case C-311/18 (July 2020):
- Invalidated EU-US Privacy Shield
- SCCs remain valid BUT:
- Must assess whether third country law ensures adequate protection
- Transfer Impact Assessment (TIA) required
- Supplementary measures may be needed (encryption, pseudonymization, etc.)
- Particular concern: US surveillance laws (FISA 702, EO 12333)
Practical Impact:
- US transfers: Challenging, require TIA and often supplementary measures
- China, Russia: High-risk jurisdictions
- Other countries: Case-by-case assessment
Personal Data Breaches (Articles 33-34)
Covered in detail in breach-process.md command.
72-Hour Rule:
- Notify supervisory authority within 72 hours (Article 33)
- Notify data subjects if high risk (Article 34)
Documentation (Article 33(5)):
- Record all breaches (even if not notified)
- Facts, effects, remedial action
- Demonstrate compliance
Supervisory Authorities (Articles 51-59)
Independence (Article 52):
- Act with complete independence
- Free from external influence
- Adequate resources
Tasks (Article 57):
- Monitor and enforce GDPR
- Promote awareness
- Advise on legislative measures
- Handle complaints
- Conduct investigations
- Authorize contractual clauses, BCRs
- Issue opinions, warnings, guidelines
Powers (Article 58):
- Investigative: Audits, access to data/premises, obtain information
- Corrective: Warnings, reprimands, orders (compliance, rectification, erasure), processing bans, fines
- Authorization: Approve SCCs, BCRs, certifications
Lead Supervisory Authority (Article 56):
- One-stop-shop for cross-border processing
- Based on main establishment
- Coordinates with other concerned authorities
European Data Protection Board (EDPB) (Article 68):
- Replaces Article 29 Working Party
- Ensures consistent application
- Issues guidelines, recommendations, best practices
- Dispute resolution (consistency mechanism)
Enforcement and Penalties (Articles 82-84)
Administrative Fines (Article 83)
Up to €10 Million or 2% of global annual turnover (whichever higher):
- Processors not meeting obligations (Article 28)
- Certification body violations
- Monitoring body violations
Up to €20 Million or 4% of global annual turnover (whichever higher):
- Principles violations (Article 5)
- Lawful basis violations (Article 6)
- Consent violations (Article 7)
- Special categories violations (Article 9)
- Data subject rights violations (Articles 12-22)
- Transfer violations (Articles 44-49)
- Non-compliance with supervisory authority orders
Factors Considered (Article 83(2)):
- Nature, gravity, duration of infringement
- Intentional or negligent
- Actions to mitigate damage
- Degree of responsibility
- Previous relevant infringements
- Degree of cooperation with authority
- Categories of data affected
- Manner authority became aware (proactive notification vs. complaint)
- Compliance with prior orders
- Adherence to approved codes of conduct or certifications
- Aggravating or mitigating factors (financial gain, vulnerable data subjects)
Compensation (Article 82)
Right to Compensation:
- Any person who suffered material or non-material damage
- Due to GDPR infringement
- Has right to receive compensation from controller or processor
Material Damage: Financial loss, costs Non-Material Damage: Distress, anxiety, loss of control over data
Liability:
- Controller/processor liable for damage caused by processing
- Processor liable only if failed to comply with processor obligations or acted outside controller's instructions
- Not liable if proves not responsible for damage
Joint and Several Liability: For joint controllers or controller-processor chains
Notable GDPR Enforcement Cases
Large Fines:
- Amazon (2021): €746M (Luxembourg) - Inadequate lawful basis for advertising
- WhatsApp (2021): €225M (Ireland) - Transparency violations
- Google (2019): €50M (France) - Inadequate consent for advertising
- British Airways (2020): £20M (UK) - Poor security leading to breach
- Marriott (2020): £18.4M (UK) - Insufficient due diligence (acquisition), breach
Common Violation Themes:
- Lack of valid lawful basis (especially consent, legitimate interests)
- Inadequate transparency and privacy notices
- Failure to implement data subject rights
- Insufficient security measures
- Cross-border transfer violations
- Failure to notify breaches
- Lack of DPIAs
- Missing or inadequate DPAs with processors
International Variations and Related Laws
UK GDPR:
- Post-Brexit UK version
- Materially same as EU GDPR
- ICO (Information Commissioner's Office) enforces
- Adequacy decision from EU
Swiss FADP (Federal Act on Data Protection):
- Swiss data protection law
- Similar to GDPR (adequacy decision)
- Some differences (e.g., legal entities protected)
National Implementations:
- GDPR is directly applicable (Regulation, not Directive)
- Member States can specify certain provisions
- National laws for public sector, employment, etc.
- "Margin of discretion" in some articles
Sector-Specific Considerations
Healthcare
- Health data is special category (Article 9)
- Processing for healthcare (Article 9(2)(h))
- Professional secrecy requirements
- Research provisions (Article 89)
- National health data laws
Employment
- Power imbalance (consent problematic)
- Legal obligation and legitimate interests primary bases
- Member State laws specify employment processing
- Employee monitoring (necessity, proportionality, transparency)
- Works council involvement (some jurisdictions)
Financial Services
- AML/KYC (legal obligation)
- Credit scoring (automated decisions - Article 22)
- Payment data (PSD2 interaction)
- Supervisory authority coordination (financial regulators + DPAs)
Marketing
- Direct marketing (right to object - Article 21(2))
- Consent for electronic marketing (ePrivacy Directive)
- Profiling for marketing (legitimate interests with right to object)
- Transparency about targeting
Public Sector
- Public task lawful basis (Article 6(1)(e))
- Cannot use legitimate interests for official tasks
- DPO mandatory (Article 37(1)(a))
- Often subject to additional national laws (FOI, etc.)
Relationship with Other Regulations
ePrivacy Directive (2002/58/EC):
- Governs electronic communications
- Cookies and tracking (consent required)
- Marketing emails/calls/SMS (opt-in/opt-out)
- "Lex specialis" to GDPR (takes precedence in its scope)
- ePrivacy Regulation: Proposed replacement (pending)
PSD2 (Payment Services Directive 2):
- Open banking data sharing
- Explicit consent for third-party access
- GDPR applies to payment data
NIS Directive (Network and Information Security):
- Critical infrastructure security
- Incident reporting
- Complements GDPR Article 32
DORA (Digital Operational Resilience Act):
- EU financial sector ICT resilience
- Overlaps with GDPR security/breach requirements
AI Act (Proposed):
- Regulation of artificial intelligence
- Interaction with GDPR (automated decisions, profiling)
- Additional requirements for high-risk AI
Best Practices and Recommendations
Data Mapping
- Comprehensive inventory (systems, databases, files, third parties)
- Data flows (collection → storage → use → transfer → deletion)
- Categories of data and data subjects
- Lawful bases and purposes
- Retention periods
- Recipients and processors
Policy Framework
- Data protection policy
- Privacy notices (collection, updates)
- Data subject rights procedures
- Breach response plan
- Vendor management policy
- Retention and deletion policy
- Privacy by Design standard
Governance
- DPO appointment (where required or beneficial)
- Privacy steering committee
- Defined roles and responsibilities
- Regular management reporting
- Board oversight
Training and Awareness
- All staff: GDPR awareness, data protection principles
- Developers: Privacy by Design
- Customer-facing: Data subject rights
- IT/Security: Security measures, breach response
- Leadership: Accountability, risk
Ongoing Compliance
- Regular GDPR audits (internal, external)
- Privacy impact assessments (new projects)
- Vendor assessments and DPA reviews
- Monitoring of supervisory authority guidance
- Incident and breach tracking
- Metrics (rights requests, training completion, audit findings)
- Continuous improvement
Documentation (Demonstrating Accountability)
- Records of processing activities (Article 30)
- Lawful basis documentation
- Legitimate interest assessments (LIAs)
- DPIAs for high-risk processing
- Data processing agreements (DPAs)
- Records of consent
- Data subject rights request logs
- Breach register (Article 33(5))
- Policies and procedures
- Training records
- Audit reports
Common Compliance Challenges
- Lack of data visibility: Don't know what data is held or where
- Weak lawful bases: Relying on invalid consent or vague legitimate interests
- Inadequate transparency: Privacy notices unclear or incomplete
- Complex data subject rights: Cannot locate or provide data efficiently
- Vendor ecosystem: Numerous processors, inconsistent DPAs
- Cross-border transfers: US and other third countries
- Legacy systems: Old technology, poor data controls
- Shadow IT: Unsanctioned tools and data storage
- Resource constraints: Small privacy/compliance teams
- Organizational silos: Legal, IT, business not aligned
Emerging Topics
Cookies and Tracking:
- Cookie consent banners (ePrivacy + GDPR)
- "Cookie walls" (recent guidance: generally not valid consent)
- Legitimate interests for analytics (limited acceptance)
- Tracking technologies (fingerprinting, pixels, etc.)
Artificial Intelligence and Profiling:
- Automated decision-making (Article 22)
- Transparency and explainability
- Bias and fairness
- Data minimization challenges
- Proposed AI Act interaction
Children's Data:
- Age verification challenges
- Parental consent requirements
- Age-appropriate design (UK Age Appropriate Design Code)
- Online services and social media
Biometric Data:
- Special category (Article 9)
- Facial recognition (high-risk DPIA required)
- Regulatory scrutiny and bans (some public uses)
- Workplace biometrics (proportionality)
Dark Patterns:
- Manipulative UX design
- EDPB Guidelines 03/2022 on deceptive design patterns
- Cookie banners, consent flows, account deletion
International Data Transfers Post-Schrems II:
- US transfers (supplementary measures, new EU-US framework discussions)
- Transfer Impact Assessments (TIAs)
- Encryption and pseudonymization as safeguards
- Data localization pressures
Capabilities
- GDPR compliance assessments and gap analysis
- Lawful basis determination and documentation
- Legitimate interest assessments (LIAs)
- Privacy notice and transparency review
- Data subject rights implementation (all 8 rights)
- Data Protection Impact Assessments (DPIAs)
- DPO requirement evaluation and role definition
- Records of Processing Activities (Article 30) creation
- Data Processing Agreement (DPA) drafting and review
- Security measures assessment (Article 32)
- Privacy by Design and Default integration
- Breach notification procedures (72-hour rule)
- Cross-border transfer mechanism selection and implementation
- Transfer Impact Assessments (TIAs)
- Vendor and processor risk assessments
- Cookie consent and tracking compliance
- Special category data processing authorization
- Automated decision-making (Article 22) compliance
- Supervisory authority interactions and complaint responses
- GDPR training program development
- Policy and procedure creation
- Consent management systems
- Data mapping and inventory
- Retention and deletion schedules
- Incident response planning
- GDPR audit preparation
Commands 5
GDPR Assessment
Evaluates organizational readiness for General Data Protection Regulation (GDPR) compliance.
Arguments
$1- Assessment scope (optional: full, data-mapping, rights-management, security-measures)$2- Organization type (optional: controller, processor, joint-controller)
GDPR Applicability
Territorial Scope:
- Establishment in EU (regardless of processing location)
- Offering goods/services to EU data subjects
- Monitoring behavior of EU data subjects
Data Subject Rights Territory:
- EU/EEA countries
- UK (UK GDPR post-Brexit)
- Switzerland (via adequacy decision)
Assessment Output
- Compliance Score: Overall GDPR readiness percentage
- Principle Assessment: Evaluation against 7 core principles
- Lawful Basis Analysis: Validity of processing bases
- Data Subject Rights: Implementation status of 8 rights
- Security Measures: Technical and organizational safeguards
- Accountability: Documentation and governance gaps
- DPO Requirements: Whether DPO required and compliance status
- Cross-Border Transfers: Transfer mechanism compliance
- Breach Readiness: 72-hour notification capability
- Remediation Roadmap: Prioritized action plan with timelines
7 GDPR Principles (Article 5)
| Principle | Description | Key Requirements |
|---|---|---|
| Lawfulness, Fairness, Transparency | Legal basis, fair processing, clear communication | Privacy notices, consent forms, legitimate interest assessments |
| Purpose Limitation | Specific, explicit, legitimate purposes | Purpose documentation, no scope creep |
| Data Minimization | Adequate, relevant, limited to necessary | Justify each data element collected |
| Accuracy | Accurate and up to date | Data correction procedures |
| Storage Limitation | Kept no longer than necessary | Retention schedules, deletion procedures |
| Integrity and Confidentiality | Appropriate security | Encryption, access controls, pseudonymization |
| Accountability | Demonstrate compliance | Records of processing, DPIAs, policies |
6 Lawful Bases for Processing (Article 6)
Organizations must identify one lawful basis for each processing activity:
- Consent: Freely given, specific, informed, unambiguous
- Contract: Necessary for contract performance
- Legal Obligation: Required by EU/Member State law
- Vital Interests: Protect life of data subject or another
- Public Task: Official authority or public interest
- Legitimate Interests: Balancing test (not for public authorities)
Special Category Data (Article 9) requires additional lawful basis beyond Article 6.
Key Compliance Areas
Data Mapping and Inventory
- Systems processing personal data
- Data flows (collection, storage, transfer, deletion)
- Data categories and special categories
- Data subject types
- Retention periods
- Third-party processors
Privacy Notices
- Identity and contact of controller
- DPO contact (if applicable)
- Purposes and lawful basis
- Recipients of data
- International transfers
- Retention periods
- Data subject rights
- Right to withdraw consent
- Right to complain to supervisory authority
Data Subject Rights (8 Rights)
- Right to be informed
- Right of access (Article 15)
- Right to rectification (Article 16)
- Right to erasure/"right to be forgotten" (Article 17)
- Right to restriction of processing (Article 18)
- Right to data portability (Article 20)
- Right to object (Article 21)
- Rights related to automated decision-making (Article 22)
Security Measures (Article 32)
- Encryption and pseudonymization
- Confidentiality, integrity, availability
- Regular testing and evaluation
- Incident response capability
- Privacy by Design and Default (Article 25)
Records of Processing Activities (Article 30)
Required for organizations with:
- 250+ employees, OR
- High-risk processing, OR
- Regular processing of special categories/criminal data
Data Protection Impact Assessment (DPIA)
Required when processing likely to result in high risk:
- Systematic and extensive profiling
- Large-scale processing of special categories
- Systematic monitoring of public areas
- New technologies with high risk
Data Protection Officer (DPO)
Required for:
- Public authorities (except courts)
- Large-scale systematic monitoring
- Large-scale processing of special categories/criminal data
DPO Requirements:
- Professional qualities and expertise
- Adequate resources
- Independence (no conflict of interest)
- Direct reporting to highest management
- Contact point for supervisory authority
Cross-Border Data Transfers
Transfer Mechanisms:
- Adequacy Decision: EU Commission approved countries (UK, Switzerland, Japan, etc.)
- Standard Contractual Clauses (SCCs): EU-approved contracts
- Binding Corporate Rules (BCRs): Group-wide policies
- Certification Mechanisms: Approved certifications
- Derogations: Specific situations (consent, contract necessity, etc.)
Special Considerations:
- Schrems II decision impact (US transfers)
- Transfer Impact Assessments (TIAs)
- Supplementary measures beyond SCCs
Breach Notification Requirements
72-Hour Rule (Article 33):
- Notify supervisory authority within 72 hours of becoming aware
- Unless breach unlikely to result in risk to rights/freedoms
- Describe nature, categories, approximate numbers
- DPO contact information
- Likely consequences
- Measures taken/proposed
Data Subject Notification (Article 34):
- Required if high risk to rights and freedoms
- Clear and plain language
- Same information as supervisory authority
Supervisory Authorities
Lead Supervisory Authority:
- Based on main establishment in EU
- Coordinates cross-border processing investigations
Examples:
- CNIL (France)
- ICO (UK)
- EDPB (European Data Protection Board)
- National DPAs in each Member State
Penalties
Administrative Fines (Article 83):
- Tier 1: Up to €10M or 2% global annual turnover
- Processor obligations, certification, monitoring body
- Tier 2: Up to €20M or 4% global annual turnover
- Core principles, lawful basis, data subject rights
- Cross-border transfer violations
- Supervisory authority orders
Factors Considered:
- Nature, gravity, duration
- Intentional or negligent
- Mitigation actions
- Previous infringements
- Cooperation with authority
- Categories of data affected
- Manner authority became aware
Examples
# Full GDPR compliance assessment
/gdpr:assess full
# Data mapping and inventory focus
/gdpr:assess data-mapping
# Data subject rights implementation check
/gdpr:assess rights-management
# Security measures evaluation
/gdpr:assess security-measures
# Assessment as data controller
/gdpr:assess full controller
# Assessment as data processor
/gdpr:assess full processor
Assessment Timeline
Typical GDPR Compliance Journey:
- Gap Assessment: 2-4 weeks
- Data Mapping: 4-8 weeks
- Policy Development: 4-6 weeks
- Technical Implementation: 3-9 months
- Training and Awareness: Ongoing
- Ongoing Compliance: Continuous monitoring
Breach Notification Process
Guides compliance with GDPR breach notification requirements under Articles 33 (supervisory authority) and 34 (data subjects).
Arguments
$1- Breach severity (optional: low, moderate, high, critical)$2- Process phase (optional: detection, assessment, notification, documentation)
Definition of Personal Data Breach
Article 4(12): "A breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, personal data transmitted, stored or otherwise processed."
Three Types of Breach
-
Confidentiality Breach
- Unauthorized or accidental disclosure
- Unauthorized access
- Examples: Hacking, lost laptop, email to wrong recipient
-
Integrity Breach
- Unauthorized or accidental alteration
- Data corruption or modification
- Examples: Ransomware, database manipulation, accidental deletion
-
Availability Breach
- Accidental or unauthorized loss of access
- Destruction of data
- Examples: Ransomware, DDoS, system failure, natural disaster
Note: A single incident can involve multiple breach types
The 72-Hour Rule (Article 33)
Notification to Supervisory Authority
Obligation:
- Notify supervisory authority without undue delay
- Within 72 hours of becoming aware (where feasible)
- If >72 hours, must explain delay
"Becoming Aware":
- When reasonable degree of certainty breach occurred
- Not when initially suspected
- Clock starts when controller has information to conclude breach likely
- Ongoing investigation does not pause clock
When Notification NOT Required
Exception (Article 33(1)):
- Breach is unlikely to result in a risk to rights and freedoms of individuals
Risk Assessment Factors:
- Type and volume of data
- Ease of identification
- Severity and likelihood of consequences
- Special characteristics of data subject (vulnerable individuals)
- Special characteristics of controller (healthcare, financial)
- Number of affected individuals
Notification Content (Article 33(3))
Minimum Required Information:
-
Nature of breach
- Categories of data subjects affected
- Approximate number of data subjects
- Categories of personal data records
- Approximate number of records
-
Contact point
- Name and contact details of DPO or other contact
- Where more information can be obtained
-
Likely consequences
- Describe likely consequences of breach
- Potential adverse effects on individuals
-
Measures taken/proposed
- Measures taken to address breach
- Measures to mitigate adverse effects
- Remediation steps
Phased Notification
Article 33(4): If information not available within 72 hours:
- Provide initial notification with available information
- Provide additional information in phases "without undue further delay"
- Explain reasons for delay
Typical Phased Approach:
- Initial (<72h): Breach type, approximate scope, contact point
- Update 1 (1-2 weeks): Confirmed numbers, detailed consequences
- Final (ongoing): Remediation complete, lessons learned
Notification to Data Subjects (Article 34)
When Required
Mandatory notification if:
- Breach likely to result in high risk to rights and freedoms
High Risk Factors:
- Special category data (health, biometric, racial, etc.)
- Financial data (credit cards, bank details)
- Credentials (passwords, especially if not hashed)
- Large-scale breach
- Vulnerable data subjects (children)
- Significant adverse effects (discrimination, identity theft, financial loss, reputational damage)
Notification Content
Communicate in clear and plain language:
- Nature of breach: What happened
- Contact point: DPO or contact for more information
- Likely consequences: Potential impacts on individuals
- Measures taken/proposed: Steps to mitigate
- Recommended actions: What individuals should do (change passwords, monitor accounts, etc.)
Timing
- Without undue delay
- No specific deadline (unlike 72-hour rule for authority)
- As soon as possible after discovery
- May notify authority first to seek guidance
When Notification NOT Required
Exceptions (Article 34(3)):
-
Appropriate safeguards applied (Article 34(3)(a))
- Encryption or pseudonymization rendered data unintelligible
- Example: Stolen encrypted laptop with strong encryption
-
Subsequent measures taken (Article 34(3)(b))
- Controller took measures ensuring high risk no longer likely
- Example: Deleted data before unauthorized party accessed it
-
Disproportionate effort (Article 34(3)(c))
- Public communication or similar measure
- Equally effective
- Example: Cannot identify/contact affected individuals, public notice instead
Methods of Communication
Direct Individual Notification:
- Email (preferred if available)
- Mail (postal)
- Phone
- SMS
- In-app notification
Public Communication (if disproportionate):
- Press release
- Website notice (prominent)
- Social media
- Paid advertising
Breach Response Process
Phase 1: Detection and Containment (Hours 0-4)
Immediate Actions:
- Detect and verify breach occurred
- Contain breach (stop ongoing unauthorized access)
- Preserve evidence (logs, forensic data)
- Assemble response team (IT, security, legal, DPO, communications)
- Initial assessment of scope and severity
Key Questions:
- What happened?
- When did it occur?
- Is it ongoing?
- What systems/data affected?
- How many individuals potentially affected?
Phase 2: Assessment (Hours 4-24)
Detailed Investigation:
- Root cause analysis: How did breach occur?
- Scope determination: What data accessed/lost/altered?
- Impact assessment: What are consequences for individuals?
- Risk assessment: Likelihood and severity of adverse effects
- Count affected individuals: Exact or approximate numbers
- Identify data categories: Personal data, special categories, credentials
Risk Assessment:
- Low: Minimal impact, unlikely adverse effects
- Moderate: Some potential for harm
- High: Significant adverse effects likely
- Critical: Severe consequences (special categories, credentials, large scale)
Phase 3: Notification Decision (Hours 24-48)
Determine Notification Obligations:
Supervisory Authority (Article 33):
- Is risk unlikely? → No notification required
- Is risk possible/likely? → Notification required (<72h)
Data Subjects (Article 34):
- Is risk high? → Notification required (without undue delay)
- Are exceptions applicable? → May not be required
Consult DPO:
- DPO must be involved in breach response
- Seek advice on notification decisions
- Document DPO recommendations
Phase 4: Notification (Hours 48-72)
To Supervisory Authority (if required):
- Prepare notification with Article 33(3) content
- Submit to lead supervisory authority
- Online portal (if available)
- Email or designated contact
- Specify if phased notification planned
- Confirm receipt and note case reference
- Cooperate with authority investigation
To Data Subjects (if required):
- Prepare communications in clear language
- Identify affected individuals and contact methods
- Coordinate messaging (avoid panic, provide guidance)
- Send notifications via appropriate channels
- Set up helpline/FAQ for inquiries
- Monitor for questions and concerns
Phase 5: Remediation (Ongoing)
Immediate Remediation:
- Close security gaps that caused breach
- Reset credentials if compromised
- Restore data from backups if lost
- Implement additional safeguards
Short-Term Actions:
- Monitoring for signs of data misuse
- Support for affected individuals (credit monitoring, ID theft services)
- Updates to authority and individuals as investigation progresses
Long-Term Actions:
- Root cause remediation (fix underlying issues)
- Policy/procedure updates (prevent recurrence)
- Staff training (address human factors)
- Security improvements (defense in depth)
- Lessons learned exercise
Phase 6: Documentation (Ongoing)
Record of Breach (Article 33(5)):
- Document all breaches (even those not notified)
- Facts of breach
- Effects of breach
- Remedial action taken
Purpose:
- Demonstrate compliance
- Supervisory authority can verify compliance
- Learn from incidents
Breach Register Should Include:
- Date/time of breach
- Date/time became aware
- Description of breach (type, cause)
- Categories and volume of data
- Number of individuals affected
- Consequences and likely adverse effects
- Measures taken to address breach
- Whether authority notified (date, reference)
- Whether individuals notified (date, method)
- Reasoning if not notified
- Communications and decisions
- DPO involvement
- Lessons learned and preventive measures
Special Considerations
Processor Breaches (Article 33(2))
Processor obligations:
- Notify controller without undue delay after becoming aware
- No specific timeframe (unlike controller's 72 hours)
- Controller then has notification obligations
Processor should provide:
- Detailed breach information
- Affected clients/controllers
- Scope and impact assessment
- Remediation steps
Data Processing Agreement should specify:
- Breach notification procedures
- Timeframes (recommend <24 hours)
- Information to be provided
- Cooperation with controller
Cross-Border Breaches
Lead Supervisory Authority (Article 56):
- Notify lead authority (main establishment)
- Lead authority coordinates with other concerned authorities
- One-stop-shop mechanism
Concerned Authorities:
- Lead authority may inform other authorities
- Cooperation through mutual assistance
- Consistent approach across Member States
Third-Country Transfers
Breach involving data transferred outside EU:
- Same notification requirements apply
- Complexity in identifying individuals
- May need to notify multiple authorities
- Consider local breach notification laws (e.g., US state laws)
Ransomware
Unique considerations:
- Availability breach (minimum)
- Likely confidentiality breach (assume data exfiltrated)
- Do NOT pay ransom before assessment
- Notify authority even if ransom paid
- Cannot assume data not accessed/disclosed
Supervisory Authority Responses
Possible Actions:
- Request additional information
- Investigation/audit
- Corrective measures (improve security, notify individuals)
- Warnings or reprimands
- Temporary/permanent processing ban
- Administrative fines
Cooperation:
- Respond promptly to authority requests
- Provide requested evidence
- Implement recommended measures
- Maintain open communication
Penalties for Non-Compliance
Failure to notify (Article 83):
- Up to €10M or 2% of global annual turnover (whichever higher)
- Factors: Intentional or negligent, cooperation, previous infringements
Related violations (higher fines):
- Up to €20M or 4% if breach caused by failure to implement security (Article 32)
Breach Notification Tools
Breach Assessment Questionnaire
- What type of breach occurred? (confidentiality, integrity, availability)
- What personal data categories affected?
- Any special category data?
- How many individuals affected?
- What are potential consequences for individuals?
- What safeguards were in place? (encryption, etc.)
- What immediate actions taken?
- Can breach be contained?
Risk Matrix
| Data Type | Volume | Safeguards | Risk Level | Notify Authority? | Notify Individuals? |
|---|---|---|---|---|---|
| Contact info | <100 | None | Low | No | No |
| Contact info | >1000 | None | Moderate | Yes | No |
| Financial | Any | None | High | Yes | Yes |
| Health/Biometric | Any | None | Critical | Yes | Yes |
| Any | Any | Encrypted | Low | Assess | Likely No |
Notification Timeline Template
| Milestone | Deadline | Responsible | Status |
|---|---|---|---|
| Breach detected | T+0 | IT/Security | |
| Response team assembled | T+2h | Incident Manager | |
| Scope assessed | T+24h | Investigation Team | |
| Notification decision | T+48h | DPO + Legal | |
| Authority notification | T+72h | DPO | |
| Individual notification | T+96h | Communications | |
| Initial remediation | T+1 week | IT/Security |
Examples
# Guide breach response for critical severity breach
/gdpr:breach-process critical
# Assess notification requirements for moderate breach
/gdpr:breach-process moderate assessment
# Document breach that has been detected
/gdpr:breach-process high detection
# Prepare notifications for high-risk breach
/gdpr:breach-process high notification
# Review overall breach response procedures
/gdpr:breach-process
# Low severity breach documentation
/gdpr:breach-process low documentation
Common Mistakes to Avoid
- Waiting for complete information: Notify within 72h even if incomplete, update later
- Delaying while investigating: Clock starts when "becoming aware" (reasonable certainty)
- Not documenting non-notified breaches: Article 33(5) requires all breaches documented
- Generic notifications: Be specific about breach, consequences, actions
- Not involving DPO: DPO must advise on breach response
- Ignoring processor breaches: Processors must notify controllers promptly
- No breach response plan: Plan and test breach procedures in advance
- Focusing only on notification: Remediation and prevention equally important
- Not training staff: Employees must know how to recognize and report breaches
- Underestimating risk: When in doubt, notify (better safe than fined)
Breach Preparedness
Incident Response Plan
Include:
- Breach definition and examples
- Reporting procedures (internal)
- Response team roles (IT, security, legal, DPO, communications, management)
- Containment procedures
- Investigation checklists
- Assessment criteria (risk levels)
- Notification decision trees
- Communication templates
- Contact lists (supervisory authority, affected parties, vendors)
- Escalation procedures
- Training and testing schedule
Regular Testing
Exercises:
- Tabletop exercises (quarterly)
- Simulated breaches (annually)
- Update procedures based on lessons learned
- Test notification procedures (without sending)
- Validate contact lists
Staff Training
All Staff:
- Recognize and report potential breaches
- Don't delay reporting
- Preserve evidence
Response Team:
- Detailed procedures
- Roles and responsibilities
- Tools and systems
- Communication protocols
- Legal obligations
Management:
- Oversight and approval
- Resource allocation
- Authority engagement
- Public communications
DPIA - Data Protection Impact Assessment
Guides the execution of a Data Protection Impact Assessment as required by GDPR Article 35.
Arguments
$1- Processing activity name (required)$2- DPIA stage (optional: screening, assessment, review)
When DPIA Required
Article 35(3) mandates DPIA for processing likely to result in high risk, particularly:
Mandatory DPIA Scenarios
-
Systematic and Extensive Profiling
- Automated processing with legal/similar significant effects
- Example: Credit scoring, insurance profiling, algorithmic hiring
-
Large-Scale Processing of Special Categories
- Special category data (Article 9): race, health, biometrics, etc.
- Criminal conviction data (Article 10)
- Example: Hospital patient records, genetic testing, background checks
-
Systematic Monitoring of Public Areas
- Large-scale public surveillance
- Example: CCTV networks, smart city sensors
Additional High-Risk Indicators (WP29 Criteria)
DPIA recommended when processing meets 2+ criteria:
- Evaluation/scoring (including profiling)
- Automated decision-making with legal effect
- Systematic monitoring
- Sensitive data processing
- Large-scale processing
- Matching/combining datasets
- Vulnerable data subjects (children, employees)
- Innovative technology use
- Processing preventing data subjects from exercising rights
- Transfer outside EU
Exemptions
DPIA not required when:
- Legal basis is legal obligation or public task, AND
- Processing has legal basis in EU/Member State law, AND
- DPIA already conducted as part of general impact assessment
DPIA Process (5 Steps)
1. Screening (Threshold Assessment)
Determine if DPIA required:
- Review mandatory scenarios
- Apply WP29 9 criteria test
- Check supervisory authority "DPIA lists"
- Document screening decision
Output: Go/No-Go decision with justification
2. Description of Processing
Systematic description including:
- Nature of processing (what, why, how)
- Purposes of processing
- Lawful basis for processing
- Legitimate interests (if applicable)
- Personal data categories
- Special category data
- Data subject categories
- Recipients of data (internal, external, third countries)
- Data flows (collection → storage → use → deletion)
- Retention periods
- Technical and organizational measures
- Third-party processors involved
- Functional description of system/technology
Key Questions:
- What personal data is processed?
- Why is it processed?
- How is it processed (automated, manual)?
- Who has access?
- Where is it stored/transferred?
- How long is it kept?
3. Necessity and Proportionality Assessment
Evaluate:
- Compliance with GDPR principles (Article 5)
- Necessity: Could purposes be achieved with less data?
- Proportionality: Is processing appropriate for purposes?
- Alternative means: Are there less intrusive options?
- Data minimization: Only necessary data collected?
- Storage limitation: Retention periods justified?
- Purpose limitation: Clear, specific purposes?
Data Protection by Design and Default (Article 25):
- Pseudonymization where possible
- Encryption of personal data
- Minimized data collection
- Transparency measures
- Enable data subject rights
- Privacy-preserving defaults
4. Risk Assessment
Identify Risks to Data Subjects:
Risk Categories:
- Illegal access (data breach, hacking)
- Unwanted modification (data alteration, corruption)
- Disappearance (data loss, deletion)
- Disclosure (unauthorized sharing, surveillance)
Risk to Rights and Freedoms:
- Discrimination
- Identity theft/fraud
- Financial loss
- Reputational damage
- Loss of confidentiality (medical, professional)
- Economic/social disadvantage
- Deprivation of rights
- Physical harm
- Psychological harm
Risk Assessment Matrix:
| Severity | Likelihood | Risk Level | Action Required |
|---|---|---|---|
| High | Likely | Critical | Must mitigate before processing |
| High | Possible | High | Strong mitigation required |
| Medium | Likely | High | Strong mitigation required |
| Medium | Possible | Moderate | Mitigation recommended |
| Low | Unlikely | Low | Accept or basic mitigation |
For Each Risk:
- Source (threat)
- Potential impact on data subjects
- Severity (negligible, limited, significant, maximum)
- Likelihood (negligible, possible, likely, maximum)
- Overall risk level
5. Risk Mitigation Measures
Identify and Implement Safeguards:
Technical Measures:
- Encryption (at rest, in transit, end-to-end)
- Pseudonymization and anonymization
- Access controls (role-based, least privilege)
- Authentication (MFA, strong passwords)
- Network security (firewalls, segmentation)
- Logging and monitoring
- Data loss prevention (DLP)
- Secure deletion/disposal
- Regular security testing
Organizational Measures:
- Policies and procedures
- Privacy notices and transparency
- Consent management
- Data minimization practices
- Retention and deletion schedules
- Staff training and awareness
- Incident response plan
- Vendor management (DPA clauses)
- Data subject rights procedures
- Regular audits and reviews
Governance Measures:
- DPO involvement and oversight
- Privacy by Design integration
- Third-party assessments
- Compliance monitoring
- Documentation and accountability
Residual Risk:
- Re-assess risks after mitigation
- Document residual risk acceptance
- If high residual risk → consult supervisory authority
Consultation Requirements
Consult Data Protection Officer (DPO)
- Article 35(2): DPO must provide advice
- Involve DPO throughout DPIA process
- Document DPO input and recommendations
Consult Data Subjects (Where Appropriate)
- Article 35(9): Seek views of data subjects/representatives
- Not always required but recommended
- Methods: Surveys, focus groups, privacy advocates
- Document consultation outcomes
Consult Supervisory Authority (If High Residual Risk)
- Article 36: Prior consultation required if:
- DPIA shows high risk, AND
- Controller cannot sufficiently mitigate risk
- Submit DPIA and proposed measures
- Authority provides written advice within 8 weeks (extendable)
- Must not process until consultation complete
DPIA Documentation
Required Content (Article 35)
- Systematic description of processing operations and purposes
- Assessment of necessity and proportionality
- Assessment of risks to rights and freedoms
- Measures to address risks including safeguards, security, compliance demonstration
Additional Best Practice Elements
- Executive summary
- DPIA scope and boundaries
- Data controller and DPO details
- Lawful basis and legitimate interests
- Data flow diagrams
- Third-party processors list
- Privacy by Design measures
- Data subject rights implementation
- Compliance checklist (7 principles, rights, obligations)
- Sign-off and approval records
- Review schedule
Review and Update DPIA
Triggers for Review:
- Planned review schedule (e.g., annually)
- Changes to processing operations
- New risks identified
- Technology changes
- Legal/regulatory changes
- Supervisory authority guidance
- Data breaches or incidents
- Organizational changes (merger, acquisition)
Review Process:
- Assess if changes trigger new DPIA
- Update existing DPIA if appropriate
- Re-evaluate risks and mitigation
- Consult DPO on changes
- Document review and updates
- Obtain new approvals if needed
Supervisory Authority DPIA Lists
Positive Lists: Processing requiring DPIA Negative Lists: Processing not requiring DPIA
Check your jurisdiction's DPA for:
- Country-specific DPIA requirements
- Industry-specific guidance (healthcare, finance, etc.)
- Technology-specific guidance (AI, biometrics, etc.)
Examples
# Screen whether DPIA is required for new customer analytics system
/gdpr:dpia "Customer Analytics Platform" screening
# Conduct full DPIA for employee monitoring system
/gdpr:dpia "Employee Monitoring System" assessment
# Review existing DPIA for mobile app processing
/gdpr:dpia "Mobile App User Data" review
# DPIA for AI-powered recruitment tool
/gdpr:dpia "AI Recruitment Tool"
# DPIA for health data processing
/gdpr:dpia "Patient Health Portal" assessment
DPIA Templates and Resources
Official Guidance:
- WP29 Guidelines on DPIA (WP248 rev.01)
- ICO DPIA guidance and template
- CNIL PIA methodology and tools
- EDPB Guidelines 09/2020 on relevant criteria
Template Sections (Typical Structure):
- Introduction (Purpose, scope, DPIA team)
- Screening Assessment (Threshold determination)
- Processing Description (What, why, how)
- Necessity and Proportionality (Compliance with principles)
- Consultation (DPO, data subjects, stakeholders)
- Risk Assessment (Identified risks, severity, likelihood)
- Risk Treatment (Mitigation measures, residual risk)
- Sign-off (Controller approval, DPO review)
- Review Schedule (Next review date, triggers)
Common DPIA Mistakes to Avoid
- Treating DPIA as checkbox exercise - Must be meaningful risk assessment
- Not involving DPO early - DPO must advise throughout
- Ignoring data subject consultation - Required where appropriate
- Generic risk assessments - Risks must be specific to processing
- Inadequate mitigation - High risks require strong safeguards
- No review process - DPIAs must be living documents
- Skipping prior consultation - Required if high residual risk remains
- Poor documentation - DPIA must demonstrate accountability
Output Format
The DPIA assessment provides:
- DPIA Necessity Determination: Required/Not Required with justification
- Processing Description: Comprehensive systematic description
- Compliance Analysis: Assessment against GDPR principles
- Risk Register: Identified risks with severity/likelihood
- Mitigation Plan: Technical and organizational measures
- Residual Risk Assessment: Remaining risks after mitigation
- Consultation Records: DPO, data subjects, authority (if needed)
- Approval and Review: Sign-off and next review date
- Action Items: Specific tasks to complete before/during processing
GDPR Evidence Checklist
Generates comprehensive evidence collection checklists for EU General Data Protection Regulation (GDPR) compliance with focus on technical and organizational measures (TOMs) and data processing activities.
Never commit evidence artifacts to source control. The outputs below include real usernames, credential reports, MFA device states, and privileged-account inventories. For GDPR workflows, raw exports may carry personal data subject to Art. 5 minimization and storage-limitation rules. Keep only what you need and delete on a retention schedule.
.gitignorecoversevidence/by default sogit add -Awill not sweep it up, but durable storage is your responsibility. Use an encrypted, access-controlled evidence locker (encrypted S3 with least-privilege IAM, a GRC platform, or a shared drive with full-disk encryption and MFA-gated access).
Usage
/gdpr:evidence-checklist <article|principle> [--role <controller|processor>] [--export <format>]
Arguments
<article|principle>: GDPR article (e.g., "Article 32", "Article 30") or principle (e.g., "Security", "Data Subject Rights", "Lawfulness")--role: Organization role (controller,processor, orboth). Default:controller--export: Export format (json,csv,markdown). Default:markdown
Example: Article 32 Security of Processing Evidence
/gdpr:evidence-checklist "Article 32" --role controller
Output:
GDPR Evidence Checklist
Article: Article 32 - Security of Processing
Role: Data Controller
Applicable To: All organizations processing personal data of EU residents
Enforcement: EU Data Protection Authorities (DPAs)
Maximum Penalty: €10 million or 2% of worldwide annual revenue (whichever higher)
## Article 32 Requirements
The controller and the processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate:
(a) the pseudonymisation and encryption of personal data;
(b) the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services;
(c) the ability to restore the availability and access to personal data in a timely manner in the event of a physical or technical incident;
(d) a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing.
## Evidence Requirements
### Required Documentation (TOMs - Technical and Organizational Measures)
□ **Information Security Policy**
- Scope: All personal data processing activities
- Required elements:
- Encryption requirements (at rest, in transit)
- Access control measures
- Incident response procedures
- Data retention and deletion
- Third-party security (processors)
- Update frequency: Annually
- Approver: Data Protection Officer (DPO) and senior management
- Evidence: Signed Information Security Policy v1.x
□ **Data Processing Inventory (Article 30 - Records of Processing)**
- All processing activities documented
- Required elements for each activity:
- Purpose of processing
- Categories of personal data
- Categories of data subjects
- Recipients (including third countries)
- Retention periods
- Technical and organizational security measures
- Evidence: Article 30 Record of Processing Activities (ROPA)
- Frequency: Updated when processing changes, reviewed annually
□ **Data Protection Impact Assessment (DPIA) for High-Risk Processing**
- Required when: New technology, profiling, large-scale sensitive data, public monitoring
- Required elements:
- Description of processing and purposes
- Assessment of necessity and proportionality
- Risk assessment (rights and freedoms)
- Mitigation measures
- DPO consultation
- Evidence: Completed DPIA for high-risk processing
- Frequency: Before commencing high-risk processing
□ **Data Processing Agreements (DPA) with Processors**
- Contract with every processor (Article 28)
- Required clauses:
- Subject matter, duration, nature, purpose
- Processor obligations (confidentiality, security, sub-processors)
- Controller audit rights
- Data breach notification (72 hours)
- Data deletion/return after termination
- Evidence: Signed DPAs with all processors
- Frequency: Before engaging processor, reviewed every 2 years
□ **Data Breach Response Plan**
- Documented breach notification procedures
- 72-hour notification to DPA requirement
- Data subject notification criteria
- Breach investigation procedures
- Evidence: Breach Response Plan v1.x
- Frequency: Annual review and testing
### Automated Evidence Collection
✓ **Encryption at Rest Evidence**
```bash
# AWS - S3 bucket encryption status
aws s3api list-buckets --output json | jq -r '.Buckets[].Name' | while read bucket; do
encryption=$(aws s3api get-bucket-encryption --bucket "$bucket" 2>&1)
if echo "$encryption" | grep -q "ServerSideEncryptionConfigurationNotFoundError"; then
echo "$bucket,NOT ENCRYPTED" >> evidence/gdpr-art32-s3-encryption-$(date +%Y%m%d).csv
else
echo "$bucket,ENCRYPTED" >> evidence/gdpr-art32-s3-encryption-$(date +%Y%m%d).csv
fi
done
# RDS encryption
aws rds describe-db-instances --query 'DBInstances[].[DBInstanceIdentifier,StorageEncrypted]' \
--output json > evidence/gdpr-art32-rds-encryption-$(date +%Y%m%d).json
# EBS volume encryption
aws ec2 describe-volumes --query 'Volumes[].[VolumeId,Encrypted,KmsKeyId]' \
--output json > evidence/gdpr-art32-ebs-encryption-$(date +%Y%m%d).json
# Azure - Storage account encryption
az storage account list --query '[].{Name:name,Encryption:encryption.services}' \
--output json > evidence/gdpr-art32-azure-encryption-$(date +%Y%m%d).json
# GCP - Cloud Storage bucket encryption
gsutil ls | while read bucket; do
encryption=$(gsutil encryption get "$bucket")
echo "$bucket: $encryption" >> evidence/gdpr-art32-gcp-encryption-$(date +%Y%m%d).txt
done
Collection Frequency: Monthly Retention: 3 years (minimum for GDPR compliance evidence) Purpose: Demonstrates encryption at rest (Article 32(1)(a))
✓ Encryption in Transit Evidence
# AWS - Application Load Balancer HTTPS enforcement
aws elbv2 describe-load-balancers --output json | \
jq '.LoadBalancers[] | {Name: .LoadBalancerName, Scheme: .Scheme}' \
> evidence/gdpr-art32-alb-$(date +%Y%m%d).json
aws elbv2 describe-listeners --load-balancer-arn <ARN> | \
jq '.Listeners[] | select(.Protocol == "HTTPS")' \
>> evidence/gdpr-art32-https-listeners-$(date +%Y%m%d).json
# CloudFront TLS versions
aws cloudfront list-distributions --query 'DistributionList.Items[].[Id,ViewerCertificate.MinimumProtocolVersion]' \
--output json > evidence/gdpr-art32-cloudfront-tls-$(date +%Y%m%d).json
# Check for TLS 1.2+ (TLS 1.0/1.1 not secure)
aws cloudfront list-distributions --output json | \
jq '.DistributionList.Items[] | select(.ViewerCertificate.MinimumProtocolVersion < "TLSv1.2")' \
> evidence/gdpr-art32-insecure-tls-$(date +%Y%m%d).json
Collection Frequency: Monthly Retention: 3 years Purpose: Demonstrates encryption in transit (Article 32(1)(a))
✓ Access Control Evidence
# AWS IAM user inventory (should minimize IAM users, prefer SSO)
aws iam list-users --output json > evidence/gdpr-art32-iam-users-$(date +%Y%m%d).json
# IAM credential report (shows password age, MFA status)
aws iam generate-credential-report
aws iam get-credential-report --output text | base64 -d \
> evidence/gdpr-art32-credential-report-$(date +%Y%m%d).csv
# Users without MFA (non-compliant)
aws iam get-credential-report --output text | base64 -d | \
awk -F',' '$4 == "true" && $8 == "false" {print $1}' \
> evidence/gdpr-art32-no-mfa-$(date +%Y%m%d).txt
# S3 bucket public access (should be blocked for personal data)
aws s3api list-buckets --output json | jq -r '.Buckets[].Name' | while read bucket; do
public=$(aws s3api get-bucket-acl --bucket "$bucket" | grep -i "AllUsers\|AuthenticatedUsers")
if [ ! -z "$public" ]; then
echo "$bucket is PUBLIC" >> evidence/gdpr-art32-public-s3-$(date +%Y%m%d).txt
fi
done
# RDS public accessibility (should be false for personal data)
aws rds describe-db-instances --query 'DBInstances[].[DBInstanceIdentifier,PubliclyAccessible]' \
--output json > evidence/gdpr-art32-rds-public-$(date +%Y%m%d).json
Collection Frequency: Weekly Retention: 3 years Purpose: Access control measures (Article 32(1)(b))
✓ Backup and Recovery Evidence
# AWS Backup jobs (last 30 days)
aws backup list-backup-jobs \
--by-created-after $(date -u -d '30 days ago' +%Y-%m-%dT%H:%M:%S) \
--output json > evidence/gdpr-art32-backup-jobs-$(date +%Y%m).json
# RDS automated backups
aws rds describe-db-instances \
--query 'DBInstances[].[DBInstanceIdentifier,BackupRetentionPeriod,PreferredBackupWindow]' \
--output json > evidence/gdpr-art32-rds-backups-$(date +%Y%m%d).json
# EBS snapshots (for EC2 volumes)
aws ec2 describe-snapshots --owner-ids self \
--query 'Snapshots[?StartTime>=`2024-01-01`].[SnapshotId,VolumeId,StartTime,State]' \
--output json > evidence/gdpr-art32-ebs-snapshots-$(date +%Y%m%d).json
# S3 versioning (for data recovery)
aws s3api list-buckets --output json | jq -r '.Buckets[].Name' | while read bucket; do
versioning=$(aws s3api get-bucket-versioning --bucket "$bucket")
echo "$bucket: $versioning" >> evidence/gdpr-art32-s3-versioning-$(date +%Y%m%d).txt
done
Collection Frequency: Monthly Retention: 3 years Purpose: Data availability and resilience (Article 32(1)(c))
✓ Security Monitoring Evidence
# AWS GuardDuty findings (threat detection)
aws guardduty list-findings \
--detector-id $(aws guardduty list-detectors --query 'DetectorIds[0]' --output text) \
--finding-criteria '{"Criterion":{"severity":{"Gte":7},"updatedAt":{"Gte":'$(date -d '30 days ago' +%s%3N)'}}}' \
--output json > evidence/gdpr-art32-guardduty-$(date +%Y%m).json
# Security Hub findings
aws securityhub get-findings \
--filters '{"SeverityLabel":[{"Value":"CRITICAL","Comparison":"EQUALS"},{"Value":"HIGH","Comparison":"EQUALS"}],"RecordState":[{"Value":"ACTIVE","Comparison":"EQUALS"}]}' \
--output json > evidence/gdpr-art32-securityhub-$(date +%Y%m%d).json
# CloudTrail events (audit trail)
aws cloudtrail lookup-events \
--lookup-attributes AttributeKey=EventName,AttributeValue=DeleteBucket \
--start-time $(date -u -d '30 days ago' +%Y-%m-%dT%H:%M:%S) \
--output json > evidence/gdpr-art32-deletion-events-$(date +%Y%m).json
# VPC Flow Logs enabled (network monitoring)
aws ec2 describe-vpcs --output json | jq -r '.Vpcs[].VpcId' | while read vpc; do
flowlogs=$(aws ec2 describe-flow-logs --filter "Name=resource-id,Values=$vpc" --query 'FlowLogs[].FlowLogStatus')
echo "$vpc: $flowlogs" >> evidence/gdpr-art32-flow-logs-$(date +%Y%m%d).txt
done
Collection Frequency: Monthly Retention: 3 years Purpose: Ongoing monitoring and testing (Article 32(1)(d))
✓ Data Deletion Evidence (Right to Erasure - Article 17)
# S3 lifecycle policies (automated deletion after retention period)
aws s3api list-buckets --output json | jq -r '.Buckets[].Name' | while read bucket; do
lifecycle=$(aws s3api get-bucket-lifecycle-configuration --bucket "$bucket" 2>&1)
if echo "$lifecycle" | grep -q "NoSuchLifecycleConfiguration"; then
echo "$bucket,NO LIFECYCLE POLICY" >> evidence/gdpr-art32-lifecycle-$(date +%Y%m%d).csv
else
echo "$bucket,HAS LIFECYCLE POLICY" >> evidence/gdpr-art32-lifecycle-$(date +%Y%m%d).csv
echo "$lifecycle" >> evidence/gdpr-art32-lifecycle-details-$(date +%Y%m%d).json
fi
done
# RDS retention periods (should align with GDPR retention)
aws rds describe-db-instances \
--query 'DBInstances[].[DBInstanceIdentifier,BackupRetentionPeriod]' \
--output json > evidence/gdpr-art32-retention-$(date +%Y%m%d).json
Collection Frequency: Quarterly Retention: 3 years Purpose: Data minimization and storage limitation principles
Manual Evidence Collection
□ Article 30 Record of Processing Activities (ROPA)
- Complete inventory of all processing activities
- For each processing activity, document:
- Name and contact details of controller/processor
- Purposes of processing
- Categories of data subjects (employees, customers, etc.)
- Categories of personal data (names, emails, financial, etc.)
- Categories of recipients (third parties, sub-processors)
- Transfers to third countries (if applicable)
- Retention periods
- Technical and organizational security measures (TOMs)
- Evidence: ROPA spreadsheet or GRC tool export
- Frequency: Annual review, update when processing changes
- CRITICAL: Required for all controllers (Article 30(1)) and processors (Article 30(2))
□ Data Protection Impact Assessment (DPIA) for High-Risk Processing
- Required when: automated decision-making, large-scale profiling, large-scale sensitive data, systematic monitoring of public areas, innovative technology
- Template: ICO DPIA template or similar
- Required sections:
- Description of processing and business need
- Consultation with DPO
- Necessity and proportionality assessment
- Risk to rights and freedoms (likelihood + severity)
- Measures to mitigate risks
- Sign-off by senior management
- Evidence: Completed DPIA documents (one per high-risk processing)
- Frequency: Before starting high-risk processing, review every 2 years
□ Data Processing Agreements (DPAs) with Processors
- Must have DPA with every processor (cloud providers, SaaS vendors, etc.)
- Use Standard Contractual Clauses (SCCs) for non-EU processors
- Required elements (Article 28(3)):
- Process only on documented instructions
- Confidentiality obligations
- Security measures (Article 32)
- Sub-processor restrictions and notification
- Data subject rights assistance
- Deletion/return of data after termination
- Audit rights for controller
- Evidence: Signed DPAs with all processors (AWS, Azure, GCP, SaaS vendors)
- Frequency: Before engaging processor, review every 2 years
□ Data Breach Register
- Log of all data breaches (even if not notified to DPA)
- Required elements for each breach:
- Date/time discovered
- Nature of breach (confidentiality, integrity, availability)
- Categories and approximate number of data subjects affected
- Categories and approximate number of records affected
- Likely consequences
- Measures taken to mitigate
- DPA notification (Y/N, date)
- Data subject notification (Y/N, date)
- Evidence: Breach register (Excel or GRC tool)
- Frequency: Ongoing (log all breaches within 72 hours)
- CRITICAL: Must notify DPA within 72 hours if risk to rights (Article 33)
□ Data Subject Rights Request Log
- Log of all data subject requests (access, rectification, erasure, portability, objection, restriction)
- Required elements:
- Request date
- Request type (SAR, erasure, etc.)
- Data subject identity verification
- Response date (must be <30 days)
- Outcome (granted, denied, partial)
- Denial justification (if denied)
- Evidence: DSR log (Excel or GRC tool)
- Frequency: Ongoing
□ Penetration Test / Vulnerability Assessment
- Annual penetration test or vulnerability assessment
- Scope: Systems processing personal data
- Required elements:
- Test scope and methodology
- Findings (vulnerabilities identified)
- Risk ratings (critical, high, medium, low)
- Remediation plan with timelines
- Re-test results (for critical/high findings)
- Evidence: Penetration test report + remediation tracking
- Frequency: Annually (Article 32(1)(d) - regular testing)
□ Staff Security Awareness Training
- All staff handling personal data must be trained
- Topics: GDPR principles, data subject rights, breach reporting, secure data handling
- Evidence: Training completion records, training materials, attendance registers
- Frequency: Annually, on hire for new staff
□ Data Retention and Deletion Procedures
- Documented retention periods for each processing activity (align with ROPA)
- Automated deletion procedures (where possible)
- Manual review process for legacy data
- Evidence: Retention schedule + deletion logs
- Frequency: Annual review of retention schedule
GDPR Compliance Assessment
Data Protection Authorities will assess:
Documentation Review
✓ Article 30 ROPA completed and up-to-date ✓ DPIAs for high-risk processing ✓ Data Processing Agreements with all processors ✓ Privacy notices published and comprehensive ✓ Data breach register maintained ✓ DSR request log maintained ✓ TOMs documented (encryption, access control, etc.)
Implementation Review
✓ Encryption at rest for personal data ✓ Encryption in transit (TLS 1.2+) ✓ Access controls (MFA, least privilege) ✓ Backup and recovery capabilities ✓ Security monitoring (SIEM, IDS) ✓ Vulnerability management process ✓ Data deletion capabilities (right to erasure)
Testing and Validation
✓ Penetration testing annually ✓ Data breach response plan tested ✓ DSR process tested (can respond within 30 days) ✓ Staff trained on GDPR and security
Breach Notification
✓ Can detect breaches promptly ✓ Can notify DPA within 72 hours ✓ Can notify data subjects without undue delay ✓ Breach register maintained
Common DPA Findings
Critical (Likely to Result in Fine)
❌ No Article 30 ROPA ❌ Breach not notified to DPA within 72 hours ❌ No encryption of sensitive personal data ❌ Personal data transferred to non-EU without SCCs ❌ No Data Processing Agreements with processors ❌ Personal data retained beyond stated retention period
Moderate (Requires Remediation)
⚠️ ROPA incomplete or outdated ⚠️ DPIA not performed for high-risk processing ⚠️ DPAs with processors missing required clauses ⚠️ No penetration testing in last 12 months ⚠️ Staff not trained on GDPR ⚠️ DSR response time >30 days
Minor (Best Practice Recommendations)
⚠️ Privacy notices could be more detailed ⚠️ No automated data deletion procedures ⚠️ Backup retention longer than necessary ⚠️ TOMs documentation could be more comprehensive
Remediation Guidance
If No Article 30 ROPA
- Immediate (Weeks 1-2): Create ROPA template (use ICO or EDPB template)
- Weeks 3-6: Interview stakeholders to identify all processing
- Weeks 7-8: Document each processing activity in ROPA
- Week 9: Get DPO and senior management sign-off
- Ongoing: Update ROPA when processing changes
Timeline: 2-3 months Priority: 🔴 CRITICAL (foundational requirement)
If No DPAs with Processors
- Week 1: Inventory all processors (cloud providers, SaaS, third-party services)
- Week 2: Download standard DPA templates (AWS, Azure, GCP have pre-signed DPAs)
- Weeks 3-6: For custom processors, negotiate DPAs (use EDPB template)
- Week 7: Sign all DPAs
- Ongoing: Update DPAs when processors change or every 2 years
Timeline: 6-8 weeks Priority: 🔴 CRITICAL (Article 28 requirement)
If No Encryption
- Week 1: Identify all datastores containing personal data
- Week 2: Prioritize by sensitivity (start with special categories - health, biometric, etc.)
- Weeks 3-4: Enable encryption at rest (S3: SSE-S3 or SSE-KMS, RDS: enable storage encryption)
- Weeks 5-6: Enable encryption in transit (enforce HTTPS, TLS 1.2+)
- Ongoing: Monitor for unencrypted datastores
Timeline: 6-8 weeks Priority: 🔴 CRITICAL (Article 32(1)(a))
Cross-References
Related GDPR Articles
- Article 5 - Principles (lawfulness, fairness, transparency, purpose limitation, data minimization, accuracy, storage limitation, integrity and confidentiality, accountability)
- Article 6 - Lawfulness of processing
- Article 13-14 - Information to data subjects (privacy notices)
- Article 15-22 - Data subject rights
- Article 25 - Data protection by design and by default
- Article 28 - Processor obligations
- Article 30 - Records of processing activities (ROPA)
- Article 33-34 - Breach notification
- Article 35 - Data Protection Impact Assessment (DPIA)
Maps to Other Frameworks
- ISO 27001:2022: Annex A (all controls), especially A.5.34 (privacy), A.8 (technological controls)
- NIST 800-53: All families, especially SC (System and Communications Protection), AC (Access Control)
- SOC 2: CC6 (Logical and physical access), CC7 (System monitoring), P1-P8 (Privacy criteria)
- NIST Privacy Framework: All 5 functions (Identify, Govern, Control, Communicate, Protect)
Cost Estimates
GDPR Compliance Program (SMB with 50-200 employees)
- Article 30 ROPA development: 40 hours ($4,000)
- DPIA for high-risk processing: 40 hours per DPIA ($4,000 each)
- DPA negotiation and signing: 80 hours ($8,000)
- Privacy notice updates: 24 hours ($2,400)
- Policy and procedure documentation: 80 hours ($8,000)
- Technical measures (encryption, access control): 120 hours ($12,000)
- Penetration testing: $10k-$25k (annual)
- Staff training: 8 hours development + 2 hours per employee ($1,000 + $100/person)
- Total Year 1: ~$49k-$64k (one-time)
- Ongoing: ~$20k-$30k/year
DPO (Data Protection Officer)
- External DPO (retainer): $3k-$10k/month ($36k-$120k/year)
- Internal DPO (salary): $80k-$150k/year + benefits
Tools
- Privacy management platform (OneTrust, TrustArc): $25k-$100k/year
- Consent management platform: $5k-$20k/year
- DSAR automation: $10k-$30k/year
Evidence Package Structure
evidence/
└── gdpr-compliance/
├── article-30-ropa/
│ ├── ropa-master-2024.xlsx
│ ├── ropa-review-2024-Q1.pdf
│ └── ... (quarterly reviews)
├── article-32-security/
│ ├── 2024-01/
│ │ ├── s3-encryption-20240131.csv
│ │ ├── rds-encryption-20240131.json
│ │ ├── credential-report-20240131.csv
│ │ └── backup-jobs-202401.json
│ └── ... (monthly)
├── dpias/
│ ├── dpia-marketing-automation-2024.pdf
│ ├── dpia-customer-profiling-2024.pdf
│ └── dpia-biometric-access-2024.pdf
├── dpas/
│ ├── dpa-aws-signed.pdf
│ ├── dpa-azure-signed.pdf
│ ├── dpa-salesforce-signed.pdf
│ └── dpa-register-master.xlsx
├── breach-register/
│ ├── breach-register-master.xlsx
│ ├── breach-001-investigation-report.pdf
│ └── breach-001-dpa-notification.pdf
├── dsr-log/
│ ├── dsr-log-master.xlsx
│ ├── sar-001-response.pdf
│ └── ... (all DSR responses)
├── testing/
│ ├── pentest-2024-Q2-report.pdf
│ ├── pentest-2024-Q2-remediation-tracker.xlsx
│ └── vulnerability-scans/ (quarterly)
├── training/
│ ├── gdpr-training-materials-2024.pdf
│ ├── training-completion-records-2024.xlsx
│ └── attendance-registers/
└── README.md (evidence index, 3-year retention)
Automation Script
#!/usr/bin/env python3
"""
GDPR Article 32 Security of Processing Evidence Collection
Multi-cloud support (AWS, Azure, GCP)
"""
import boto3
import json
import csv
import os
from datetime import datetime
class GDPRSecurityEvidence:
def __init__(self, output_dir="evidence/gdpr-compliance/article-32-security"):
self.output_dir = f"{output_dir}/{datetime.now().strftime('%Y-%m')}"
self.timestamp = datetime.now().strftime("%Y%m%d")
os.makedirs(self.output_dir, exist_ok=True)
def check_s3_encryption(self):
"""Check S3 bucket encryption status"""
print("Checking S3 bucket encryption...")
s3 = boto3.client('s3')
buckets = s3.list_buckets()['Buckets']
results = []
for bucket in buckets:
bucket_name = bucket['Name']
try:
encryption = s3.get_bucket_encryption(Bucket=bucket_name)
results.append({
'bucket': bucket_name,
'encrypted': True,
'algorithm': encryption['ServerSideEncryptionConfiguration']['Rules'][0]['ApplyServerSideEncryptionByDefault']['SSEAlgorithm']
})
except s3.exceptions.ServerSideEncryptionConfigurationNotFoundError:
results.append({
'bucket': bucket_name,
'encrypted': False,
'algorithm': None
})
output_file = f"{self.output_dir}/s3-encryption-{self.timestamp}.json"
with open(output_file, 'w') as f:
json.dump(results, f, indent=2)
encrypted_count = len([r for r in results if r['encrypted']])
print(f"✓ S3 buckets: {encrypted_count}/{len(results)} encrypted")
if encrypted_count < len(results):
print(f"⚠️ WARNING: {len(results) - encrypted_count} buckets NOT encrypted (GDPR non-compliant)")
return results
def check_rds_encryption(self):
"""Check RDS database encryption"""
print("Checking RDS encryption...")
rds = boto3.client('rds')
instances = rds.describe_db_instances()['DBInstances']
results = []
for instance in instances:
results.append({
'instance': instance['DBInstanceIdentifier'],
'encrypted': instance.get('StorageEncrypted', False),
'kms_key': instance.get('KmsKeyId'),
'publicly_accessible': instance.get('PubliclyAccessible', True)
})
output_file = f"{self.output_dir}/rds-encryption-{self.timestamp}.json"
with open(output_file, 'w') as f:
json.dump(results, f, indent=2)
encrypted_count = len([r for r in results if r['encrypted']])
public_count = len([r for r in results if r['publicly_accessible']])
print(f"✓ RDS instances: {encrypted_count}/{len(results)} encrypted")
if public_count > 0:
print(f"⚠️ WARNING: {public_count} RDS instances are publicly accessible")
return results
def check_iam_mfa(self):
"""Check IAM users for MFA"""
print("Checking IAM MFA compliance...")
iam = boto3.client('iam')
# Generate credential report
iam.generate_credential_report()
report = iam.get_credential_report()
# Parse CSV
users_without_mfa = []
for line in csv.DictReader(report['Content'].decode('utf-8').splitlines()):
if line.get('password_enabled') == 'true' and line.get('mfa_active') == 'false':
users_without_mfa.append({
'user': line['user'],
'password_last_used': line.get('password_last_used'),
'mfa_active': False
})
output_file = f"{self.output_dir}/iam-no-mfa-{self.timestamp}.json"
with open(output_file, 'w') as f:
json.dump(users_without_mfa, f, indent=2)
total_users = len(list(csv.DictReader(report['Content'].decode('utf-8').splitlines())))
print(f"✓ IAM users: {total_users - len(users_without_mfa)}/{total_users} have MFA")
if len(users_without_mfa) > 0:
print(f"⚠️ WARNING: {len(users_without_mfa)} users without MFA (GDPR Article 32 non-compliant)")
return users_without_mfa
def check_backups(self):
"""Check backup configuration"""
print("Checking backup configuration...")
backup = boto3.client('backup')
# Get backup jobs from last 30 days
from datetime import datetime, timedelta
start_date = datetime.now() - timedelta(days=30)
backup_jobs = backup.list_backup_jobs(
ByCreatedAfter=start_date
)
output_file = f"{self.output_dir}/backup-jobs-{self.timestamp}.json"
with open(output_file, 'w') as f:
json.dump(backup_jobs, f, indent=2, default=str)
total_jobs = len(backup_jobs.get('BackupJobs', []))
completed = len([j for j in backup_jobs.get('BackupJobs', []) if j.get('State') == 'COMPLETED'])
print(f"✓ Backup jobs (30 days): {completed}/{total_jobs} successful")
return backup_jobs
def generate_compliance_report(self, s3_results, rds_results, mfa_results):
"""Generate GDPR Article 32 compliance summary"""
report = f"""
GDPR Article 32 - Security of Processing Evidence Report
Generated: {datetime.now().strftime("%Y-%m-%d %H:%M:%S")}
ENCRYPTION AT REST (Article 32(1)(a))
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
S3 Buckets: {len([r for r in s3_results if r['encrypted']])}/{len(s3_results)} encrypted
RDS Databases: {len([r for r in rds_results if r['encrypted']])}/{len(rds_results)} encrypted
ACCESS CONTROL (Article 32(1)(b))
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
IAM MFA: {len(mfa_results)} users WITHOUT MFA {'⚠️ NON-COMPLIANT' if len(mfa_results) > 0 else '✓ COMPLIANT'}
OVERALL COMPLIANCE STATUS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
{'✓ COMPLIANT' if len(mfa_results) == 0 and all(r['encrypted'] for r in s3_results) and all(r['encrypted'] for r in rds_results) else '✗ NON-COMPLIANT - Remediation Required'}
REQUIRED ACTIONS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
"""
if not all(r['encrypted'] for r in s3_results):
report += "□ Enable S3 encryption for all buckets containing personal data\n"
if not all(r['encrypted'] for r in rds_results):
report += "□ Enable RDS encryption for all databases containing personal data\n"
if len(mfa_results) > 0:
report += f"□ Enable MFA for {len(mfa_results)} IAM users\n"
if any(r.get('publicly_accessible') for r in rds_results):
report += "□ Review and restrict RDS public accessibility\n"
report += f"\nEvidence Location: {self.output_dir}/\n"
report += "Retention: 3 years (GDPR Article 5(2) accountability)\n"
report_file = f"{self.output_dir}/compliance-report-{self.timestamp}.txt"
with open(report_file, 'w') as f:
f.write(report)
print(f"\n{report}")
return report_file
if __name__ == "__main__":
print("GDPR Article 32 Security of Processing Evidence Collection")
print("=" * 70)
collector = GDPRSecurityEvidence()
s3_results = collector.check_s3_encryption()
rds_results = collector.check_rds_encryption()
mfa_results = collector.check_iam_mfa()
collector.check_backups()
collector.generate_compliance_report(s3_results, rds_results, mfa_results)
print("\n✓ GDPR evidence collection complete")
print("⚠️ REMINDER: Maintain evidence for 3 years per Article 5(2)")
GDPR Applicability: All organizations processing personal data of EU residents Enforcement: 27 EU Member State Data Protection Authorities Maximum Penalty: €20 million or 4% of worldwide annual revenue (Article 83) Evidence Retention: 3 years minimum (accountability principle) Priority: 🔴 CRITICAL (legal requirement for EU operations)
Data Subject Rights Check
Evaluates implementation of the 8 data subject rights under GDPR Articles 12-22.
Arguments
$1- Specific right to check (optional: access, rectification, erasure, restriction, portability, object, automated-decisions, all)$2- Check depth (optional: basic, comprehensive, audit-ready)
Overview of Data Subject Rights
GDPR grants individuals 8 fundamental rights over their personal data. Organizations must facilitate the exercise of these rights.
General Requirements (Article 12)
Response Timeframes
- 1 month to respond to requests (standard)
- +2 months extension if complex/numerous (inform data subject within 1 month)
- Without undue delay for rectification/erasure urgent cases
No Fee (Generally)
- Rights exercised free of charge
- Fee allowed if requests manifestly unfounded, excessive, or repetitive
- Reasonable fee for administrative costs
Transparent Communication
- Concise, transparent, intelligible language
- Plain language (no legalese)
- Written or electronic form (preference of data subject)
- Oral if requested (must verify identity)
Identity Verification
- Verify identity before responding (proportionate measures)
- Request additional information if reasonable doubts
- Balance verification with not collecting excessive data
Right to Complain
- Inform data subjects of right to lodge complaint with supervisory authority
- Provide supervisory authority contact details
1. Right to Be Informed
Implicit right exercised through privacy notices
Fair Processing Information (Articles 13-14)
At Collection (Article 13):
- Controller identity and contact
- DPO contact (if applicable)
- Purposes and lawful basis
- Legitimate interests (if applicable)
- Recipients or categories
- Third country transfers and safeguards
- Retention period
- Data subject rights (access, rectification, erasure, etc.)
- Right to withdraw consent (if applicable)
- Right to complain
- Statutory/contractual requirement
- Automated decision-making details
Not Obtained from Data Subject (Article 14):
- All Article 13 information, PLUS:
- Categories of personal data
- Source of data (including public sources)
Timing:
- At collection (Article 13): When data obtained
- Not from subject (Article 14): Within 1 month, or at first communication, or before disclosure
Implementation Check
- Privacy notices available and accessible?
- Content complete per Articles 13/14?
- Multi-layered approach (short + full notice)?
- Language clear and plain?
- Updated when processing changes?
2. Right of Access (Article 15)
Data subjects can request:
- Confirmation whether personal data processed
- Copy of personal data
- Supplementary information
Supplementary Information Required
- Purposes of processing
- Categories of data
- Recipients or categories
- Retention period (or criteria)
- Rights (rectification, erasure, restriction, object, complain)
- Source of data (if not from data subject)
- Automated decision-making details
- Safeguards for third country transfers
Copy of Data
- First copy: Free of charge
- Additional copies: Reasonable fee for administrative costs
- Format: Commonly used electronic format (if electronic request)
Implementation Check
- Process to search and compile personal data?
- All systems/databases covered?
- Automated retrieval where possible?
- Verification of identity?
- Response within 1 month?
- Copy provided in accessible format?
- Supplementary information included?
Common Challenges
- Data scattered across multiple systems
- Unstructured data (emails, documents)
- Third-party data (processor, joint controller)
- Impact on others' rights (redaction needed)
- Manifestly unfounded/excessive requests
3. Right to Rectification (Article 16)
Data subjects can request:
- Correction of inaccurate personal data
- Completion of incomplete personal data
Scope
- Factual inaccuracies (names, addresses, dates)
- Incomplete data relevant to purposes
- Takes into account purposes of processing
Notification Obligation
- Communicate rectification to recipients
- Unless impossible or disproportionate effort
- Inform data subject of recipients if requested
Implementation Check
- Simple process to submit corrections?
- Verification of corrections?
- Updates propagated to all systems?
- Notification to recipients/processors?
- Response within 1 month?
4. Right to Erasure / "Right to be Forgotten" (Article 17)
Data subjects can request deletion when:
Grounds for Erasure
- No longer necessary: Data not needed for original purpose
- Consent withdrawn: Lawful basis was consent, now withdrawn
- Objection: Data subject objects (no overriding legitimate grounds)
- Unlawful processing: Processing violates GDPR
- Legal obligation: Deletion required by EU/Member State law
- Children's data: Consent obtained when subject was child (Article 8)
Exceptions (Right Not Absolute)
- Freedom of expression/information
- Legal obligation (compliance with law)
- Public interest (public health, archiving, scientific/historical research)
- Legal claims (establishment, exercise, defense)
"Right to be Forgotten" (Public Data)
- If data made public, controller must inform other controllers
- Take reasonable steps (technical measures) to notify
- Consider technology and cost
Implementation Check
- Process to identify and delete data?
- Deletion from all systems (including backups)?
- Notification to processors and recipients?
- "Right to be forgotten" for published data?
- Response within 1 month?
- Assessment of grounds and exceptions?
Deletion Challenges
- Backups (delete on backup cycle, mark for deletion)
- Legal hold (litigation, regulatory obligation)
- Logs (anonymize where possible)
- Third parties (processors, recipients)
5. Right to Restriction of Processing (Article 18)
Data subjects can request restriction (not deletion) when:
Grounds for Restriction
- Accuracy disputed: During verification period
- Unlawful processing: Subject prefers restriction over erasure
- No longer needed: But subject needs for legal claims
- Objection pending: During assessment of controller's grounds
Restricted Processing Means
- Storage only (no further processing)
- Exceptions: Subject consent, legal claims, others' protection, public interest
Lifting Restriction
- Inform data subject before lifting restriction
- Only lift when grounds no longer apply
Implementation Check
- Ability to "flag" or mark restricted data?
- Prevents processing (except storage)?
- Notification to recipients?
- Inform subject before lifting?
- Response within 1 month?
6. Right to Data Portability (Article 20)
Data subjects can request:
- Receive personal data in structured, commonly used, machine-readable format
- Transmit data to another controller
Scope (Narrow Right)
Only applies when:
- Lawful basis: Consent OR contract
- Processing: Carried out by automated means
Does NOT apply to:
- Manual processing/paper records
- Processing on other lawful bases (legal obligation, legitimate interests, etc.)
"Structured, Commonly Used, Machine-Readable"
- JSON, CSV, XML formats
- Not PDF, printed documents
- Interoperable between systems
Direct Transmission
- Transmit directly to another controller "where technically feasible"
- Does not require interoperability between controllers
Rights of Others
- Must not adversely affect others' rights and freedoms
- May require redaction/exclusion
Implementation Check
- Automated export in machine-readable format?
- Common formats (JSON, CSV, XML)?
- Includes all data in scope (consent/contract + automated)?
- Ability to transmit to another controller?
- Response within 1 month?
7. Right to Object (Article 21)
Two Types of Objection
General Right to Object (Article 21(1))
Applies when lawful basis is:
- Legitimate interests (Article 6(1)(f))
- Public task (Article 6(1)(e))
Data subject must:
- Object on grounds relating to particular situation
Controller must:
- Stop processing UNLESS
- Demonstrate compelling legitimate grounds overriding data subject's interests/rights/freedoms, OR
- Processing for legal claims
Absolute Right to Object (Article 21(2-3))
Direct marketing:
- Right to object at any time
- No balancing test - must stop immediately
- Includes profiling for direct marketing
Scientific/historical research or statistics:
- Right to object on grounds of particular situation
- Unless necessary for public interest task
Opt-Out vs. Right to Object
- Direct marketing opt-out ≠ full right to object
- Separate processes may be needed
Implementation Check
- Clear information about right to object?
- Explicit mention in privacy notice?
- Easy method to object (one-click for direct marketing)?
- Processing stops upon objection?
- Balancing test for legitimate interests (if applicable)?
- Response within 1 month?
8. Rights Related to Automated Decision-Making (Article 22)
Scope
Automated decision-making that:
- Is based solely on automated processing (including profiling)
- Produces legal or similarly significant effects
Examples:
- Credit scoring (automatic loan denial)
- Algorithmic hiring (automatic rejection)
- Online behavioral advertising (if significant effect)
- Healthcare decision algorithms
General Prohibition
Data subject has right NOT to be subject to such decisions
Exceptions (When Allowed)
- Necessary for contract (entering or performing)
- Authorized by law (with safeguards for rights/freedoms/interests)
- Explicit consent (with safeguards)
Safeguards Required (Exceptions 1 & 3)
- Right to human intervention
- Right to express point of view
- Right to contest the decision
Special Category Data
- NOT allowed for automated decisions involving special categories
- Exception: Explicit consent OR substantial public interest + suitable safeguards
Implementation Check
- Identification of automated decision-making?
- Legal basis for automated decisions?
- Safeguards in place (human intervention, contest)?
- Information provided to data subjects?
- Meaningful information about logic?
- Significance and consequences explained?
Implementation Framework
Rights Management System
Essential Components:
- Request intake: Portal, email, phone, mail
- Identity verification: Proportionate measures
- Request routing: To responsible teams/systems
- Deadline tracking: 1-month (extendable to 3) SLAs
- Data retrieval: Across all systems and databases
- Response generation: Consistent templates
- Audit trail: Log all requests and responses
- Metrics and reporting: Volume, types, response times
Verification Procedures
Proportionate Measures:
- Match request to known data (email, account number)
- Request additional information if reasonable doubts
- Challenge: Don't collect excessive data for verification
Examples:
- Account holders: Login to portal
- Former customers: Match to order history, DOB
- Unknown subjects: Request identifying information
Fees and Refusals
Manifestly Unfounded or Excessive:
- Charge reasonable fee, OR
- Refuse to act
- Must demonstrate unfounded/excessive nature
- Inform data subject and complaint rights
Examples:
- Repetitive requests without change
- Clearly no data held
- Harassment or abuse
Communication Templates
Standard Responses Needed:
- Acknowledgment (especially if extension needed)
- Access request fulfillment
- Erasure confirmation
- Restriction confirmation
- Portability data package
- Objection acknowledgment
- Refusal (with reasons and complaint rights)
Staff Training
Key Personnel:
- Customer service (front-line request handlers)
- IT/Data teams (retrieval and deletion)
- Legal/Compliance (complex requests)
- DPO (oversight and advice)
Training Topics:
- Recognizing rights requests
- Verification procedures
- Deadlines and escalation
- Systems and data locations
- Templates and tools
Examples
# Check all data subject rights implementation
/gdpr:rights-check all comprehensive
# Verify right of access implementation
/gdpr:rights-check access
# Check erasure (right to be forgotten) procedures
/gdpr:rights-check erasure comprehensive
# Verify data portability capability
/gdpr:rights-check portability
# Basic check of rectification process
/gdpr:rights-check rectification basic
# Audit-ready assessment of all rights
/gdpr:rights-check all audit-ready
# Check automated decision-making safeguards
/gdpr:rights-check automated-decisions comprehensive
Common Implementation Gaps
- No centralized request process: Requests lost or delayed
- Inadequate identity verification: Over/under verification
- Data scattered: Can't locate all personal data
- No recipient tracking: Can't notify about erasure/rectification
- Backup challenges: Can't delete from backups
- Third-party systems: Processors not integrated
- No metrics: Can't track compliance or trends
- Insufficient training: Staff don't recognize requests
- Portability gaps: No machine-readable export
- Automated decisions unidentified: Don't know where they occur
Best Practices
- Proactive transparency: Explain rights in privacy notice
- Self-service portals: Enable data subjects to exercise rights online
- Automated workflows: Ticket systems, SLA tracking
- Data mapping prerequisite: Know where data is before requests arrive
- Regular testing: Simulate requests, measure response times
- DPO involvement: Review complex/novel requests
- Metrics and KPIs: Track volume, types, resolution times
- Continuous improvement: Learn from requests to improve practices
Sponsors
Details
- Marketplace
- GRCEngClub/claude-grc-engineering
- Source
- plugins/frameworks/gdpr
- Category
- Community
More from GRCEngClub/claude-grc-engineering
All 70- github-inspectorv0.1.0
- glbav0.1.0
- grc-auditorv0.1.0
- grc-diagramsv0.1.0
- grc-engineerv0.1.0
- grc-internalv0.1.0
- grc-loopv0.1.0
- grc-portfoliov0.1.0
- grc-reporterv0.1.0
- grc-tprmv0.1.0
- hitrustv0.1.0
- ind-dpdpav0.1.0
- irapv0.1.0
- ismapv0.1.0
- iso27001v0.1.0
- jp-appiv0.1.0
- nist-800-53v0.1.0
- nist-ai-600-1v0.1.0
- nist-ai-rmfv0.1.0
- nist-csf-20v0.1.0
- nydfsv0.1.0
- okta-inspectorv0.1.0
- onepassword-connectorv0.1.0
- oscalv0.1.0
