ISO/IEC 27701 Lead Implementer Training — Lesson 3: Controller, Processor, Rights, Vendors, Transfers, and Operations

Learning Objectives

• Interpret the principles, requirements, roles, and dependencies shaping controller, processor, rights, vendors, transfers, and operations.
• Apply the workflow and produce PIMS operational control evidence library that another practitioner can review.
• Analyze “a processor cannot demonstrate deletion after contract termination” and recommend a proportionate, supported response.

Detailed Topics

• controller controls
• processor controls
• data-subject rights
• vendor agreements
• international transfers
• privacy by design
• incident management
• retention controls
• Competence, communication, governance, documented information, risk, validation, and follow-up considerations

Instructor Demonstration

The instructor demonstrates the controller, processor, rights, vendors, transfers, and operations workflow, identifies the applicable inputs and responsibilities, records checkpoints in PIMS operational control evidence library, and contrasts the accepted state with a condition where a processor cannot demonstrate deletion after contract termination.

Hands-On Exercise

Complete a controlled implementation, audit, assessment, or foundation exercise for Controller, Processor, Rights, Vendors, Transfers, and Operations. Establish scope and criteria, collect or create evidence, examine “a processor cannot demonstrate deletion after contract termination,” reach a supported conclusion, and preserve the result in PIMS operational control evidence library.

1. Confirm objectives, scope, roles, criteria, stakeholders, and expected outputs.
2. Perform the planned activities while recording assumptions, evidence, and decisions.
3. Test a normal case, an exception, and a follow-up or improvement condition.
4. Document conclusions, owners, due dates, escalation, and verification requirements.

Scenario Analysis

• Identify the requirement or principle with the strongest influence on controller, processor, rights, vendors, transfers, and operations.
• Compare two defensible responses and explain their governance, risk, and evidence trade-offs.
• Determine how PIMS operational control evidence library should be approved, retained, reviewed, and updated.

Troubleshooting Guidance

Separate missing evidence from ineffective practice, and distinguish a documentation issue from a control, process, governance, or competence failure. Use PIMS operational control evidence library to trace the earliest divergence. Treat “a processor cannot demonstrate deletion after contract termination” as a hypothesis until the response is validated against the applicable requirement and intended outcome.

Validation Checklist

• The scope, criteria, stakeholders, and intended outcome for controller, processor, rights, vendors, transfers, and operations are explicit.
• The PIMS operational control evidence library links statements and decisions to objective, reviewable support.
• Responsibilities, competence, communication, risk, legal duties, and change impact were considered where relevant.
• Findings, corrective actions, monitoring, review triggers, and improvement ownership are clear.

Lesson Outcome

Learners can apply Controller, Processor, Rights, Vendors, Transfers, and Operations, explain the reasoning used, and defend the result through PIMS operational control evidence library.