How this command is triggered — by the user, by Claude, or both
Slash command
/gdpr:assessThe summary Claude sees in its command listing — used to decide when to auto-load this command
# 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 ...
Evaluates organizational readiness for General Data Protection Regulation (GDPR) compliance.
$1 - Assessment scope (optional: full, data-mapping, rights-management, security-measures)$2 - Organization type (optional: controller, processor, joint-controller)Territorial Scope:
Data Subject Rights Territory:
| 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 |
Organizations must identify one lawful basis for each processing activity:
Special Category Data (Article 9) requires additional lawful basis beyond Article 6.
Required for organizations with:
Required when processing likely to result in high risk:
Required for:
DPO Requirements:
Transfer Mechanisms:
Special Considerations:
72-Hour Rule (Article 33):
Data Subject Notification (Article 34):
Lead Supervisory Authority:
Examples:
Administrative Fines (Article 83):
Factors Considered:
# 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
Typical GDPR Compliance Journey:
/assessCompares a local repository against a topic wiki's research body and the broader market, producing a gap analysis with opportunities and competitive landscape.
/assessAssesses DORA compliance readiness for EU financial entities and ICT providers. Requires scope (full, pillar-specific, entity-type); optional entity classification.
/assessAssesses GLBA compliance readiness for specified scope (full, safeguards, privacy, pretexting) and institution type, producing compliance score and detailed evaluation.
/assessAssesses compliance with NIST 800-53 controls for a specified control family (e.g., AC) or baseline (low, moderate, high), with optional revision (r4 or r5).
/assessAssesses SOC 2 Type I or II audit readiness for specified scope (security, availability, confidentiality, processing integrity, privacy), producing readiness scores, control gaps, evidence requirements, remediation recommendations, and timeline.
/assessAssesses ISMS compliance against ISO 27001:2022 clauses and Annex A controls, producing status reports, gap analysis, Statement of Applicability guidance, and certification readiness.
npx claudepluginhub fianulabs/claude-grc-engineering --plugin gdpr