Back to catalog
Static reviewDevelopment

Skill dossier

implementing-gdpr-data-protection-controls

Source declaration

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.

The author's original description, preserved in English. It describes intent, not verified performance.

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.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

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. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/implementing-gdpr-data-protection-controls/SKILL.md:L93]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/implementing-gdpr-data-protection-controls/SKILL.md:L1-L36]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
70.6 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/implementing-gdpr-data-protection-controls/assets/template.mdReference6.1 KB
skills/implementing-gdpr-data-protection-controls/LICENSEOther11 KB
skills/implementing-gdpr-data-protection-controls/references/api-reference.mdReference2.1 KB
skills/implementing-gdpr-data-protection-controls/references/standards.mdReference5.4 KB
skills/implementing-gdpr-data-protection-controls/references/workflows.mdReference7 KB
skills/implementing-gdpr-data-protection-controls/scripts/agent.pyScript9.1 KB
skills/implementing-gdpr-data-protection-controls/scripts/process.pyScript21.6 KB
skills/implementing-gdpr-data-protection-controls/SKILL.mdInstruction8.3 KB

SKILL.md frontmatter

{
  "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"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    Core Concepts

    Source-described action candidate under “Core Concepts”; not verified execution.

  4. 04
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  5. 05
    Action

    Create comprehensive data inventory:

    Source-described action candidate under “Phase 1: Data Mapping and Assessment (Weeks 1-6)”; not verified execution.

  6. 06
    Action

    Document Records of Processing Activities (ROPA) per Article 30

    Source-described action candidate under “Phase 1: Data Mapping and Assessment (Weeks 1-6)”; not verified execution.

Inspect all extracted workflow candidates (43 candidate steps)
  1. 07
    Action

    Identify lawful basis for each processing activity

    Source-described action candidate under “Phase 1: Data Mapping and Assessment (Weeks 1-6)”; not verified execution.

  2. 08
    Action

    Map cross-border data transfers and transfer mechanisms

    Source-described action candidate under “Phase 1: Data Mapping and Assessment (Weeks 1-6)”; not verified execution.

  3. 09
    Action

    Identify processing activities requiring DPIA

    Source-described action candidate under “Phase 1: Data Mapping and Assessment (Weeks 1-6)”; not verified execution.

  4. 10
    Action

    Assess current state against GDPR requirements

    Source-described action candidate under “Phase 2: Gap Analysis and Risk Assessment (Weeks 7-10)”; not verified execution.

  5. 11
    Action

    Perform DPIAs for high-risk processing activities

    Source-described action candidate under “Phase 2: Gap Analysis and Risk Assessment (Weeks 7-10)”; not verified execution.

  6. 12
    Action

    Identify security gaps in Article 32 compliance

    Source-described action candidate under “Phase 2: Gap Analysis and Risk Assessment (Weeks 7-10)”; not verified execution.

  7. 13
    Action

    Evaluate data retention compliance

    Source-described action candidate under “Phase 2: Gap Analysis and Risk Assessment (Weeks 7-10)”; not verified execution.

  8. 14
    Action

    Assess data subject rights request handling capabilities

    Source-described action candidate under “Phase 2: Gap Analysis and Risk Assessment (Weeks 7-10)”; not verified execution.

  9. 15
    Action

    Encryption:

    Source-described action candidate under “Phase 3: Technical Controls Implementation (Weeks 11-24)”; not verified execution.

  10. 16
    Action

    Pseudonymization:

    Source-described action candidate under “Phase 3: Technical Controls Implementation (Weeks 11-24)”; not verified execution.

  11. 17
    Action

    Access Controls:

    Source-described action candidate under “Phase 3: Technical Controls Implementation (Weeks 11-24)”; not verified execution.

  12. 18
    Action

    Data Minimization:

    Source-described action candidate under “Phase 3: Technical Controls Implementation (Weeks 11-24)”; not verified execution.

  13. 19
    Action

    Erasure and Portability:

    Source-described action candidate under “Phase 3: Technical Controls Implementation (Weeks 11-24)”; not verified execution.

  14. 20
    Action

    Consent Management:

    Source-described action candidate under “Phase 3: Technical Controls Implementation (Weeks 11-24)”; not verified execution.

  15. 21
    Action

    Breach Detection:

    Source-described action candidate under “Phase 3: Technical Controls Implementation (Weeks 11-24)”; not verified execution.

  16. 22
    Decision

    Appoint Data Protection Officer (DPO) if required

    Source-described decision candidate under “Phase 4: Organizational Controls (Weeks 11-24)”; not verified execution.

  17. 23
    Action

    Develop data protection policies and procedures

    Source-described action candidate under “Phase 4: Organizational Controls (Weeks 11-24)”; not verified execution.

  18. 24
    Action

    Create breach notification procedures (72-hour timeline)

    Source-described action candidate under “Phase 4: Organizational Controls (Weeks 11-24)”; not verified execution.

  19. 25
    Action

    Establish data subject request (DSR) handling procedures

    Source-described action candidate under “Phase 4: Organizational Controls (Weeks 11-24)”; not verified execution.

  20. 26
    Action

    Implement vendor management with Data Processing Agreements (DPAs)

    Source-described action candidate under “Phase 4: Organizational Controls (Weeks 11-24)”; not verified execution.

  21. 27
    Action

    Deploy privacy awareness training for all staff

    Source-described action candidate under “Phase 4: Organizational Controls (Weeks 11-24)”; not verified execution.

  22. 28
    Action

    Create data protection by design guidance for development teams

    Source-described action candidate under “Phase 4: Organizational Controls (Weeks 11-24)”; not verified execution.

  23. 29
    Action

    Finalize ROPA documentation

    Source-described action candidate under “Phase 5: Documentation and Compliance Evidence (Weeks 25-30)”; not verified execution.

  24. 30
    Action

    Document all DPIAs and outcomes

    Source-described action candidate under “Phase 5: Documentation and Compliance Evidence (Weeks 25-30)”; not verified execution.

  25. 31
    Action

    Create data protection policies

    Source-described action candidate under “Phase 5: Documentation and Compliance Evidence (Weeks 25-30)”; not verified execution.

  26. 32
    Action

    Document technical and organizational measures

    Source-described action candidate under “Phase 5: Documentation and Compliance Evidence (Weeks 25-30)”; not verified execution.

  27. 33
    Action

    Establish privacy notice and consent records

    Source-described action candidate under “Phase 5: Documentation and Compliance Evidence (Weeks 25-30)”; not verified execution.

  28. 34
    Action

    Create international transfer documentation (SCCs, TIAs)

    Source-described action candidate under “Phase 5: Documentation and Compliance Evidence (Weeks 25-30)”; not verified execution.

  29. 35
    Action

    Regular DPIA reviews for new processing activities

    Source-described action candidate under “Phase 6: Ongoing Compliance (Continuous)”; not verified execution.

  30. 36
    Action

    Annual data mapping refresh

    Source-described action candidate under “Phase 6: Ongoing Compliance (Continuous)”; not verified execution.

  31. 37
    Action

    Periodic security measure testing (Art. 32 requirement)

    Source-described action candidate under “Phase 6: Ongoing Compliance (Continuous)”; not verified execution.

  32. 38
    Action

    Data subject request tracking and SLA monitoring

    Source-described action candidate under “Phase 6: Ongoing Compliance (Continuous)”; not verified execution.

  33. 39
    Action

    Breach response readiness testing

    Source-described action candidate under “Phase 6: Ongoing Compliance (Continuous)”; not verified execution.

  34. 40
    Action

    Training refresh and awareness campaigns

    Source-described action candidate under “Phase 6: Ongoing Compliance (Continuous)”; not verified execution.

  35. 41
    Action

    Key Artifacts

    Source-described action candidate under “Key Artifacts”; not verified execution.

  36. 42
    Action

    Common Pitfalls

    Source-described action candidate under “Common Pitfalls”; not verified execution.

  37. 43
    Action

    References

    Source-described action candidate under “References”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

47 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

7 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 7 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

40 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 40 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/implementing-gdpr-data-protection-controls/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/implementing-gdpr-data-protection-controls/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/implementing-gdpr-data-protection-controls
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.