ISO 27701 Assessment
Assess ISO/IEC 27701:2019 Privacy Information Management System (PIMS) compliance for "$ARGUMENTS". Evaluate PIMS requirements, controller-specific and processor-specific controls, and map controls to GDPR articles and CCPA sections.
Prerequisites
Read .metapowers/compliance/$ARGUMENTS/00-scope.md. If this file does not exist, tell the user:
Phase 0 (Scope) has not been completed for "$ARGUMENTS". Run /compliance:regulatory-landscape $ARGUMENTS first, or use --skip-checks to bypass.
If --skip-checks is present in $ARGUMENTS, skip this check.
Process
Read context files:
- Read
plugins/compliance/shared/grc-lifecycle-guide.md for GRC methodology reference
- Read
plugins/compliance/shared/assessment-template.md for output structure
- Read
.metapowers/compliance/$ARGUMENTS/00-scope.md for scope and control framework context
PIMS scope and context:
- Determine organization's role(s): PII controller, PII processor, or both
- Identify PII processing activities and data flows
- Map interested parties and their privacy requirements
- Review existing ISO 27001 ISMS scope for PIMS extension alignment
PIMS requirements assessment (Clauses 5-8):
- Clause 5: PIMS-specific requirements related to ISO 27001 — assess context, leadership, planning, support, operation, performance evaluation, improvement with privacy extensions
- Clause 6: PIMS-specific guidance related to ISO 27002 — assess privacy-specific implementation guidance for applicable ISO 27002 controls
- Clause 7: Additional ISO 27002 guidance for PII controllers — assess controller obligations
- Clause 8: Additional ISO 27002 guidance for PII processors — assess processor obligations
- Score each clause: Conforming / Minor nonconformity / Major nonconformity
Controller-specific controls assessment (Annex A):
- Legal basis — assess documentation and validation of legal bases for processing (consent, contract, legitimate interest, legal obligation)
- Consent management — assess consent collection, granularity, withdrawal mechanisms, consent records
- Data subject rights — assess right to access, rectification, erasure, portability, restriction, objection
- Privacy by design and default — assess data protection impact assessments (DPIAs), privacy-by-design principles
- Data sharing and transfer — assess third-party data sharing agreements, cross-border transfer mechanisms (SCCs, BCRs, adequacy decisions)
- Score each area: Implemented / Partially Implemented / Not Implemented
Processor-specific controls assessment (Annex B):
- Processing only on instruction — assess controls ensuring processing only per controller instructions
- Sub-processor management — assess sub-processor authorization, notification, contractual flow-down, due diligence
- Data breach notification — assess processor-to-controller breach notification procedures, timeline, content
- Data return and deletion — assess data return/deletion upon contract termination, deletion verification
- Audit support — assess support for controller audits, information provision
- Score each area: Implemented / Partially Implemented / Not Implemented
GDPR mapping:
- Map ISO 27701 controls to GDPR articles (Articles 5-49)
- Identify controls that directly satisfy GDPR requirements
- Highlight GDPR requirements not fully covered by ISO 27701 controls
- Assess GDPR-specific requirements: DPO, records of processing, DPIAs, lead supervisory authority
CCPA mapping:
- Map ISO 27701 controls to CCPA sections (California Consumer Privacy Act / CPRA)
- Identify controls satisfying consumer rights (right to know, delete, opt-out, non-discrimination)
- Highlight CCPA-specific requirements not covered (sale of personal information, financial incentives, service provider obligations)
Privacy program overlap assessment:
- Identify existing privacy program elements that already satisfy ISO 27701
- Assess gap between current privacy program and ISO 27701 requirements
- Document where ISO 27701 certification would provide incremental value beyond existing compliance
Write the artifact to .metapowers/compliance/$ARGUMENTS/01-assess/iso27701.md following the assessment template structure with:
- PIMS Scope — roles, data flows, interested parties
- PIMS Requirements Assessment — Clauses 5-8 scored with findings
- Controller Controls — Annex A controls scored with findings
- Processor Controls — Annex B controls scored with findings
- GDPR Mapping — control-to-article mapping with coverage analysis
- CCPA Mapping — control-to-section mapping with coverage analysis
- Privacy Program Overlap — existing coverage and incremental value
- Overall Compliance Score — aggregate score with heatmap
- Remediation Priorities — ranked list of gaps to address
Output
The ISO 27701 assessment written to .metapowers/compliance/$ARGUMENTS/01-assess/iso27701.md. Present a summary to the user highlighting:
- Organization role (controller/processor/both) and PIMS scope
- Overall PIMS compliance score
- GDPR coverage percentage via ISO 27701 controls
- Top 3 privacy control gaps
- Overlap with existing privacy program
1---2name: iso277013description: Assess ISO 27701 privacy extension — PIMS requirements, GDPR/CCPA mapping4---56# ISO 27701 Assessment78Assess ISO/IEC 27701:2019 Privacy Information Management System (PIMS) compliance for "$ARGUMENTS". Evaluate PIMS requirements, controller-specific and processor-specific controls, and map controls to GDPR articles and CCPA sections.910## Prerequisites1112Read `.metapowers/compliance/$ARGUMENTS/00-scope.md`. If this file does not exist, tell the user:1314> Phase 0 (Scope) has not been completed for "$ARGUMENTS". Run `/compliance:regulatory-landscape $ARGUMENTS` first, or use `--skip-checks` to bypass.1516If `--skip-checks` is present in $ARGUMENTS, skip this check.1718## Process19201. **Read context files:**21 - Read `plugins/compliance/shared/grc-lifecycle-guide.md` for GRC methodology reference22 - Read `plugins/compliance/shared/assessment-template.md` for output structure23 - Read `.metapowers/compliance/$ARGUMENTS/00-scope.md` for scope and control framework context24252. **PIMS scope and context:**26 - Determine organization's role(s): PII controller, PII processor, or both27 - Identify PII processing activities and data flows28 - Map interested parties and their privacy requirements29 - Review existing ISO 27001 ISMS scope for PIMS extension alignment30313. **PIMS requirements assessment (Clauses 5-8):**32 - **Clause 5: PIMS-specific requirements related to ISO 27001** — assess context, leadership, planning, support, operation, performance evaluation, improvement with privacy extensions33 - **Clause 6: PIMS-specific guidance related to ISO 27002** — assess privacy-specific implementation guidance for applicable ISO 27002 controls34 - **Clause 7: Additional ISO 27002 guidance for PII controllers** — assess controller obligations35 - **Clause 8: Additional ISO 27002 guidance for PII processors** — assess processor obligations36 - Score each clause: Conforming / Minor nonconformity / Major nonconformity37384. **Controller-specific controls assessment (Annex A):**39 - **Legal basis** — assess documentation and validation of legal bases for processing (consent, contract, legitimate interest, legal obligation)40 - **Consent management** — assess consent collection, granularity, withdrawal mechanisms, consent records41 - **Data subject rights** — assess right to access, rectification, erasure, portability, restriction, objection42 - **Privacy by design and default** — assess data protection impact assessments (DPIAs), privacy-by-design principles43 - **Data sharing and transfer** — assess third-party data sharing agreements, cross-border transfer mechanisms (SCCs, BCRs, adequacy decisions)44 - Score each area: Implemented / Partially Implemented / Not Implemented45465. **Processor-specific controls assessment (Annex B):**47 - **Processing only on instruction** — assess controls ensuring processing only per controller instructions48 - **Sub-processor management** — assess sub-processor authorization, notification, contractual flow-down, due diligence49 - **Data breach notification** — assess processor-to-controller breach notification procedures, timeline, content50 - **Data return and deletion** — assess data return/deletion upon contract termination, deletion verification51 - **Audit support** — assess support for controller audits, information provision52 - Score each area: Implemented / Partially Implemented / Not Implemented53546. **GDPR mapping:**55 - Map ISO 27701 controls to GDPR articles (Articles 5-49)56 - Identify controls that directly satisfy GDPR requirements57 - Highlight GDPR requirements not fully covered by ISO 27701 controls58 - Assess GDPR-specific requirements: DPO, records of processing, DPIAs, lead supervisory authority59607. **CCPA mapping:**61 - Map ISO 27701 controls to CCPA sections (California Consumer Privacy Act / CPRA)62 - Identify controls satisfying consumer rights (right to know, delete, opt-out, non-discrimination)63 - Highlight CCPA-specific requirements not covered (sale of personal information, financial incentives, service provider obligations)64658. **Privacy program overlap assessment:**66 - Identify existing privacy program elements that already satisfy ISO 2770167 - Assess gap between current privacy program and ISO 27701 requirements68 - Document where ISO 27701 certification would provide incremental value beyond existing compliance69709. **Write the artifact** to `.metapowers/compliance/$ARGUMENTS/01-assess/iso27701.md` following the assessment template structure with:71 - **PIMS Scope** — roles, data flows, interested parties72 - **PIMS Requirements Assessment** — Clauses 5-8 scored with findings73 - **Controller Controls** — Annex A controls scored with findings74 - **Processor Controls** — Annex B controls scored with findings75 - **GDPR Mapping** — control-to-article mapping with coverage analysis76 - **CCPA Mapping** — control-to-section mapping with coverage analysis77 - **Privacy Program Overlap** — existing coverage and incremental value78 - **Overall Compliance Score** — aggregate score with heatmap79 - **Remediation Priorities** — ranked list of gaps to address8081## Output8283The ISO 27701 assessment written to `.metapowers/compliance/$ARGUMENTS/01-assess/iso27701.md`. Present a summary to the user highlighting:84- Organization role (controller/processor/both) and PIMS scope85- Overall PIMS compliance score86- GDPR coverage percentage via ISO 27701 controls87- Top 3 privacy control gaps88- Overlap with existing privacy program