mukul975/privacy-data-protection-skills

dpia-risk-scoring

- Provides a structured risk scoring methodology for Data Protection Impact Assessments aligned with ENISA threat taxonomy and ISO 29134.

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/mukul975/privacy-data-protection-skills --skill dpia-risk-scoring

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

DPIA Risk Scoring Methodology

Overview

Art. 35(7)(c) GDPR requires a DPIA to include "an assessment of the risks to the rights and freedoms of data subjects." This skill provides a quantifiable risk scoring framework that converts qualitative privacy risks into comparable, prioritised scores supporting mitigation decisions.

Risk Scoring Framework

Severity Scale (Impact on Data Subject Rights)

LevelScoreDescriptionExamples
Negligible1Minor inconvenience, easily recoverableTemporary inability to access non-essential service
Limited2Significant inconvenience, recoverable with effortTargeted advertising based on inferred preferences
Significant3Serious consequences, difficult to recover fromFinancial loss, discrimination, reputational harm
Maximum4Irreversible or very difficult to recover fromIdentity theft, physical safety risk, loss of employment

Likelihood Scale

LevelScoreDescriptionIndicators
Negligible1Unlikely given current controlsStrong technical controls, limited access, encrypted at rest and in transit
Limited2Possible but requires specific conditionsSome access controls, partial encryption, known but unproven attack vectors
Significant3Probable given known threat landscapeWeak controls in specific areas, prior incidents in sector, active threat actors
Maximum4Near-certain or already occurringNo controls, known vulnerabilities, prior breach of similar system

Risk Matrix

Severity →    Negligible(1)  Limited(2)  Significant(3)  Maximum(4)
Likelihood ↓
Maximum(4)        4(M)         8(H)        12(VH)         16(VH)
Significant(3)    3(L)         6(M)         9(H)          12(VH)
Limited(2)        2(L)         4(M)         6(M)           8(H)
Negligible(1)     1(L)         2(L)         3(L)           4(M)

Risk Levels: L=Low(1-3), M=Medium(4-6), H=High(7-9), VH=Very High(10-16)

Risk Categories (ENISA-Aligned)

Rights and Freedoms Impacts

  1. Loss of confidentiality -- Unauthorised disclosure of personal data
  2. Loss of integrity -- Unauthorised modification of personal data
  3. Loss of availability -- Inability to access or use personal data
  4. Loss of purpose limitation -- Data used beyond original purpose
  5. Discrimination -- Unfair treatment based on processing outcomes
  6. Identity theft/fraud -- Misuse of personal data for impersonation
  7. Financial loss -- Direct or indirect monetary harm
  8. Reputational damage -- Social standing or professional harm
  9. Physical harm -- Safety or health impacts
  10. Loss of autonomy -- Chilling effects on behaviour or free expression

Inherent vs Residual Risk

  • Inherent risk: Risk level before applying any mitigation measures
  • Residual risk: Risk level after applying planned mitigation measures
  • Risk reduction: Difference between inherent and residual risk scores
  • Acceptable risk threshold: Organisation-defined tolerance level

Art. 36 Prior Consultation Trigger

When residual risk remains High or Very High after all feasible mitigation measures, the controller must consult the supervisory authority under Art. 36(1) before commencing processing.

Relacionados por tarefa

do mesmo repositório

Mais Skills

Todos os Skills
mukul975
Comunidade

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.

instalações
1
GitHub Stars
315
Atualizado
16 de mar.
mukul975
Comunidade

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.

instalações
1
GitHub Stars
315
Atualizado
16 de mar.
mukul975
Comunidade

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.

instalações
1
GitHub Stars
295
Atualizado
16 de mar.
mukul975
Comunidade

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.

instalações
1
GitHub Stars
295
Atualizado
16 de mar.