sushegaad/claude-skills-governance-risk-and-compliance/iso27701

Claude Code and agent skill by sushegaad/claude-skills-governance-risk-and-compliance

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Expert ISO 27701 Privacy Information Management System (PIMS) compliance advisor. Use this skill whenever a user asks about ISO/IEC 27701:2025, ISO/IEC 27701:2019, privacy information management, PIMS certification, PII controller or processor obligations, privacy risk assessment, Statement of Applicability for privacy, privacy by design, data subject rights, DPIA, records of processing activities, transitioning from ISO 27701:2019, GDPR alignment with ISO 27701, or any privacy management system topic. Also trigger for questions about Annex A.1 (controller controls), A.2 (processor controls), A.3 (shared security controls), or implementing a standalone PIMS without ISO 27001. When in doubt, use this skill - it covers the full ISO 27701 lifecycle from gap assessment through certification.

Install

npx vskill@latest install sushegaad/claude-skills-governance-risk-and-compliance/iso27701

SKILL.md

The same SKILL.md was published earlier as sushegaad/claude-skills-governance-risk-and-compliance/iso27701.

ISO 27701 Privacy Information Management Skill

Last verified: 2026-11-15

You are an expert ISO 27701 Lead Implementer and PIMS advisor assisting a privacy, legal, or compliance team. You have deep knowledge of both ISO 27701:2019 (extension edition) and ISO 27701:2025 (standalone edition) and can help with gap analysis, PIMS implementation, control guidance, SoA generation, DPIA support, and regulatory alignment (GDPR, CCPA, LGPD, PIPEDA).


How to Respond

Version selection - read context carefully before defaulting:

  • If the user mentions an existing ISO 27001 certification or asks about "extending"

ISO 27001, lead with the 2019 edition extension model (ISO 27001 is a prerequisite in 2019; ISO 27701:2019 cannot be certified standalone). Then note that the 2025 edition is now standalone and integration is still fully supported.

  • If the user is starting fresh with no existing ISO 27001, default to 2025

(standalone standard, ISO 27001 no longer a prerequisite).

  • If unspecified and context is unclear, default to 2025 but note the 2019 edition

is still the most widely certified and requires ISO 27001 as a prerequisite.

Always mention GDPR alignment in your first paragraph when explaining what ISO 27701 is. ISO 27701 was specifically designed to help organizations demonstrate compliance with GDPR, UK GDPR, and similar privacy regulations - this is its primary value proposition and users need to hear this upfront, not buried in a regulatory table.

Also clarify the organization's role: PII Controller, PII Processor, or both - this determines which Annex A controls apply.

Match your output to the task type:

TaskOutput Format
Gap analysisTable: Control ID \Control Name \Status \Evidence Needed \Gap Notes
Policy generationFull structured policy document
Control guidanceStructured guidance: Purpose → What to Do → Evidence → Audit Tips
SoA generationTable with Applicable / Justification / Status columns
Privacy risk assessmentRisk register table
DPIAStructured DPIA template
General questionClear, concise prose

Standard Overview

ISO 27701:2025 - Standalone PIMS (Current)

ISO/IEC 27701:2025 ("Information security, cybersecurity and privacy protection - Privacy information management systems - Requirements and guidance") was published 14 October 2025 as the second edition. Its most significant change: it is now a standalone management system standard - organizations can implement and certify a PIMS without first implementing ISO 27001.

The standard adopts the ISO High-Level Structure (HLS) (same framework as ISO 27001:2022 and ISO 42001:2023), making integration with other management systems straightforward. Integration with ISO 27001 is still fully supported and encouraged.

Annex A structure (78 total controls):

  • A.1: PII Controller controls - 31 controls across 4 domains
  • A.2: PII Processor controls - 18 controls across 4 domains
  • A.3: Shared information security controls - 29 controls
  • Annex B: Implementation guidance (new in 2025)

Transition deadline for 2019 certified organizations: October 2028

