mukul975/privacy-data-protection-skills

ropa-completeness-audit

- Audits Records of Processing Activities against supervisory authority templates from CNIL, ICO, and BfDI.

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/mukul975/privacy-data-protection-skills --skill ropa-completeness-audit

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

RoPA Completeness Audit

Overview

Supervisory authorities across the EEA publish RoPA templates and guidance that extend beyond the bare minimum Art. 30(1) requirements. While Art. 30(1) mandates seven fields, supervisory authorities such as CNIL, ICO, and BfDI expect additional information in practice. This skill provides a methodology for auditing RoPA entries against these expanded expectations, calculating completeness scores, identifying gaps, and tracking remediation to achieve supervisory authority readiness.

Supervisory Authority Template Comparison

CNIL (France) Template

The CNIL publishes the most structured RoPA template in the EU, available in both PDF and machine-readable (CSV/JSON) format. The CNIL template requires the Art. 30 mandatory fields plus additional recommended fields:

FieldArt. 30 MandatoryCNIL RequiredCNIL Recommended
Controller identity and contactYes (a)Yes—
Joint controller detailsYes (a)Yes—
DPO contactYes (a)Yes—
Processing activity name—Yes—
Purposes of processingYes (b)Yes—
Lawful basis (Art. 6)——Yes
Data subject categoriesYes (c)Yes—
Personal data categoriesYes (c)Yes—
Special category indication (Art. 9)——Yes
Recipient categoriesYes (d)Yes—
Processor details with DPA reference——Yes
International transfersYes (e)Yes—
Transfer safeguard mechanism—Yes—
Retention periodsYes (f)Yes—
Security measuresYes (g)Yes—
DPIA conducted (yes/no)——Yes
DPIA reference——Yes
Last review date——Yes

ICO (United Kingdom) Template

The ICO template aligns with UK GDPR Art. 30 and includes guidance notes for each field:

FieldArt. 30 MandatoryICO RequiredICO Recommended
Controller name and contactYes (a)Yes—
DPO contactYes (a)Yes—
Purposes of processingYes (b)Yes—
Lawful basis—Yes—
Legitimate interest description (if applicable)——Yes
Data subject categoriesYes (c)Yes—
Personal data categoriesYes (c)Yes—
Special category data and Art. 9 condition—Yes—
RecipientsYes (d)Yes—
International transfers with safeguardsYes (e)Yes—
Retention periodsYes (f)Yes—
Technical and organisational measuresYes (g)Yes—
Link to privacy notice——Yes
DPIA reference——Yes

BfDI (Germany) Template

The German Federal Commissioner for Data Protection (BfDI) publishes guidance (Hinweise zum Verzeichnis von Verarbeitungstaetigkeiten) with sector-specific requirements:

FieldArt. 30 MandatoryBfDI RequiredBfDI Recommended
Controller identity (Verantwortlicher)Yes (a)Yes—
DPO (Datenschutzbeauftragte/r)Yes (a)Yes—
Purpose (Zweck der Verarbeitung)Yes (b)Yes—
Lawful basis (Rechtsgrundlage)—Yes—
Data subject categories (Kategorien betroffener Personen)Yes (c)Yes—
Personal data categories (Kategorien personenbezogener Daten)Yes (c)Yes—
Recipients (Empfaenger)Yes (d)Yes—
Transfers to third countries (Uebermittlungen in Drittlaender)Yes (e)Yes—
Transfer safeguard with reference—Yes—
Retention periods (Loeschfristen)Yes (f)Yes—
Technical measures (Technische Massnahmen)Yes (g)Yes—
Organisational measures (Organisatorische Massnahmen)—Yes—
Responsible department (Verantwortliche Fachabteilung)——Yes
IT systems used——Yes

Completeness Scoring Methodology

Scoring Framework

Each RoPA entry is scored against a three-tier assessment:

  1. Tier 1 — Art. 30 Mandatory Compliance (40% weight): Are all seven Art. 30(1) mandatory fields populated?
  2. Tier 2 — Supervisory Authority Expectations (35% weight): Does the entry meet the selected SA's expanded requirements?
  3. Tier 3 — Quality Assessment (25% weight): Are populated fields specific, accurate, and current?

Tier 1: Mandatory Field Scoring

FieldPresent (1/0)Quality Score (0-3)
Art. 30(1)(a) Controller identity[1/0]0 = Missing, 1 = Partial, 2 = Complete, 3 = Excellent
Art. 30(1)(b) Purposes[1/0]0-3
Art. 30(1)(c) Data subject categories[1/0]0-3
Art. 30(1)(c) Personal data categories[1/0]0-3
Art. 30(1)(d) Recipients[1/0]0-3
Art. 30(1)(e) International transfers[1/0]0-3
Art. 30(1)(f) Retention periods[1/0]0-3
Art. 30(1)(g) Security measures[1/0]0-3

Quality scoring criteria:

  • 0 (Missing): Field is empty or contains only "N/A" where substantive content is expected.
  • 1 (Partial): Field contains some content but is materially incomplete (e.g., "employees" without further granularity for data subjects).
  • 2 (Complete): Field satisfies the legal requirement with specific, substantive content.
  • 3 (Excellent): Field exceeds minimum requirements with cross-references, supporting detail, and regulatory alignment.

Tier 2: SA-Specific Field Scoring

Score additional fields required or recommended by the target SA. Each SA template adds 3-6 fields beyond Art. 30 minimums.

