Study guide
4.4 Processor/Vendor Evaluation & Physical/Environmental Controls
Certified Information Privacy Manager CIPM
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 CIPM Exam Facts & Format 1.2 The CIPM Body of Knowledge: Six Domains & How the Exam Is Built 1.3 Study Strategy, Timeline & How to Use This Guide
2 Domain I: Developing a Privacy Program Framework
2.1 Program Scope, Strategy & Governance Model 2.2 Stakeholders, Privacy Team Structure & Common Vocabulary 2.3 Applicable Regulations, Oversight Agencies & Non-Compliance Impact 2.4 Personal Information Sources, Cross-Border Operations & AI Privacy Risk 2.5 Business Model, Operating Environment & Risk Appetite 2.6 Structuring the Privacy Team: DPO, CPO, Representatives & Resourcing 2.7 Vision, Mission & the Privacy Program Communication Plan 2.8 Policy Access, Version Control & Role-Relevant Updates 2.9 Codes of Conduct, Certifications & Self-Certification Mechanisms
3 Domain II: Establishing Program Governance
3.1 Privacy Policies & Life-Cycle Processes 3.2 Breach, Complaint, DSR & Retention Plans 3.3 Roles, Responsibilities, Metrics & Continuous Legal Monitoring 3.4 Training & Awareness Activities 3.5 Governance Bodies, Program Charter & Escalation Paths 3.6 Governing Internal & External Data Sharing and Disclosure 3.7 Retention Schedules & Defensible Disposal 3.8 Regulatory Change Monitoring & Enforcement Systems
4 Domain III: Operational Life Cycle — Assessing Data
4.1 Data Inventories, Flows & Life-Cycle Mapping 4.2 Data Discovery, System Integrations & Keeping the Inventory Current 4.3 Policy Compliance Measurement & Gap Analysis 4.4 Processor/Vendor Evaluation & Physical/Environmental Controls 4.5 Third-Party Risk Life Cycle & Sub-Processor Chains
5 Domain III (continued): Assessing Data — Technical & Physical Controls, M&A Risk
4.6 Technical Controls, Use/Retention Limits & Data Location 4.7 Physical & Environmental Controls in Depth 4.8 Mergers, Acquisitions & Divestitures Data Risk
6 Domain IV: Operational Life Cycle — Protecting Personal Data
5.1 Information Security Practices, Data Classification & Access Controls 5.2 Privacy by Design Principles & the SDLC 5.3 Organizational Guidelines for Data Use & Secondary-Use Governance 5.4 Privacy-Enhancing Technologies & Technical Control Enforcement 5.5 Technical, Administrative & Organizational Measures 5.6 Access Reviews, Monitoring & Enforcing Technical Controls
7 Domain V: Operational Life Cycle — Sustaining Program Performance
6.1 Privacy Metrics for Program Performance 6.2 Auditing the Privacy Program 6.3 Continuous Assessment: PIA, DPIA, TIA, LIA & PTA 6.4 Risk Mitigation, Post-M&A Assessment & Ethical AI Use
8 Domain VI: Operational Life Cycle — Responding to Requests & Incidents
7.1 Data Subject Access Requests & Consent/Rights Processes 7.2 Global Privacy Legislation on Data Subject Rights 7.3 Incident Handling, Breach Response & Records 7.4 Post-Incident Review & IR Plan Improvement 7.5 Privacy Notices & Transparency Obligations 7.6 Complaint Handling & Regulator Interaction 7.7 Breach Communications to Regulators, Individuals & Other Stakeholders
9 Final Review & Exam Strategy
8.1 Mixed-Domain Scenarios & Common Exam Traps 8.2 Test-Day Logistics, Score Strategy & Credential Maintenance
4.4 Processor/Vendor Evaluation & Physical/Environmental Controls
Key Takeaways Explain This Topic AI
Processor due diligence must occur before contract signing and cover security posture, sub-processor chain, cross-border transfer mechanism, and privacy track record
A Data Processing Agreement (DPA) or Article 28 Terms is legally required under GDPR Art. 28 and must specify purpose limitation, confidentiality, security, sub-processor rules, deletion, and audit rights
Post-Schrems II, restricted transfers to third countries require a transfer impact assessment (TIA) verifying the SCCs can be effectively enforced in the recipient jurisdiction
Physical controls — clean-desk, visitor access, media sanitization, device security, document retention and destruction — protect data that encryption cannot reach
Vendor risk and physical risk are assessed at the most appropriate functional level: procurement, internal audit, information security, physical security, or the DPA review
Last updated: August 2026
Two Risk Surfaces Outside the Controller's Direct Custody
Personal data does not stay inside the four walls of the organization. It moves to processors and third-party vendors (Domain III.B) and it lives in physical locations — data centers, offices, paper files, removable media, and end-user devices (Domain III.C). The CIPM Body of Knowledge treats these as a single competency cluster because the privacy manager must evaluate risk in both places where data resides outside direct application-layer controls.
- III.B — Evaluating Processors and Third-Party Vendors
- The Outsourcing Risk
Outsourcing processing shifts operational custody but not accountability . Under GDPR Art. 28, the controller remains responsible for the processor's compliance with the controller's instructions. Under CCPA/CPRA, service providers and contractors must be contractually bound to equivalent restrictions. Outsourcing introduces several specific risks:
Unauthorized use — the processor uses data for its own purposes beyond the controller's instructions.
Sub-processor sprawl — the processor engages sub-processors the controller never approved.
Cross-border exposure — data is moved to a jurisdiction without an adequate transfer mechanism.
Security failure — the processor's controls are weaker than the controller's, creating a weakest-link breach.
Concentration risk — many controllers depend on one processor (e.g., a single cloud region), creating systemic exposure.
Due Diligence Before Contract
Vendor due diligence should occur before contract signing, not after. A typical due-diligence package includes:
- Dimension Evidence Requested
- Security posture SOC 2 Type II report, ISO 27001 certificate, penetration test summary
- Privacy program ISO 27701 certificate, prior DPIAs, breach history
- Sub-processor list Names, locations, functions, and sub-contract chain
- Transfer mechanism SCCs, BCRs, adequacy reliance, or derogation justification
- Personnel controls Background checks, training records, access reviews
- Incident response Notification SLA (≤ 24–48 hours), forensic capabilities
- Financial viability Audit or credit signals indicating the vendor will persist for the contract term
- The DPA / Article 28 Terms
A Data Processing Agreement (DPA) — also called Article 28 Terms — is mandatory under GDPR Art. 28(3) and must include, at minimum:
Subject matter and duration of processing.
Nature and purpose of processing.
Type of personal data and categories of data subjects .
Obligations and rights of the controller.
Processor obligations to: process only on documented instructions, ensure confidentiality of personnel, implement Art. 32 security, respect sub-processor conditions, assist with DSARs, assist with breach notification, assist with DPIAs, and delete or return data at end of service.
Audit rights — the controller's right to audit or commission audits of the processor.
The Accountability for Received Transfers (ART) clause added to the 2021 SCCs extends accountability downstream: the importer must pass equivalent obligations to any sub-importer, so the controller's reach follows the data.
Transfer Impact Assessments (TIAs)
After Schrems II (CJEU C-311/18) , a controller relying on SCCs for a transfer to a third country must perform a Transfer Impact Assessment (TIA) to verify the SCCs can be effectively enforced in the recipient jurisdiction. A TIA examines:
The data and transfer specifics (what data, which importer, which destination).
The legal regime of the destination country — particularly government surveillance laws (e.g., US FISA 702, EO 12333).
Whether the SCCs can be enforced in practice — are there supplementary measures (encryption with controller-held keys, pseudonymization, contractual transparency) needed?
A documented conclusion on whether the transfer can proceed or must be suspended.
The US-EU Data Privacy Framework (DPF) , adopted in 2023, provides an adequacy route for certified US companies, but transfers to non-certified importers still require SCCs plus a TIA.
Functional-Level Assessment
The Body of Knowledge stresses that processor risk is assessed at the most appropriate functional level , not always by the privacy team alone:
Procurement — commercial terms, vendor viability, contract execution.
Information security — technical security review, penetration test findings, access model.
Internal audit — independent assurance over the vendor's control environment.
Physical security — on-site inspection for data-center or paper-handling vendors.
DPA review — privacy counsel and the DPO confirm Art. 28 terms and transfer mechanism.
Ongoing Monitoring
Due diligence is a snapshot; monitoring is continuous. Mature programs:
Review SOC 2 reports annually and track any qualified opinions.
Reconcile the sub-processor list quarterly against notifications received.
Re-test the TIA on material legal changes (new surveillance law, invalidated adequacy).
Track vendor incidents against the DPA's notification SLA.
Offboard vendors with a verified deletion certificate at contract end.
III.C — Physical and Environmental Controls
Personal data often exists in forms encryption cannot protect: paper files, whiteboards, removable media, and even spoken conversations. Physical and environmental controls close that gap.
Physical Control Categories
Control Purpose Common Implementation
Clean-desk policy Prevent casual exposure of paper and screens Locked drawers, automatic screen lock, no sticky notes with passwords
Visitor access Limit unauthorized physical access Sign-in logs, escorts, badge expiry, restricted zones
Media sanitization & disposal Prevent data recovery from retired media NIST 800-88 guidelines — Clear, Purge, Destroy; certificate of destruction
Document retention & destruction Enforce storage limitation on paper Locked retention cabinets, scheduled shredding, secure-destruction vendor
Device security Protect laptops, phones, and removable media Full-disk encryption, MDM, cable locks, remote wipe, USB port control
Environmental controls Protect data center and office integrity Fire suppression, HVAC, flood detection, UPS/generator power
Data center controls Restrict physical access to servers Biometric access, mantraps, CCTV, 24/7 staffing, dual control
Operational Risks of Physical Locations
A privacy manager should walk through each physical location where personal data is handled and ask what could go wrong:
Data center — fire, flood, power loss, or unauthorized rack access could destroy or expose data.
Open-plan office — overheard conversations, shoulder-surfing, unattended printouts.
Home office (post-pandemic norm) — family members, shared devices, unshredded printouts in household waste.
Paper records archive — uncontrolled retention, rodent/water damage, unauthorized browsing.
Removable media — lost USB drives, unencrypted backups leaving the building.
Worked Scenario: Cloud CRM with Paper Onboarding
A financial services firm onboards clients through a paper application form that is later scanned into a cloud CRM. The privacy team's vendor evaluation confirms the CRM provider is ISO 27701 certified, signs a DPA with an ART clause, and relies on SCCs plus a TIA showing the US importer is DPF-certified. The physical controls review, however, finds branch offices have no clean-desk policy, printouts sit in trays overnight, and the shredding vendor has not provided a destruction certificate in 18 months. The gap analysis records: (1) a High compliance gap — DPA lacks audit rights (Art. 28(3)(h)); (2) a High risk gap — no clean-desk or locked-storage policy for paper containing financial data; (3) a Medium risk gap — shredding vendor unverified. The program roadmap funds a clean-desk rollout, a locked-storage procurement, and a DPA amendment adding audit rights within 60 days.
Why Both Surfaces Matter Together
A controller can have a flawless DPA and still suffer a breach because a branch office left printouts on a desk. Conversely, rigorous clean-desk discipline cannot rescue a processor relationship without a transfer impact assessment. The privacy manager must hold both surfaces to the same standard: documented requirements, scored gaps, and verified closure.