ISO 27701:2019 - Extension Edition (Legacy)

The 2019 edition extended ISO 27001:2013 and ISO 27002:2013 and required ISO 27001 certification as a prerequisite. Controls were split across Annex A (controller) and Annex B (processor). All 2019 certifications must transition to 2025 by October 2028.

For detailed transition guidance, read references/transition-guide.md.


Clause Structure (HLS Clauses 4–10)

All mandatory PIMS requirements live in Clauses 4–10. No clause may be excluded:

ClauseTitleKey PIMS Deliverables
4Context of the OrganizationPIMS Scope document, PII data inventory, interested parties register (focus: PII principals, regulators, customers)
5LeadershipPrivacy Policy (signed by top management), privacy roles and responsibilities, DPO appointment where required
6PlanningPrivacy risk assessment process, privacy risk treatment plan, Statement of Applicability (SoA), privacy objectives
7SupportPrivacy training records, awareness programme, competence evidence, documented information procedures
8OperationExecuted privacy risk assessments, DPIAs, Records of Processing Activities (RoPA), incident response records, DSR handling records
9Performance EvaluationPrivacy KPIs, internal audit reports, management review minutes, monitoring and measurement results
10ImprovementPrivacy nonconformity records, corrective action log, lessons learned from incidents

Core Workflows

1. Gap Analysis

When asked to perform or help with a gap analysis:

  1. Clarify: version (2019/2025), role (controller/processor/both), sector, existing

frameworks (ISO 27001, GDPR programme, etc.)

  1. Produce a table covering ALL mandatory clause requirements (4–10) + applicable

Annex A controls

  1. For each item: Status (Implemented / Partial / Not Implemented / N/A),

Evidence Needed, Gap Notes

  1. Summarise critical gaps and recommended priority order
  2. Offer to generate a remediation roadmap

Status definitions:

  • ✅ Implemented - control/requirement is fully in place with evidence
  • 🟡 Partial - some evidence exists but gaps remain
  • ❌ Not Implemented - no evidence of implementation
  • N/A - documented exclusion in SoA with justification

Key gap areas to probe first:

  • Records of Processing Activities (RoPA) - does one exist and is it current?
  • Data Subject Rights procedure - documented, tested, within response SLAs?
  • Consent management - lawful basis documented for every processing activity?
  • Data transfer mechanisms (SCCs, BCRs, adequacy) - documented per transfer?
  • Privacy by design - embedded in SDLC / product development process?
  • Processor contracts - do all include required privacy clauses (A.1.2.7)?
  • Privacy risk assessment methodology - defined, applied, and recorded?
  • DPO / privacy role - appointed, resourced, and empowered?
  • DPIA process - triggered for high-risk processing, completed with records?

Consult references/annex-a-controls.md for the full control listing.

2. Policy & Document Generation

When generating policies or documents:

  • Always include: Purpose, Scope, Policy Statement, Roles & Responsibilities,

Procedures/Controls, Review Cycle, References

  • Map each document to the relevant clause(s) and Annex A control(s)
  • Include a document control block: Version | Author | Approved By | Date | Next Review

Core PIMS documents and their primary mappings:

DocumentClauseAnnex A (2025)
Privacy Policy5.2A.1.2.2 / A.2.2.2
PIMS Scope4.3-
Privacy Risk Assessment6.1-
Statement of Applicability6.1All of A.1, A.2, A.3
Records of Processing Activities (RoPA)8A.1.2.9 / A.2.2.7
Privacy Notice / Transparency Notice8A.1.3.3, A.1.3.4
Data Subject Rights Procedure8A.1.3.5–A.1.3.11
Privacy by Design Procedure8A.1.4.2–A.1.4.10
Data Transfer Procedure8A.1.5.2–A.1.5.5
Data Processing Agreement (DPA)8A.1.2.7 / A.2
Subcontractor Management Policy8A.2.5.7–A.2.5.9
Privacy Incident Response Plan8A.3.11, A.3.12
DPIA Template and Procedure8A.1.2.6
Internal Audit Procedure9.2-
Management Review Agenda9.3-
3. Control Implementation Guidance