Tier 3: Quality Metrics

MetricScoring
Purpose specificity0-3 (penalise vague terms per EDPB guidance)
Retention concreteness0-3 (penalise "as long as necessary" type terms)
Transfer mechanism documentation0-3 (must identify specific mechanism, not just "safeguards in place")
Review currency0-3 (reviewed within 12m = 3, 12-18m = 2, 18-24m = 1, >24m = 0)
DPA cross-reference0-3 (all processors have DPA refs = 3)

Overall Completeness Score Calculation

Tier 1 Score = (fields present / 8) * (avg quality / 3) * 100
Tier 2 Score = (SA fields present / SA total fields) * (avg quality / 3) * 100
Tier 3 Score = (sum of quality metrics / max possible) * 100

Overall = (Tier 1 * 0.40) + (Tier 2 * 0.35) + (Tier 3 * 0.25)

Readiness thresholds:

ScoreRatingInterpretation
95-100%ExcellentSupervisory authority ready — no immediate action
85-94%GoodMinor improvements recommended before SA interaction
70-84%AcceptableMaterial gaps exist — remediation plan required
50-69%PoorSignificant non-compliance risk — urgent remediation
Below 50%CriticalRoPA fundamentally deficient — rebuild required

Gap Identification Process

Step 1: Template Selection

Select the primary supervisory authority template based on:

  • The country where the controller is established (lead SA under one-stop-shop)
  • Any pending investigations or correspondence with a specific SA
  • Regulatory expectations in the primary market

Step 2: Field-by-Field Comparison

For each RoPA entry, compare every field against the selected SA template and classify:

ClassificationDefinitionRemediation Priority
CompliantField meets or exceeds SA expectationsNone
Gap — MissingRequired field is absentHigh
Gap — IncompleteField is present but does not meet SA expectationsMedium
Gap — StaleField content is outdatedMedium
Gap — VagueField content uses imprecise languageMedium
EnhancementSA-recommended field not presentLow

Step 3: Gap Register

Compile all identified gaps into a structured register:

Gap IDRecord IDProcessing ActivityFieldClassificationSA TemplateDescriptionSeverityRemediation OwnerTarget DateStatus
GAP-001RPA-023Customer analyticsArt. 30(1)(f)MissingCNILRetention period field is emptyCriticalStefan Richter[Date]Open
GAP-002RPA-034Website analyticsArt. 30(1)(b)VagueCNILPurpose too broad ("analytics")MajorJulia Richter[Date]Open

Remediation Tracking

Remediation Workflow

  1. Gap register creation: Compile all gaps from the audit into the register.
  2. Prioritisation: Sort by severity (Critical > Major > Minor > Enhancement).
  3. Owner assignment: Assign each gap to the processing owner responsible for the affected entry.
  4. Deadline setting: Critical = 30 days, Major = 60 days, Minor = 90 days, Enhancement = next annual review.
  5. Progress tracking: Weekly status updates on Critical items, bi-weekly on Major items.
  6. Verification: DPO verifies each remediated gap before closing.
  7. Re-scoring: After remediation cycle, re-calculate completeness scores.

Remediation Status Dashboard

SeverityTotalOpenIn ProgressRemediatedVerified
Critical30111
Major112432
Minor93231
Enhancement85120
Total3110894

Audit Frequency

Audit TypeFrequencyScope
Full completeness auditAnnuallyAll RoPA entries against selected SA template
Targeted audit (post-change)As neededEntries affected by organisational or regulatory change
Pre-investigation readiness checkOn demandFull RoPA in preparation for SA investigation or inquiry
Automated completeness scanMonthlyAll entries — field presence and vague term detection only

Verwandte Aufgaben

aus demselben Repository

Weitere Skills

Alle Skills
mukul975
Community

applying-privacy-design-patterns

- Systematic application of the eight privacy design patterns per Hoepman: minimize, hide, separate, abstract, inform, control, enforce, and demonstrate. Covers pattern selection methodology per processing activity, mapping to GDPR principles, and practical implementation guidance for privacy-by-design system architecture.

Installationen
1
GitHub Stars
315
Aktualisiert
16. März
mukul975
Community

brazil-lgpd

- Guides compliance with Brazil's Lei Geral de Proteção de Dados (LGPD, Lei 13.709/2018). Covers the 10 lawful bases under Art. 7, DPO appointment, ANPD enforcement, data subject rights under Arts. 17-22, and international transfer mechanisms. Keywords: LGPD, Brazil data protection, ANPD, lawful bases, data subject rights, international transfers.

Installationen
1
GitHub Stars
315
Aktualisiert
16. März
mukul975
Community

adequacy-assessment

- Guides assessment of third-country adequacy decisions under GDPR Article 45 for international data transfers. Covers the current EC adequacy decisions list, adequacy assessment criteria, partial adequacy handling, and monitoring of adequacy decision reviews. Keywords: adequacy decision, Article 45, third country, adequate protection, EC adequacy list.

Installationen
1
GitHub Stars
295
Aktualisiert
16. März
mukul975
Community

age-gating-services

- Implements age-gating mechanisms for online services to restrict access based on user age. Covers hard gates versus soft gates, neutral age prompts, re-verification triggers, circumvention prevention, and regulatory requirements under GDPR, COPPA, UK Online Safety Act, and DSA. Keywords: age gate, age restriction, neutral prompt, children, online services, access control.

Installationen
1
GitHub Stars
295
Aktualisiert
16. März