What it does. Implements GDPR (EU 2016/679) technical and organizational measures — privacy by design/default, DPIAs, data subject rights management, 72-hour breach notification, and cross-border transfer mechanisms (SCCs, BCRs, adequacy). Use when designing or auditing GDPR controls, building a DPIA, handling data subject access/erasure requests, or assessing cross-border data transfers. Part of mukul975/Anthropic-Cybersecurity-Skills (817 security skills) (mukul975/Anthropic-Cybersecurity-Skills).
Install
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-gdpr-data-protection-controls, or copy the skill folder into ~/.claude/skills/implementing-gdpr-data-protection-controls/.
- Raw file:
curl -sL https://raw.githubusercontent.com/mukul975/Anthropic-Cybersecurity-Skills/HEAD/skills/implementing-gdpr-data-protection-controls/SKILL.md
SKILL.md (verbatim)
name: implementing-gdpr-data-protection-controls
description: Implements GDPR (EU 2016/679) technical and organizational measures — privacy by design/default, DPIAs, data subject rights management, 72-hour breach notification, and cross-border transfer mechanisms (SCCs, BCRs, adequacy). Use when designing or auditing GDPR controls, building a DPIA, handling data subject access/erasure requests, or assessing cross-border data transfers.
domain: cybersecurity
subdomain: compliance-governance
tags:
- compliance
- governance
- gdpr
- privacy
- data-protection
- eu-regulation
nist_csf:
- GV.OC-02
- GV.PO-01
- PR.DS-01
- PR.AA-01
- ID.AM-02
version: '1.0'
author: mahipal
license: Apache-2.0
nist_ai_rmf:
- MEASURE-2.7
- MAP-5.1
- MANAGE-2.4
- MEASURE-2.8
- MEASURE-2.9
atlas_techniques:
- AML.T0070
- AML.T0066
- AML.T0082
mitre_attack:
- T1078
- T1530
- T1685.002
Implementing GDPR Data Protection Controls
Overview
The General Data Protection Regulation (EU) 2016/679 (GDPR) is the EU's comprehensive data protection law governing the collection, processing, storage, and transfer of personal data. This skill covers implementing the technical and organizational measures required by GDPR, including data protection by design and by default, Data Protection Impact Assessments (DPIAs), data subject rights management, breach notification procedures, and cross-border data transfer mechanisms.
When to Use
- When deploying or configuring implementing gdpr data protection controls capabilities in your environment
- When establishing security controls aligned to compliance requirements
- When building or improving security architecture for this domain
- When conducting security assessments that require this implementation
Prerequisites
- Understanding of EU data protection law and its territorial scope
- Knowledge of personal data processing activities within the organization
- Familiarity with data architecture, databases, and application systems
- Understanding of data flows including cross-border transfers
Core Concepts
Key GDPR Articles for Technical Controls
| Article |
Requirement |
| Art. 5 |
Principles: lawfulness, purpose limitation, data minimization, accuracy, storage limitation, integrity and confidentiality, accountability |
| Art. 6 |
Lawful basis for processing (consent, contract, legal obligation, vital interests, public task, legitimate interest) |
| Art. 25 |
Data protection by design and by default |
| Art. 28 |
Processor obligations and contractual requirements |
| Art. 30 |
Records of processing activities (ROPA) |
| Art. 32 |
Security of processing (technical and organizational measures) |
| Art. 33 |
Breach notification to supervisory authority (72 hours) |
| Art. 34 |
Communication of breach to data subjects |
| Art. 35 |
Data Protection Impact Assessment (DPIA) |
| Art. 37-39 |
Data Protection Officer (DPO) appointment and role |
| Art. 44-49 |
Cross-border data transfers (adequacy, SCCs, BCRs) |
Article 32 Security Measures
The regulation requires organizations to implement measures appropriate to the risk:
- Pseudonymization and encryption of personal data
- Confidentiality, integrity, availability, and resilience of processing systems
- Ability to restore availability and access to personal data in a timely manner
- Regular testing and evaluation of technical and organizational measures
Data Subject Rights (Articles 12-22)
| Right |
Article |
Description |
| Right to be informed |
13-14 |
Transparent information about processing |
| Right of access |
15 |
Obtain copy of personal data |
| Right to rectification |
16 |
Correct inaccurate data |
| Right to erasure |
17 |
"Right to be forgotten" |
| Right to restrict processing |
18 |
Limit processing of data |
| Right to data portability |
20 |
Receive data in machine-readable format |
| Right to object |
21 |
Object to processing (especially direct marketing) |
| Automated decision-making |
22 |
Not be subject to solely automated decisions |
Workflow
Phase 1: Data Mapping and Assessment (Weeks 1-6)
- Create comprehensive data inventory:
- What personal data is collected
- From whom (data subjects)
- Why (purposes and lawful bases)
- Where it's stored (systems, locations, countries)
- Who has access (internal and external)
- How long it's retained
- What security measures protect it
- Document Records of Processing Activities (ROPA) per Article 30
- Identify lawful basis for each processing activity
- Map cross-border data transfers and transfer mechanisms
- Identify processing activities requiring DPIA
Phase 2: Gap Analysis and Risk Assessment (Weeks 7-10)
- Assess current state against GDPR requirements
- Perform DPIAs for high-risk processing activities
- Identify security gaps in Article 32 compliance
- Evaluate data retention compliance
- Assess data subject rights request handling capabilities
Phase 3: Technical Controls Implementation (Weeks 11-24)
- Encryption:
- Data at rest: AES-256 for databases, file systems, backups
- Data in transit: TLS 1.2+ for all personal data transfers
- Key management: secure key storage and rotation procedures
- Pseudonymization:
- Implement tokenization for sensitive identifiers
- Separate pseudonymization keys from data stores
- Access Controls:
- Role-based access control (RBAC) for personal data
- Principle of least privilege
- MFA for systems processing personal data
- Regular access reviews
- Data Minimization:
- Implement data collection limits at application layer
- Default privacy settings (data protection by default)
- Automated data retention enforcement
- Erasure and Portability:
- Build data deletion workflows across all systems
- Implement data export in machine-readable formats (JSON, CSV)
- Cascade deletion to backups and archives
- Consent Management:
- Implement granular consent collection mechanisms
- Consent withdrawal functionality
- Consent audit trail and versioning
- Breach Detection:
- SIEM for personal data access monitoring
- Data loss prevention (DLP) controls
- Anomalous access detection
Phase 4: Organizational Controls (Weeks 11-24)
- Appoint Data Protection Officer (DPO) if required
- Develop data protection policies and procedures
- Create breach notification procedures (72-hour timeline)
- Establish data subject request (DSR) handling procedures
- Implement vendor management with Data Processing Agreements (DPAs)
- Deploy privacy awareness training for all staff
- Create data protection by design guidance for development teams
Phase 5: Documentation and Compliance Evidence (Weeks 25-30)
- Finalize ROPA documentation
- Document all DPIAs and outcomes
- Create data protection policies
- Document technical and organizational measures
- Establish privacy notice and consent records
- Create international transfer documentation (SCCs, TIAs)
Phase 6: Ongoing Compliance (Continuous)
- Regular DPIA reviews for new processing activities
- Annual data mapping refresh
- Periodic security measure testing (Art. 32 requirement)
- Data subject request tracking and SLA monitoring
- Breach response readiness testing
- Training refresh and awareness campaigns
Key Artifacts
- Records of Processing Activities (ROPA)
- Data Protection Impact Assessments (DPIAs)
- Data Processing Agreements (DPAs)
- Privacy Notices and Consent Records
- Breach Response Procedures and Register
- Data Subject Request Handling Procedures
- International Data Transfer Mechanisms (SCCs, BCRs)
- Technical and Organizational Measures Documentation
Common Pitfalls
- Treating GDPR as only a legal/compliance exercise without technical implementation
- Incomplete data mapping missing shadow IT or legacy systems
- Failing to maintain consent audit trails
- Not testing 72-hour breach notification capability
- Ignoring cross-border transfer requirements for cloud services
- Over-reliance on consent as lawful basis when legitimate interest applies
References
Other files in this skill
assets/template.md (verbatim)
GDPR Compliance Audit Checklist
| Field |
Value |
| Organization Name |
|
| Role |
Controller / Processor / Joint Controller |
| DPO Name and Contact |
|
| Lead Supervisory Authority |
|
| Assessment Date |
|
| Assessor |
|
Article 5: Data Processing Principles
Article 6: Lawful Basis
Articles 13-14: Transparency
Articles 15-22: Data Subject Rights
Article 25: Data Protection by Design and Default
Article 28: Processors
Article 30: Records of Processing Activities (ROPA)
Article 32: Security of Processing
Articles 33-34: Breach Notification
Article 35: Data Protection Impact Assessment
Articles 44-49: International Transfers
Articles 37-39: Data Protection Officer
Summary
| GDPR Area |
Items |
Compliant |
Non-Compliant |
N/A |
| Principles (Art. 5) |
|
|
|
|
| Lawful Basis (Art. 6) |
|
|
|
|
| Transparency (Art. 13-14) |
|
|
|
|
| Data Subject Rights (Art. 15-22) |
|
|
|
|
| Privacy by Design (Art. 25) |
|
|
|
|
| Processors (Art. 28) |
|
|
|
|
| ROPA (Art. 30) |
|
|
|
|
| Security (Art. 32) |
|
|
|
|
| Breach Notification (Art. 33-34) |
|
|
|
|
| DPIA (Art. 35) |
|
|
|
|
| International Transfers (Art. 44-49) |
|
|
|
|
| DPO (Art. 37-39) |
|
|
|
|
| Total |
|
|
|
|
Sign-off
| Role |
Name |
Signature |
Date |
| DPO |
|
|
|
| CISO |
|
|
|
| Legal Counsel |
|
|
|
| Senior Management |
|
|
|
references/api-reference.md (verbatim)
API Reference: Implementing GDPR Data Protection Controls
Key GDPR Articles
| Article |
Requirement |
Technical Control |
| Art 5 |
Processing principles |
Data minimization, retention policies |
| Art 25 |
Privacy by design |
Default privacy settings |
| Art 30 |
Records of processing |
ROPA documentation system |
| Art 32 |
Security of processing |
Encryption, access controls, testing |
| Art 33 |
Breach notification |
72-hour DPA notification |
| Art 35 |
DPIA |
Impact assessment for high-risk processing |
Data Subject Rights (Art 12-22)
| Right |
Article |
SLA |
| Access |
Art 15 |
1 month |
| Rectification |
Art 16 |
1 month |
| Erasure |
Art 17 |
1 month |
| Portability |
Art 20 |
1 month |
| Object |
Art 21 |
Without undue delay |
PII Detection Patterns
import re
patterns = {
"email": r"\b[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Z|a-z]{2,}\b",
"iban": r"\b[A-Z]{2}\d{2}[A-Z0-9]{11,30}\b",
"ip_address": r"\b\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}\b",
}
ROPA Required Fields (Art 30)
| Field |
Description |
| controller_name |
Data controller identity |
| purposes |
Processing purposes |
| data_categories |
Types of personal data |
| data_subjects |
Categories of data subjects |
| recipients |
Data recipients |
| transfers |
Cross-border transfers |
| retention_periods |
Data retention schedules |
| security_measures |
Art 32 controls |
Cross-Border Transfer Mechanisms (Art 44-49)
| Mechanism |
Use Case |
| Adequacy Decision |
Transfer to adequate countries (Art 45) |
| Standard Contractual Clauses (SCCs) |
Most common mechanism (Art 46) |
| Binding Corporate Rules (BCRs) |
Intra-group transfers (Art 47) |
| Derogations |
Consent, contract necessity (Art 49) |
References
references/standards.md (verbatim)
GDPR Standards Reference
Primary Legislation
Regulation (EU) 2016/679 - General Data Protection Regulation
- Adopted: April 14, 2016
- Effective: May 25, 2018
- Scope: Applies to any organization processing personal data of EU/EEA residents
- Chapters: 11 chapters, 99 articles, 173 recitals
- Enforcement: Supervisory authorities in each EU member state
- Penalties: Up to EUR 20 million or 4% of annual global turnover (whichever is greater)
Key Articles Reference
Chapter II - Principles (Articles 5-11)
- Art. 5: Core processing principles (lawfulness, fairness, transparency, purpose limitation, data minimization, accuracy, storage limitation, integrity and confidentiality, accountability)
- Art. 6: Six lawful bases for processing
- Art. 7: Conditions for consent
- Art. 8: Child's consent (minimum age varies by member state, 13-16)
- Art. 9: Special categories of data (health, biometric, genetic, racial/ethnic, political, religious, trade union, sexual orientation)
- Art. 10: Criminal conviction data
Chapter III - Rights of the Data Subject (Articles 12-23)
- Art. 12: Transparent communication (one month response deadline)
- Art. 13: Information for direct collection
- Art. 14: Information for indirect collection
- Art. 15: Right of access (copy of data, processing purposes, recipients, retention periods, safeguards for transfers)
- Art. 16: Right to rectification
- Art. 17: Right to erasure (applies when: consent withdrawn, purpose fulfilled, unlawful processing, legal obligation)
- Art. 18: Right to restriction of processing
- Art. 20: Right to data portability (structured, commonly used, machine-readable format)
- Art. 21: Right to object (especially direct marketing - absolute right)
- Art. 22: Automated individual decision-making including profiling
Chapter IV - Controller and Processor (Articles 24-43)
- Art. 24: Responsibility of the controller
- Art. 25: Data protection by design and by default
- Art. 26: Joint controllers
- Art. 28: Processor (DPA requirements: subject-matter, duration, nature/purpose, personal data types, data subject categories, controller obligations/rights)
- Art. 30: Records of processing activities
- Art. 32: Security of processing
- Art. 33: Notification to supervisory authority (72 hours)
- Art. 34: Communication to data subject (when high risk to rights and freedoms)
- Art. 35: Data Protection Impact Assessment (DPIA)
- Art. 36: Prior consultation with supervisory authority
- Art. 37-39: Data Protection Officer
Chapter V - International Transfers (Articles 44-49)
- Art. 45: Adequacy decision (EU Commission determines adequate countries)
- Art. 46: Appropriate safeguards (SCCs, BCRs, codes of conduct, certification)
- Art. 47: Binding Corporate Rules
- Art. 49: Derogations (explicit consent, contract, public interest)
Supporting Standards and Guidance
ISO/IEC 27701:2019
- Privacy Information Management System (PIMS) extension to ISO 27001
- Maps GDPR requirements to ISO management system controls
- Provides controller and processor-specific guidance
EDPB Guidelines
- Guidelines on Data Protection Impact Assessment (WP 248)
- Guidelines on Data Breach Notification (WP 250)
- Guidelines on Consent (updated 2020)
- Guidelines on International Data Transfers (post-Schrems II)
- Guidelines on Data Protection by Design and Default (04/2019)
Transfer Mechanisms Post-Schrems II
- Standard Contractual Clauses (SCCs): New modular SCCs adopted June 2021
- Module 1: Controller to Controller
- Module 2: Controller to Processor
- Module 3: Processor to Processor
- Module 4: Processor to Controller
- Transfer Impact Assessment (TIA): Required to supplement SCCs
- Supplementary Measures: Technical (encryption, pseudonymization), contractual, organizational
- EU-US Data Privacy Framework: Adequacy decision adopted July 2023
DPIA Criteria (Article 35(3) and EDPB)
DPIA required when processing involves:
- Systematic and extensive evaluation of personal aspects (profiling)
- Large-scale processing of special categories or criminal data
- Systematic monitoring of publicly accessible areas
- New technologies with potential high risk
- Large-scale data processing
- Matching or combining datasets
- Data concerning vulnerable subjects
- Innovative use of biometric data
- Data transfers outside EU without adequacy
- Processing that prevents data subjects from exercising rights
Supervisory Authorities
| Country |
Authority |
Website |
| EU-wide |
European Data Protection Board (EDPB) |
edpb.europa.eu |
| France |
CNIL |
cnil.fr |
| Germany |
BfDI (Federal), State DPAs |
bfdi.bund.de |
| Ireland |
DPC |
dataprotection.ie |
| Netherlands |
Autoriteit Persoonsgegevens |
autoriteitpersoonsgegevens.nl |
| Spain |
AEPD |
aepd.es |
| Italy |
Garante |
garanteprivacy.it |
| UK |
ICO (UK GDPR post-Brexit) |
ico.org.uk |
Key Enforcement Decisions (Benchmark)
- Meta (Ireland DPC, 2023): EUR 1.2 billion - Transfers to US without adequate safeguards
- Amazon (Luxembourg CNPD, 2021): EUR 746 million - Advertising targeting
- WhatsApp (Ireland DPC, 2021): EUR 225 million - Transparency failures
- Google (CNIL, 2022): EUR 150 million - Cookie consent
- H&M (Hamburg DPA, 2020): EUR 35.3 million - Employee surveillance
references/workflows.md (verbatim)
GDPR Data Protection Control Workflows
Workflow 1: Data Subject Request (DSR) Handling
Start
|
v
[Receive DSR from Data Subject]
- Via email, web form, phone, in-person
- Record receipt timestamp (30-day clock starts)
|
v
[Verify Identity of Requestor]
- Request additional identification if needed
- Clock pauses until identity verified
|
v
[Classify Request Type]
|
+--> Access Request (Art. 15) --> Locate all personal data
+--> Rectification (Art. 16) --> Identify incorrect data
+--> Erasure (Art. 17) --> Verify grounds for erasure
+--> Restriction (Art. 18) --> Flag data for restriction
+--> Portability (Art. 20) --> Export in machine-readable format
+--> Objection (Art. 21) --> Assess processing basis
|
v
[Check for Exemptions]
- Legal obligation to retain
- Freedom of expression
- Public health
- Archiving in public interest
- Legal claims
|
v
[Execute Request Across All Systems]
- Production databases
- Backups and archives
- Third-party processors
- Cloud services
- Analytics platforms
|
v
[Document Action Taken]
|
v
[Respond to Data Subject within 30 days]
- Extension to 60 additional days if complex (notify subject)
|
v
End
Workflow 2: Data Breach Notification (Art. 33-34)
Start
|
v
[Breach Detected or Reported]
- Technical detection (SIEM, DLP, IDS)
- Employee report
- External notification
- Third-party processor notification
|
v
[72-hour Clock Starts]
|
v
[Assess Breach Severity]
- Number of data subjects affected
- Types of personal data compromised
- Special categories involved?
- Risk to rights and freedoms
|
v
[Determine Notification Requirements]
|
+--> [Risk to Rights and Freedoms?]
|
+--> No Risk --> Document in breach register only
|
+--> Risk exists --> Notify Supervisory Authority (72 hours)
| |
| v
+--> High Risk --> Notify Supervisory Authority (72 hours)
AND notify affected data subjects
|
v
[Prepare Supervisory Authority Notification]
- Nature of the breach
- Categories and approximate number of data subjects
- Categories and approximate number of records
- Name and contact details of DPO
- Likely consequences of the breach
- Measures taken or proposed to address the breach
|
v
[Submit Notification to Lead Supervisory Authority]
|
v
[If High Risk: Notify Data Subjects]
- Clear and plain language
- Description of breach
- DPO contact information
- Likely consequences
- Measures taken to mitigate
|
v
[Conduct Post-Breach Review]
- Root cause analysis
- Control improvements
- Update breach register
|
v
End
Workflow 3: Data Protection Impact Assessment (DPIA)
Start
|
v
[Identify Processing Activity]
|
v
[Screen Against DPIA Criteria]
- Profiling or automated decision-making?
- Large-scale special category data?
- Systematic monitoring of public areas?
- New technology application?
- Cross-border data transfer?
- Vulnerable data subjects?
|
+--> [No DPIA triggers] --> Document screening decision --> End
|
+--> [DPIA required]
|
v
[Describe Processing Operation]
- Purpose and scope
- Data elements collected
- Data subjects categories
- Recipients and transfers
- Retention period
- Technology used
|
v
[Assess Necessity and Proportionality]
- Is processing necessary for the purpose?
- Could purpose be achieved with less data?
- Is lawful basis appropriate?
- Are data subject rights supported?
|
v
[Identify and Assess Risks]
- Risks to confidentiality
- Risks to integrity
- Risks to availability
- Risks to rights and freedoms
- Likelihood and severity of each risk
|
v
[Identify Mitigation Measures]
- Technical measures (encryption, pseudonymization, access controls)
- Organizational measures (policies, training, DPO oversight)
- Contractual measures (DPAs, SCCs)
|
v
[Determine Residual Risk]
|
+--> [Residual Risk Acceptable] --> Approve and proceed
|
+--> [Residual Risk High] --> Consult DPO
| |
| +--> [Can mitigate further] --> Add measures
| |
| +--> [Cannot mitigate] --> Prior consultation
| with Supervisory Authority (Art. 36)
|
v
[Document DPIA]
- Keep under review
- Reassess when processing changes
|
v
End
Workflow 4: International Data Transfer Assessment
Start
|
v
[Identify Cross-Border Transfer]
- Data flowing outside EEA
- Cloud services in non-EEA regions
- Group company data sharing
- Vendor/processor locations
|
v
[Check Adequacy Decision]
- Is destination country on EU adequacy list?
- (Andorra, Argentina, Canada, Faroe Islands, Guernsey,
Israel, Isle of Man, Japan, Jersey, New Zealand, Republic
of Korea, Switzerland, UK, Uruguay, US under DPF)
|
+--> [Adequate] --> Document and proceed
|
+--> [Not Adequate]
|
v
[Select Transfer Mechanism]
|
+--> Standard Contractual Clauses (SCCs)
+--> Binding Corporate Rules (BCRs)
+--> Approved Code of Conduct
+--> Certification Mechanism
+--> Derogations (Art. 49) - limited circumstances
|
v
[Conduct Transfer Impact Assessment (TIA)]
- Laws of destination country
- Government surveillance powers
- Data protection standards
- Access by public authorities
|
v
[Identify Supplementary Measures]
- Technical: encryption with EEA-held keys
- Contractual: additional processor obligations
- Organizational: policies limiting access
|
v
[Document Transfer Mechanism]
- Signed SCCs with correct module
- TIA findings and conclusions
- Supplementary measures implemented
|
v
End
Workflow 5: Records of Processing Activities (ROPA)
Start
|
v
[Identify All Processing Activities]
- Interview business units
- Review system inventory
- Analyze data flows
- Check vendor agreements
|
v
[For Each Processing Activity Document:]
|
v
[Controller Record (Art. 30(1))]
- Name and contact details of controller (and DPO)
- Purposes of processing
- Categories of data subjects
- Categories of personal data
- Categories of recipients
- Transfers to third countries (safeguards)
- Retention periods
- Technical and organizational security measures
|
v
[Processor Record (Art. 30(2))]
- Name and contact details of processor and controller
- Categories of processing carried out
- Transfers to third countries (safeguards)
- Technical and organizational security measures
|
v
[Maintain and Update ROPA]
- Review quarterly or when processing changes
- Update for new systems, vendors, purposes
- Make available to supervisory authority on request
|
v
End
Back to mukul975/Anthropic-Cybersecurity-Skills (817 security skills) or Agent skills.