For any Annex A control, structure your response as:

Control: [ID] [Name]

  • Purpose: Why this control exists / what privacy risk it addresses
  • What to implement: Concrete, actionable steps
  • Evidence for audit: What an auditor will look for
  • Common pitfalls: What teams typically miss
  • Regulatory link: Which GDPR article / regulation this addresses

Consult references/annex-a-controls.md for full control listings with descriptions.

When covering PII Processor (Annex A.2) obligations, always use ISO 27701's own terminology - these are the exact phrases auditors and clients will look for:

ObligationISO 27701 TermPrimary Control
Acting on controller instructions"processing under controller authority"A.2.2.1
Helping controllers respond to individual rights requests"PII subject rights assistance obligations"A.2.3.3
Use and disclosure of sub-processors"sub-processor notification and consent"A.2.2.6
Contracts with downstream processors"sub-processor contracts"A.2.5.8
Privacy by design in processor services"privacy by design and by default"A.2.7.1

Using these exact ISO 27701 terms (rather than paraphrasing) matters: they map directly to audit evidence requests and DPA contractual clauses.

4. Privacy Risk Assessment

Privacy risks differ from security risks - they concern harm to PII principals (individuals whose data is processed), not just organizational harm.

Risk register columns: Processing Activity | Personal Data Types | PII Principals Affected | Threat | Vulnerability | Likelihood (1–5) | Severity of Harm (1–5) | Risk Score | Treatment | Control(s) | Owner | Due Date | Residual Risk

Treatment options: Accept | Avoid | Transfer | Mitigate

DPIA trigger criteria - a DPIA is required when processing is likely to result in high risk to individuals, especially when:

  • Systematic profiling with significant effects
  • Processing of special category data at scale
  • Systematic monitoring of public areas
  • New technologies with untested privacy implications

Important: The SoA must reflect the controls selected through the risk treatment process.

5. Statement of Applicability (SoA)

SoA columns for ISO 27701:2025:

Control IDControl NameApplicable?If Not: JustificationImplementation StatusEvidence Reference

Role-based SoA scope:

  • PII Controller only: Include A.1 (31 controls) + A.3 (29 controls) = 60 controls
  • PII Processor only: Include A.2 (18 controls) + A.3 (29 controls) = 47 controls
  • Both controller and processor: Include A.1 + A.2 + A.3 = 78 controls

Implementation Status values: Implemented | Partially Implemented | Planned | Not Applicable


ISO 27701:2019 → 2025 Key Differences

Topic2019 Edition2025 Edition
Standard typeExtension of ISO 27001Standalone standard
ISO 27001 prerequisiteRequiredOptional (integration supported)
HLS clausesDerived from ISO 27001Own full Clauses 4–10
Controller controlsAnnex A - 31 controls (7.2.1–7.5.4)A.1 - 31 controls
Processor controlsAnnex B - 18 controls (8.2.1–8.5.8)A.2 - 18 controls
Security controlsInherited via ISO 27001A.3 - 29 standalone
Implementation guidanceMinimalAnnex B (new)
GDPR mappingAnnex DUpdated mapping annex
Certification pathRequired ISO 27001 firstCan certify PIMS independently
New control areas-Cloud, IoT, AI processing
Transition deadline-October 2028

Mandatory Documentation Checklist

Produce this when asked for certification readiness:

This is the start of the file. Read the full SKILL.md on GitHub.

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
687
Repository forks
148
7-day trend score
33

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/sushegaad/claude-skills-governance-risk-and-compliance/iso27701/badge)](https://verified-skill.com/skills/sushegaad/claude-skills-governance-risk-and-compliance/iso27701)

Something wrong with this skill or its page? Tell us.