
vendor-privacy-management-skills
11 vendor management skills: DPA drafting, sub-processor management, vendor risk scoring, breach cascade, due diligence
- version
- 1.0.0
- GitHub stars
- 340
Install
/plugin install vendor-privacy-management-skills@privacy-data-protection-skillsRun it inside Claude Code after adding the marketplace with /plugin marketplace add mukul975/Privacy-Data-Protection-Skills.
Contents
Discovered from sourceSkills 11
Cloud Service Provider Privacy Assessment
Overview
Cloud service providers present unique privacy assessment challenges due to shared responsibility models, multi-tenancy architectures, global infrastructure, and the abstraction of physical processing locations. GDPR Article 28 obligations apply fully to cloud processing relationships, but the assessment approach must account for cloud-specific characteristics.
ISO/IEC 27018:2019 provides the international standard for protecting personally identifiable information (PII) in public clouds, supplementing ISO 27001 with cloud-specific privacy controls. The Cloud Security Alliance (CSA) STAR program provides a cloud-specific security assurance framework. SOC 2 Type II with the Privacy trust services criterion addresses personal data handling controls.
At Summit Cloud Partners, cloud providers undergo enhanced assessment incorporating these cloud-specific frameworks alongside standard vendor due diligence.
Cloud Service Models and Privacy Implications
IaaS (Infrastructure as a Service)
| Aspect | Controller Responsibility | Provider Responsibility |
|---|---|---|
| Data encryption at rest | Configure and manage keys | Provide encryption infrastructure |
| Access management (app level) | Define and manage | Provide IAM platform |
| Network security (app level) | Configure security groups, firewall rules | Provide network infrastructure |
| Physical security | None | Full responsibility |
| Patch management (OS) | Controller (or managed service) | Hypervisor and below |
| Data backup | Configure and manage | Provide backup infrastructure |
| Incident detection (app) | Application-level monitoring | Infrastructure-level monitoring |
PaaS (Platform as a Service)
| Aspect | Controller Responsibility | Provider Responsibility |
|---|---|---|
| Application code security | Full responsibility | None |
| Data handling in application | Full responsibility | None |
| Runtime and middleware | Limited — configuration only | Manage platform components |
| OS and infrastructure | None | Full responsibility |
| Platform security patching | None | Full responsibility |
| Identity management | Configure | Provide identity platform |
SaaS (Software as a Service)
| Aspect | Controller Responsibility | Provider Responsibility |
|---|---|---|
| Data entered by users | Determine what data to process | Process per controller instructions |
| Application security | None (except configuration) | Full responsibility |
| Infrastructure security | None | Full responsibility |
| Data portability | Define export requirements | Provide export functionality |
| Data deletion | Request deletion | Implement deletion per DPA |
| Access configuration | Configure user roles | Provide RBAC platform |
Assessment Framework
Domain 1: Data Residency and Sovereignty
Assessment Questions:
| # | Question | Expected Evidence |
|---|---|---|
| 1.1 | In which regions/availability zones will personal data be stored at rest? | Architecture documentation specifying data storage locations |
| 1.2 | Can the controller restrict processing to specific geographic regions? | Configuration documentation showing region-locking capability |
| 1.3 | Are there any circumstances where data may be processed outside the selected region? | Disclosure of any cross-region processing (DR, support, analytics) |
| 1.4 | Where is metadata and telemetry data stored? | Often stored in provider's home jurisdiction — must be disclosed |
| 1.5 | Where do support staff access data from? | List of countries from which support personnel may access data |
| 1.6 | What government access or disclosure obligations apply in processing jurisdictions? | Legal analysis of government access powers per EDPB Recommendations 01/2020 |
Domain 2: Multi-Tenancy and Data Isolation
| # | Question | Expected Evidence |
|---|---|---|
| 2.1 | How is tenant data isolated from other customers' data? | Architecture documentation — logical/physical separation details |
| 2.2 | Are encryption keys unique per tenant? | Key management architecture documentation |
| 2.3 | Can one tenant's operations affect another tenant's data? | Side-channel and cross-tenant risk assessment |
| 2.4 | How are shared infrastructure components secured? | Hypervisor security, shared storage controls |
| 2.5 | What tenant isolation testing has been performed? | Penetration test results covering cross-tenant attacks |
Domain 3: ISO 27018 Cloud Privacy Controls
ISO/IEC 27018:2019 extends ISO 27001 with cloud-specific PII protection controls:
| Control | Requirement | Assessment Check |
|---|---|---|
| A.1 | PII processor consent — process only per controller instructions | Verify contractual terms and processing boundaries |
| A.2 | Purpose limitation — no processing beyond controller purpose | Review processing scope documentation |
| A.3 | Use for marketing — no use of PII for marketing without consent | Confirm no data monetization or marketing use |
| A.4 | Notification — notify controller of government access requests | Verify government access notification process |
| A.5 | Disclosure — document all disclosures of PII | Review disclosure logging mechanism |
| A.10 | Return, transfer, and disposal — secure data handling at termination | Verify deletion procedures and certification |
| A.11 | Confidentiality — binding confidentiality obligations on personnel | Verify personnel agreements cover cloud-specific risks |
| A.12 | Sub-contracting — notification of sub-processor engagement | Verify sub-processor management per Art. 28(2) |
Domain 4: CSA STAR Assessment
The Cloud Security Alliance STAR (Security, Trust, Assurance, and Risk) program provides three levels:
| Level | Description | Assessment Method |
|---|---|---|
| Level 1: Self-Assessment | Provider completes CSA Consensus Assessments Initiative Questionnaire (CAIQ) | Review self-assessment for completeness and substantiation |
| Level 2: Third-Party Audit | Independent audit against CSA Cloud Controls Matrix (CCM) | Review audit report, scope, and findings |
| Level 3: Continuous Monitoring | Real-time monitoring of control effectiveness | Review continuous monitoring dashboard and alerts |
Key CCM Control Domains for Privacy:
| Domain | Controls | Privacy Relevance |
|---|---|---|
| DSP (Data Security & Privacy) | DSP-01 through DSP-19 | Data classification, retention, inventory, privacy by design |
| GRC (Governance, Risk, Compliance) | GRC-01 through GRC-08 | Governance framework, risk assessment, policy management |
| IAM (Identity & Access Management) | IAM-01 through IAM-16 | Access control, credential management, MFA |
| SEF (Security Incident Management) | SEF-01 through SEF-08 | Incident response, breach notification |
Domain 5: SOC 2 Type II Privacy Criterion
The AICPA Trust Services Criteria Privacy criterion evaluates:
| Criterion | Area | Assessment Focus |
|---|---|---|
| P1 | Notice | Provider discloses privacy practices to controllers |
| P2 | Choice and consent | Controller can configure privacy settings |
| P3 | Collection | Data collection limited to stated purposes |
| P4 | Use, retention, disposal | Processing per instructions; retention per DPA; certified deletion |
| P5 | Access | Controller can access and retrieve their data |
| P6 | Disclosure to third parties | Sub-processor disclosure and management |
| P7 | Security for privacy | Technical controls protecting PII |
| P8 | Quality | Data integrity and accuracy controls |
| P9 | Monitoring and enforcement | Compliance monitoring and breach response |
Domain 6: Shared Responsibility Model Mapping
Document the shared responsibility boundary for every control domain:
| Control Domain | Controller Responsibility | Provider Responsibility | Gap/Risk |
|---|---|---|---|
| Data classification | Classify data before upload | Provide classification tools | [Gap?] |
| Encryption key management | [Depends on model] | [Depends on model] | [Gap?] |
| Access control (application) | [Depends on model] | [Depends on model] | [Gap?] |
| Vulnerability management | [Depends on model] | [Depends on model] | [Gap?] |
| Incident detection | [Depends on model] | [Depends on model] | [Gap?] |
| Data backup | [Depends on model] | [Depends on model] | [Gap?] |
| Compliance reporting | [Depends on model] | [Depends on model] | [Gap?] |
Assessment Scoring
| Domain | Weight | Score (1-5) | Weighted |
|---|---|---|---|
| Data residency and sovereignty | 20% | ||
| Multi-tenancy and isolation | 20% | ||
| ISO 27018 compliance | 15% | ||
| CSA STAR level | 15% | ||
| SOC 2 Privacy criterion | 15% | ||
| Shared responsibility clarity | 15% | ||
| TOTAL | 100% |
Key Regulatory References
- GDPR Article 28 — Controller-processor relationship applies fully to cloud
- GDPR Article 32 — Security measures including cloud-specific controls
- ISO/IEC 27018:2019 — Code of practice for protection of PII in public clouds
- ISO/IEC 27017:2015 — Code of practice for information security controls for cloud services
- CSA Cloud Controls Matrix (CCM) v4.0 — Cloud security control framework
- EDPB Recommendations 01/2020 — Supplementary measures for cloud transfers
- ENISA Cloud Computing Risk Assessment (2009, updated) — EU cloud risk framework
Data Processing Agreement Drafting
Overview
GDPR Article 28(3) mandates that processing by a processor shall be governed by a contract or other legal act that is binding on the processor. This contract must set out specific mandatory provisions covering the subject-matter and duration of processing, the nature and purpose, the type of personal data, the categories of data subjects, and the obligations and rights of the controller. The EDPB has emphasized in Guidelines 07/2020 that these requirements are not optional and that failure to include any mandatory element renders the DPA non-compliant.
The European Commission adopted Standard Contractual Clauses for controller-to-processor arrangements in Implementing Decision (EU) 2021/915, providing a reference framework that organizations may adopt or adapt.
Mandatory DPA Provisions Under Article 28(3)
Provision 1: Subject-Matter and Duration
The DPA must specify what processing the vendor will perform and for how long.
Required Elements:
| Element | Description | Example |
|---|---|---|
| Subject-matter | The specific service being provided | "Cloud-hosted customer analytics platform" |
| Duration | Period of processing | "Duration of the Master Services Agreement plus 90-day data return/deletion period" |
| Commencement date | When processing begins | "Effective as of the MSA effective date" |
| Survival clauses | Obligations surviving termination | "Confidentiality, deletion certification, and audit rights survive for 3 years" |
Provision 2: Nature and Purpose of Processing
Required Elements:
| Element | Description | Example |
|---|---|---|
| Nature of processing | Operations performed on personal data | "Collection via API ingestion, storage in encrypted database, automated analysis, aggregated reporting, deletion upon contract termination" |
| Purpose of processing | Why processing occurs | "To provide Summit Cloud Partners with customer behavior analytics enabling product improvement decisions" |
| Processing instructions scope | Boundaries of processing | "Processor shall process personal data only for the purposes specified in Annex 1 and only on documented instructions from the Controller" |
Provision 3: Type of Personal Data
Enumerate all categories of personal data the processor will handle.
Summit Cloud Partners — Example Annex:
| Data Category | Description | Sensitivity Level |
|---|---|---|
| Contact information | Name, email address, phone number | Standard |
| Account identifiers | User ID, account number, tenant ID | Standard |
| Usage data | Feature usage logs, session duration, click paths | Standard |
| Device information | IP address, browser type, OS version | Standard |
| Location data | City/region derived from IP address (not precise GPS) | Elevated |
| Payment metadata | Transaction dates, plan type (not card numbers) | Elevated |
Provision 4: Categories of Data Subjects
| Category | Description | Approximate Volume |
|---|---|---|
| Enterprise customers | Named users of Summit Cloud Partners platform | 50,000 |
| Trial users | Users on free trial accounts | 15,000 |
| API consumers | Developers using Summit Cloud Partners API | 5,000 |
Provision 5: Obligations and Rights of the Controller
The DPA must set out what the controller is entitled to do and what the controller must provide to the processor:
- Right to issue instructions: The controller has the right to issue documented written instructions regarding processing
- Right to audit: The controller may audit the processor's compliance (Article 28(3)(h))
- Obligation to determine lawful basis: The controller confirms that processing is lawful under Article 6
- Obligation to respond to data subjects: The controller is responsible for responding to data subject requests, with processor assistance
- Obligation to notify processor of relevant changes: Changes to processing instructions, data categories, or regulatory requirements
Provision 6: Processor Obligations (Article 28(3)(a)-(h))
The eight mandatory processor obligations under Article 28(3):
(a) Process only on documented instructions
"The Processor shall process personal data only on documented instructions from the Controller, including with regard to transfers of personal data to a third country or an international organisation, unless required to do so by Union or Member State law to which the Processor is subject; in such a case, the Processor shall inform the Controller of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest."
(b) Confidentiality obligations
"The Processor shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality."
(c) Security measures (Article 32)
"The Processor shall implement all measures required pursuant to Article 32, including as appropriate: (i) pseudonymisation and encryption of personal data; (ii) the ability to ensure ongoing confidentiality, integrity, availability and resilience of processing systems; (iii) the ability to restore availability and access to personal data in a timely manner in the event of a physical or technical incident; (iv) a process for regularly testing, assessing, and evaluating the effectiveness of technical and organisational measures."
(d) Sub-processor conditions
"The Processor shall not engage another processor without prior specific or general written authorisation of the Controller. In the case of general written authorisation, the Processor shall inform the Controller of any intended changes concerning the addition or replacement of other processors, thereby giving the Controller the opportunity to object to such changes."
(e) Assist with data subject rights
"Taking into account the nature of the processing, the Processor shall assist the Controller by appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the Controller's obligation to respond to requests for exercising the data subject's rights laid down in Chapter III."
(f) Assist with compliance obligations
"The Processor shall assist the Controller in ensuring compliance with Articles 32 to 36, taking into account the nature of processing and the information available to the Processor."
(g) Deletion or return after termination
"At the choice of the Controller, the Processor shall delete or return all personal data to the Controller after the end of the provision of services relating to processing, and delete existing copies unless Union or Member State law requires storage of the personal data."
(h) Audit rights
"The Processor shall make available to the Controller all information necessary to demonstrate compliance with the obligations laid down in Article 28, and allow for and contribute to audits, including inspections, conducted by the Controller or another auditor mandated by the Controller."
Provision 7: Sub-Processor Cascade
When the processor engages sub-processors, Article 28(4) requires the same data protection obligations as in the controller-processor DPA to be imposed on the sub-processor by way of a contract. The sub-processor DPA must contain materially equivalent terms.
Sub-processor management provisions:
| Provision | Description |
|---|---|
| Authorization mechanism | General written authorization with notification of changes |
| Notification period | Minimum 30 calendar days before engaging new sub-processor |
| Objection right | Controller may object within the notification period |
| Objection consequence | If objection not resolved, either party may terminate affected services |
| Flow-down obligations | Sub-processor contract must impose equivalent Article 28(3) obligations |
| Liability | Processor remains fully liable for sub-processor compliance |
Provision 8: International Transfers
If personal data will be transferred outside the EEA, the DPA must address the transfer mechanism:
| Transfer Scenario | Required Mechanism |
|---|---|
| EEA to Adequacy country (per Art. 45) | Reference adequacy decision |
| EEA to non-adequate country | Standard Contractual Clauses (Commission Decision 2021/914) |
| EEA to non-adequate country with supplementary measures | SCCs plus technical/organizational/contractual supplementary measures per EDPB Recommendations 01/2020 |
DPA Drafting Checklist
| # | Requirement | Article | Status |
|---|---|---|---|
| 1 | Subject-matter and duration specified | 28(3) | [ ] |
| 2 | Nature and purpose of processing defined | 28(3) | [ ] |
| 3 | Types of personal data listed | 28(3) | [ ] |
| 4 | Categories of data subjects listed | 28(3) | [ ] |
| 5 | Controller obligations and rights defined | 28(3) | [ ] |
| 6 | Processor processes only on documented instructions | 28(3)(a) | [ ] |
| 7 | Confidentiality obligations for authorized personnel | 28(3)(b) | [ ] |
| 8 | Article 32 security measures implemented | 28(3)(c) | [ ] |
| 9 | Sub-processor conditions and authorization | 28(3)(d) | [ ] |
| 10 | Assistance with data subject rights | 28(3)(e) | [ ] |
| 11 | Assistance with Articles 32-36 compliance | 28(3)(f) | [ ] |
| 12 | Deletion or return upon termination | 28(3)(g) | [ ] |
| 13 | Audit rights and information access | 28(3)(h) | [ ] |
| 14 | Sub-processor flow-down obligations per Art. 28(4) | 28(4) | [ ] |
| 15 | International transfer mechanism (if applicable) | 28(3), Ch. V | [ ] |
| 16 | Breach notification obligations per Art. 33(2) | 33(2) | [ ] |
| 17 | DPA is in writing (including electronic form) | 28(9) | [ ] |
Key Regulatory References
- GDPR Article 28(3) — Mandatory DPA provisions
- GDPR Article 28(4) — Sub-processor flow-down obligations
- GDPR Article 28(9) — Written form requirement
- GDPR Article 32 — Security of processing
- GDPR Article 33(2) — Processor breach notification to controller
- Commission Implementing Decision (EU) 2021/915 — Standard Contractual Clauses for controller-to-processor
- EDPB Guidelines 07/2020 — Controller and processor concepts
- EDPB Recommendations 01/2020 — Supplementary measures for international transfers
SaaS Vendor Data Processing Inventory
Overview
Modern organizations rely on dozens to hundreds of SaaS applications, many of which process personal data. GDPR Article 30 requires controllers to maintain records of processing activities, which includes documenting all processors. Shadow IT — SaaS applications adopted by business units without formal procurement or privacy review — creates significant compliance risk because unrecorded processing cannot be properly governed.
The EDPB Guidelines 07/2020 emphasize that controllers cannot claim ignorance of processing performed by vendors they engage, even if the engagement happened informally. Summit Cloud Partners maintains a comprehensive SaaS Vendor Data Processing Inventory to track all cloud services processing personal data, including those discovered through shadow IT detection.
Inventory Framework
Tier 1: Sanctioned SaaS — Formally Procured
Applications that have gone through formal procurement, privacy review, and DPA execution.
| Field | Description |
|---|---|
| Vendor name | Legal entity name |
| Product/service name | SaaS product name |
| Category | CRM, HR, Analytics, Communication, DevOps, etc. |
| Business owner | Department and named individual |
| Procurement date | When the service was contracted |
| DPA status | Executed / In negotiation / Not required |
| DPA reference | DPA document reference number |
| Privacy review status | Completed / In progress / Pending |
| Risk tier | Per vendor risk scoring model |
| Personal data categories | What personal data is processed |
| Data subjects | Whose data is processed |
| Processing purposes | Why data is processed |
| Processing locations | Where data is stored/processed |
| Integration method | SSO, API, manual upload, etc. |
| Data flow direction | Inbound / Outbound / Bidirectional |
| Contract expiry | When the contract term ends |
| Auto-renewal date | When auto-renewal triggers |
| Annual cost | Total annual spend |
| License count | Number of active users/seats |
Tier 2: Known Unsanctioned — Shadow IT Detected
Applications detected through discovery tools that lack formal procurement or privacy review.
| Field | Description |
|---|---|
| Application name | As detected |
| Detection method | CASB, DNS, expense, SSO log, etc. |
| Detection date | When first observed |
| Usage scope | Estimated users and frequency |
| Likely data categories | Inferred from application type |
| Risk assessment | Preliminary risk level |
| Remediation status | Under review / Sanctioning in progress / Blocked / Accepted |
| Business unit | Department(s) using the application |
Tier 3: Evaluated and Excluded
Applications evaluated and determined to not process personal data.
| Field | Description |
|---|---|
| Application name | Product name |
| Evaluation date | When reviewed |
| Determination | No personal data processing |
| Rationale | Why excluded from inventory |
| Next review date | When to re-evaluate |
Shadow IT Discovery Methods
Method 1: Cloud Access Security Broker (CASB)
Deploy a CASB solution to monitor network traffic and identify cloud service usage.
Detection Capabilities:
- SaaS application identification via API call pattern matching
- User activity monitoring across sanctioned and unsanctioned services
- Data transfer volume estimation
- Risk scoring of discovered applications
Implementation at Summit Cloud Partners:
| Component | Detail |
|---|---|
| CASB vendor | Deployed as inline proxy and API connector |
| Coverage | All corporate network egress and managed endpoints |
| Discovery scope | HTTP/HTTPS traffic to known SaaS domains |
| Update frequency | Real-time discovery, weekly consolidated reporting |
| Integration | Feeds into SaaS inventory system via API |
Method 2: DNS and Firewall Log Analysis
Analyze DNS resolution logs and firewall traffic logs to identify connections to SaaS providers.
Process:
- Aggregate DNS query logs from internal resolvers
- Match resolved domains against SaaS provider domain databases
- Cross-reference with sanctioned vendor list
- Flag unmatched SaaS domains for investigation
Method 3: SSO and Identity Provider Logs
Review identity provider (IdP) logs for OAuth consent grants and SAML integrations.
Detection Signals:
- OAuth application consent grants not in approved list
- SAML service provider registrations
- OpenID Connect client registrations
- API token generation for third-party services
Method 4: Expense and Procurement Analysis
Review corporate expense reports and credit card statements for SaaS subscriptions.
Detection Signals:
- Recurring charges to known SaaS providers
- Expense claims categorized as "software" or "subscriptions"
- Purchase order requests for cloud services bypassing IT procurement
Method 5: API Integration Audit
Scan internal systems for outbound API connections to third-party services.
Detection Signals:
- Outbound API calls to non-sanctioned endpoints
- Webhook configurations sending data to external services
- Integration platform (Zapier, Workato, etc.) connections
- Custom script connections to third-party APIs
Data Flow Mapping
For each sanctioned SaaS vendor, document the complete data flow:
Data Flow Template:
Summit Cloud Partners Internal Systems
│
├─► [SaaS Application Name]
│ │
│ ├─ Integration: [SSO/API/Manual Upload/Browser Plugin]
│ ├─ Authentication: [SAML SSO / OAuth 2.0 / Username-Password]
│ ├─ Encryption in transit: [TLS version]
│ ├─ Data categories sent: [list]
│ ├─ Data categories received: [list]
│ ├─ Data categories stored by vendor: [list]
│ ├─ Vendor processing locations: [locations]
│ ├─ Vendor sub-processors: [per sub-processor register]
│ ├─ Data retention at vendor: [period]
│ └─ Data deletion capability: [Yes/No — method]
│
└─► [Next SaaS Application]
Inventory Reconciliation
Quarterly Reconciliation Process
| Step | Activity | Responsible |
|---|---|---|
| 1 | Extract current CASB discovery report | InfoSec |
| 2 | Extract current sanctioned vendor list | Privacy Team |
| 3 | Compare: identify new unsanctioned applications | Privacy Team |
| 4 | Compare: identify sanctioned apps no longer in use | Privacy Team |
| 5 | Verify DPA status for all sanctioned vendors | Privacy Team |
| 6 | Check contract expiry dates (90-day lookahead) | Legal/Procurement |
| 7 | Update inventory records | Privacy Team |
| 8 | Report to DPO | Privacy Team Lead |
Reconciliation Outcomes
| Finding | Action |
|---|---|
| New unsanctioned SaaS discovered | Initiate shadow IT remediation workflow |
| Sanctioned SaaS no longer in use | Initiate vendor termination data workflow |
| DPA expired or missing | Expedite DPA execution or service suspension |
| Contract approaching expiry | Trigger renewal privacy review |
| Data processing scope change detected | Initiate DPA amendment review |
Contract Status Tracking
| Status | Definition | Action Required |
|---|---|---|
| Active — Compliant | Contract active, DPA executed, privacy review current | Standard monitoring |
| Active — DPA Pending | Contract active, DPA in negotiation | Expedite DPA; restrict data sharing if > 30 days |
| Active — Review Overdue | Contract active, privacy review past due | Schedule immediate review |
| Expiring (< 90 days) | Contract approaching expiry | Initiate renewal assessment |
| Expired | Contract term ended | Initiate termination data workflow |
| Suspended | Service suspended pending privacy issue resolution | Track resolution |
| Terminated | Contract terminated, data return/deletion in progress | Track deletion certification |
Key Regulatory References
- GDPR Article 30(1)(d) — Controller ROPA must include categories of recipients (processors)
- GDPR Article 28(1) — Use only processors with sufficient guarantees
- GDPR Article 5(2) — Accountability principle — must document all processing relationships
- GDPR Article 24 — Controller responsibility for demonstrating compliance
- EDPB Guidelines 07/2020 — Controller knowledge of processing operations
- EDPB Guidelines 04/2019 — Data Protection by Design and by Default (privacy in procurement)
Sub-Processor Management
Overview
GDPR Article 28(2) establishes that a processor shall not engage another processor (sub-processor) without prior specific or general written authorisation of the controller. Where general authorisation is granted, the processor must inform the controller of any intended changes concerning the addition or replacement of sub-processors, giving the controller the opportunity to object. This creates an ongoing management obligation that extends through the entire processing chain.
The EDPB Guidelines 07/2020 (paragraph 93) emphasize that the controller's Article 28(1) due diligence obligation extends to oversight of sub-processor arrangements, and that the processor remains fully liable for the sub-processor's compliance.
At Summit Cloud Partners, the Sub-Processor Management Program ensures visibility and control over the entire processing chain for all vendor relationships involving personal data.
Authorization Models
Model A: Prior Specific Authorization
Under this model, the controller individually approves each sub-processor before engagement.
When to Use:
- High-risk processing (special category data, large-scale processing, cross-border transfers)
- Processing involving sensitive industries (healthcare, financial services)
- When the controller requires direct assessment of each sub-processor
Process:
| Step | Action | Timeline |
|---|---|---|
| 1 | Processor identifies need for new sub-processor | — |
| 2 | Processor submits sub-processor details to controller | Pre-engagement |
| 3 | Controller conducts due diligence on proposed sub-processor | 15 business days |
| 4 | Controller issues written approval or rejection | 5 business days |
| 5 | If approved, processor executes sub-processor DPA | Before processing begins |
| 6 | Processor provides controller with confirmation of sub-processor DPA execution | 5 business days |
Model B: General Written Authorization with Notification
Under this model, the controller grants blanket authorization for sub-processing, subject to a notification and objection mechanism.
When to Use:
- Standard-risk processing
- SaaS vendors with dynamic infrastructure providers
- When specific authorization would be operationally impractical
Process:
| Step | Action | Timeline |
|---|---|---|
| 1 | Processor notifies controller of intended sub-processor change | 30 days before engagement |
| 2 | Notification includes: name, location, function, data access scope | With notification |
| 3 | Controller evaluates notification and exercises objection right if needed | Within 14 days |
| 4 | If no objection, processor may engage sub-processor | After objection period expires |
| 5 | If objection raised, parties negotiate resolution | Within 30 days |
| 6 | If unresolved, either party may terminate affected services | Per DPA terms |
Notification Requirements
The EDPB has clarified that the notification mechanism must be genuine and effective — a mere listing on a website that the controller must monitor does not satisfy Article 28(2) without an active notification mechanism.
Required Notification Content:
| Field | Description | Example |
|---|---|---|
| Sub-processor legal name | Full legal entity name | "Datastream Analytics Inc." |
| Jurisdiction | Country of establishment | "United States (Delaware)" |
| Processing location | Where personal data will be processed | "AWS us-east-1, Virginia, USA" |
| Processing function | What the sub-processor will do | "Real-time event processing and aggregation" |
| Data access scope | What personal data the sub-processor accesses | "Pseudonymized usage events, IP addresses" |
| Engagement date | Proposed start date | "2026-05-01" |
| Transfer mechanism | If outside EEA, the legal transfer basis | "EU-US Data Privacy Framework certification" |
| Security certifications | Relevant certifications held | "SOC 2 Type II, ISO 27001" |
Notification Channels:
- Email notification to designated controller privacy contact
- Supplement with web-based sub-processor register (not a replacement for active notification)
- Calendar integration for objection deadline tracking
Objection Mechanism
The controller's right to object must be genuine per EDPB Guidelines 07/2020 (paragraph 115). The DPA must specify:
- Objection grounds: Reasonable data protection concerns (not arbitrary)
- Objection period: Minimum 14 calendar days from notification receipt (Summit Cloud Partners standard: 30 days)
- Objection format: Written notice to processor's designated privacy contact
- Resolution process: Good-faith negotiation within defined timeframe
- Escalation: If unresolved, termination right for affected services without penalty
Objection Decision Matrix:
| Concern | Action | Escalation |
|---|---|---|
| Sub-processor in jurisdiction with inadequate protection and no valid transfer mechanism | Object — require alternative sub-processor or supplementary measures | DPO review |
| Sub-processor lacks adequate security certifications | Object — request vendor provide evidence of equivalent controls | Privacy Team review |
| Sub-processor has history of data breaches | Object — require enhanced contractual safeguards or alternative | DPO review |
| Sub-processor change is administrative (name change, corporate restructure) | No objection — acknowledge notification | Privacy Team acknowledgment |
| Sub-processor adds processing location within EEA | Evaluate — generally no objection if controls equivalent | Privacy Team review |
Flow-Down Obligations
Article 28(4) requires the processor to impose on each sub-processor, by contract, the same data protection obligations as in the controller-processor DPA. The CJEU has not yet directly interpreted the meaning of "same" obligations, but the EDPB position is that they must be materially equivalent.
Flow-Down Checklist:
| Obligation | Controller → Processor DPA | Processor → Sub-Processor DPA |
|---|---|---|
| Process only on documented instructions | Article 28(3)(a) | Must mirror |
| Confidentiality obligations | Article 28(3)(b) | Must mirror |
| Security measures (Art. 32) | Article 28(3)(c) | Must mirror or exceed |
| Further sub-processing restrictions | Article 28(3)(d) | Must cascade |
| DSR assistance | Article 28(3)(e) | Must mirror |
| Compliance assistance (Art. 32-36) | Article 28(3)(f) | Must mirror |
| Deletion/return on termination | Article 28(3)(g) | Must mirror |
| Audit rights | Article 28(3)(h) | Must provide controller with audit path |
| Breach notification | Article 33(2) | Must cascade with equivalent or shorter timeframe |
Key Consideration — Audit Rights Chain:
The controller must ultimately be able to audit the sub-processor. This can be achieved through:
- Direct audit rights over sub-processor (contractually passed through)
- Processor audits sub-processor on controller's behalf and shares results
- Sub-processor provides independent third-party audit reports (SOC 2, ISO 27001)
Sub-Processor Register
Summit Cloud Partners maintains a centralized sub-processor register for all vendor relationships.
Register Fields:
| Field | Description |
|---|---|
| Primary processor | Vendor with direct DPA |
| Sub-processor name | Legal entity name |
| Sub-processor location | Country and specific processing location |
| Processing function | What the sub-processor does |
| Data access scope | Categories of personal data accessed |
| Authorization type | Specific or general authorization |
| Authorization date | Date of approval |
| DPA status | Sub-processor DPA executed / pending |
| Transfer mechanism | If applicable — SCC, adequacy, DPF |
| Certifications | Current certifications |
| Last review date | Most recent assessment |
| Risk classification | High / Standard / Low |
Monitoring and Compliance
Ongoing Monitoring Activities
- Quarterly sub-processor list reconciliation: Compare processor-provided lists against register
- Certification tracking: Monitor sub-processor certification expiry dates
- Change notification tracking: Verify all sub-processor changes were properly notified
- Annual flow-down verification: Sample sub-processor DPAs to verify equivalent terms
Key Performance Indicators
| KPI | Target | Measurement |
|---|---|---|
| Sub-processor notification compliance | 100% of changes notified before engagement | Quarterly audit |
| Objection response time | 100% within 14 calendar days | Continuous |
| Flow-down DPA coverage | 100% of sub-processors have executed DPAs | Quarterly audit |
| Sub-processor register accuracy | 100% match with processor-provided lists | Quarterly reconciliation |
Key Regulatory References
- GDPR Article 28(2) — Sub-processor authorization requirements
- GDPR Article 28(3)(d) — Sub-processor conditions in DPA
- GDPR Article 28(4) — Flow-down obligations to sub-processors
- EDPB Guidelines 07/2020 — Controller and processor concepts (paragraphs 93, 115)
- Commission Implementing Decision (EU) 2021/915 — SCC Clause 7.7 on sub-processing
- CJEU C-311/18 (Schrems II) — Transfer assessment obligations extending to sub-processor chain
Vendor Breach Notification Cascade
Overview
GDPR Article 33(2) requires that a processor notify the controller "without undue delay after becoming aware of a personal data breach." This obligation creates a notification cascade: the processor must notify the controller promptly, enabling the controller to assess and notify the supervisory authority within 72 hours per Article 33(1), and to notify affected data subjects per Article 34 where there is a high risk to their rights and freedoms.
The EDPB Guidelines 9/2022 on personal data breach notification emphasize that "without undue delay" for processor-to-controller notification should be interpreted strictly — the processor should notify as soon as it has established that a breach has occurred, even if full details are not yet available. DPA-specific timeframes (e.g., 24 hours) may be contractually imposed.
At Summit Cloud Partners, the Vendor Breach Notification Cascade Protocol ensures rapid, coordinated response when a vendor reports a personal data breach.
Notification Chain
Required Notifications and Timeframes
BREACH OCCURS AT VENDOR (PROCESSOR)
│
├─► T+0: Vendor detects breach
│
├─► T+[DPA timeframe]: Vendor notifies Summit Cloud Partners
│ (DPA standard: within 24 hours of becoming aware)
│ Required content per DPA:
│ ├─ Nature of the breach
│ ├─ Categories and approximate number of data subjects
│ ├─ Categories and approximate number of records
│ ├─ DPO/contact point name and details
│ ├─ Description of likely consequences
│ └─ Measures taken or proposed
│
├─► T+0 to T+72h (from controller awareness): Summit Cloud Partners
│ assesses and decides on supervisory authority notification
│ (Article 33(1): within 72 hours, unless unlikely to result
│ in risk to data subjects)
│
├─► If high risk to data subjects: Summit Cloud Partners notifies
│ affected data subjects per Article 34
│
└─► If sub-processors involved: Vendor ensures sub-processor
cascade notification (sub-processor → processor → controller)
Timeframe Requirements
| Notification | GDPR Requirement | Summit Cloud Partners DPA Standard |
|---|---|---|
| Processor → Controller | "Without undue delay" (Art. 33(2)) | Within 24 hours of becoming aware |
| Controller → Supervisory Authority | Within 72 hours (Art. 33(1)) | Within 72 hours |
| Controller → Data Subjects | "Without undue delay" (Art. 34(1)) | As soon as practicable after SA notification |
| Sub-processor → Processor | Per sub-processor DPA | Within 12 hours of becoming aware |
Cascade Response Protocol
Phase 1: Initial Notification Receipt (T+0 to T+2 hours)
Upon receiving breach notification from vendor:
| Step | Action | Responsible | Timeframe |
|---|---|---|---|
| 1.1 | Log notification in breach register | Privacy Team on-call | Immediate |
| 1.2 | Verify notification came from authorized vendor contact | Privacy Team | 15 minutes |
| 1.3 | Acknowledge receipt to vendor | Privacy Team | 30 minutes |
| 1.4 | Alert Summit Cloud Partners Breach Response Team | Privacy Team | 30 minutes |
| 1.5 | Classify initial severity | Breach Response Team Lead | 1 hour |
| 1.6 | Activate appropriate response level | Breach Response Team Lead | 1 hour |
Severity Classification:
| Level | Criteria | Response Level |
|---|---|---|
| Critical | Special category data exposed; > 10,000 data subjects; criminal access confirmed | Full incident response — all hands |
| High | Sensitive data exposed; 1,000-10,000 data subjects; active threat | Expanded response team |
| Medium | Standard personal data exposed; < 1,000 data subjects; contained | Core response team |
| Low | Limited exposure; pseudonymized data; no evidence of access | Privacy Team + InfoSec lead |
Phase 2: Assessment and Investigation (T+2 to T+24 hours)
| Step | Action | Responsible |
|---|---|---|
| 2.1 | Request detailed incident report from vendor | Privacy Team |
| 2.2 | Identify affected Summit Cloud Partners data and data subjects | Privacy Team + IT |
| 2.3 | Assess whether breach is "likely to result in a risk" (Art. 33(1) threshold) | DPO |
| 2.4 | Assess whether breach results in "high risk" (Art. 34(1) threshold) | DPO |
| 2.5 | Coordinate with vendor on containment confirmation | InfoSec Team |
| 2.6 | Determine if other controllers are affected (multi-tenant breach) | Privacy Team |
| 2.7 | Engage legal counsel if liability implications exist | Legal Team |
| 2.8 | Draft preliminary supervisory authority notification (if threshold met) | DPO + Legal |
Vendor Information Requests:
| Information Required | Purpose |
|---|---|
| Root cause analysis (even preliminary) | Understand attack vector and likelihood of ongoing risk |
| Exact data categories compromised | Assess risk to data subjects |
| Exact data subject count or best estimate | Determine notification scope |
| Timeline: when breach occurred, when detected, when contained | Assess detection capability |
| Containment measures implemented | Verify threat neutralized |
| Evidence of data exfiltration (yes/confirmed no/unknown) | Critical for risk assessment |
| Impact on other clients (for multi-tenant breach) | Coordination requirement |
| Forensic investigation status and expected completion | Planning input |
Phase 3: Regulatory Notification Decision (T+24 to T+48 hours)
| Decision | Criteria | Action |
|---|---|---|
| Notify SA | Breach likely to result in risk to data subjects | File notification within 72 hours of awareness |
| Do not notify SA | Breach unlikely to result in risk (documented assessment) | Document decision and rationale; retain in breach register |
| Notify in phases | Cannot provide full details within 72 hours | File initial notification within 72 hours; provide updates as available |
Article 33(3) Notification Content:
| Required Element | Description |
|---|---|
| (a) | Nature of the breach including categories and approximate number of data subjects and records |
| (b) | Name and contact details of DPO or other contact point |
| (c) | Likely consequences of the breach |
| (d) | Measures taken or proposed to address the breach and mitigate effects |
Phase 4: Data Subject Notification (if required)
Article 34(1) requires notification to data subjects when the breach "is likely to result in a high risk to the rights and freedoms of natural persons."
Exemptions (Article 34(3)):
- Controller has applied encryption or other measures rendering data unintelligible
- Controller has taken subsequent measures ensuring high risk is no longer likely
- It would involve disproportionate effort (in which case, public communication required)
Notification Content:
- Nature of the breach in clear, plain language
- DPO/contact point name and details
- Likely consequences
- Measures taken and recommended actions for data subjects
Phase 5: Coordinated Response and Remediation
| Activity | Responsible | Timeline |
|---|---|---|
| Monitor vendor's ongoing investigation | Privacy Team | Ongoing |
| Request and review vendor's root cause analysis | Privacy Team + InfoSec | Within 30 days |
| Assess vendor's remediation plan | Privacy Team + InfoSec | Within 30 days |
| Verify remediation implementation | InfoSec | Within 60 days |
| Update vendor risk score | Privacy Team | Immediate |
| Evaluate contractual remedies | Legal Team | Within 30 days |
| Conduct lessons-learned review | Breach Response Team | Within 90 days |
Liability Allocation
DPA Liability Provisions
The DPA should address breach-related liability:
| Provision | Description |
|---|---|
| Processor indemnification | Processor indemnifies controller for losses caused by processor breach (including fines to the extent legally permissible) |
| Cooperation obligation | Processor must cooperate fully with controller's investigation and regulatory notifications |
| Forensic costs | Allocation of forensic investigation costs |
| Notification costs | Allocation of data subject notification costs |
| Credit monitoring | Allocation of credit monitoring / identity protection costs for affected data subjects |
| Regulatory engagement | Processor must participate in regulatory inquiries |
| Limitation of liability | Carve-out for data protection breaches from general liability caps (where negotiable) |
GDPR Liability Framework
- Article 82(1): Any person who has suffered material or non-material damage as a result of GDPR infringement has the right to compensation from the controller or processor.
- Article 82(2): A processor is liable only where it has not complied with processor-specific GDPR obligations or has acted outside or contrary to controller instructions.
- Article 82(3): A controller or processor is exempt from liability if it can prove it is not responsible for the event giving rise to the damage.
- Article 82(4): Where multiple controllers or processors are involved, each is liable for the entirety of the damage — with contribution rights against co-liable parties.
Multi-Vendor Breach Coordination
When a breach at a sub-processor or infrastructure provider affects multiple processors and controllers:
| Role | Responsibilities |
|---|---|
| Sub-processor | Notify all affected processors; provide consistent information |
| Processor (Vendor) | Notify all affected controllers; coordinate information flow |
| Controller (Summit Cloud Partners) | Assess own impact; make own regulatory notification decisions |
| Lead Supervisory Authority | May coordinate cross-border notifications if multiple EU/EEA controllers affected |
Key Regulatory References
- GDPR Article 33(1) — Controller notification to supervisory authority within 72 hours
- GDPR Article 33(2) — Processor notification to controller "without undue delay"
- GDPR Article 33(3) — Content of supervisory authority notification
- GDPR Article 34 — Communication of breach to data subjects
- GDPR Article 82 — Right to compensation and liability
- EDPB Guidelines 9/2022 — Personal data breach notification under GDPR
- EDPB Guidelines 01/2021 — Examples regarding data breach notification
Vendor Certification Acceptance Criteria
Overview
GDPR Article 42 establishes a framework for data protection certification mechanisms, and Article 28(5) notes that a processor's adherence to an approved certification mechanism may be used as an element to demonstrate sufficient guarantees. The EDPB Guidelines 07/2020 (paragraph 86) confirm that certifications may serve as indicators of processor reliability, though they do not discharge the controller's obligation to conduct its own assessment.
Vendor certifications and attestations provide structured evidence of control implementation, but their value depends on scope coverage, certification body credibility, recency, and relevance to the specific processing relationship. Summit Cloud Partners maintains a Certification Acceptance Framework that defines which certifications are recognized, how they are evaluated, and what supplementary measures are needed when certification coverage has gaps.
Recognized Certification Frameworks
Tier A: Strong Privacy Certifications
Certifications specifically designed for privacy/data protection management, independently audited.
ISO/IEC 27701:2019 — Privacy Information Management System (PIMS)
| Aspect | Detail |
|---|---|
| Standard | Extension to ISO 27001/27002 for PII management |
| Scope | PII controller (Annex A) and PII processor (Annex B) controls |
| Certification body | Accredited ISO certification bodies |
| Audit type | Third-party certification audit (Stage 1 + Stage 2) |
| Validity | 3-year cycle with annual surveillance audits |
| GDPR relevance | High — maps directly to GDPR requirements per Annex D |
| Acceptance criteria | Certificate scope must cover processing services provided to Summit |
| Verification | Check accreditation body registry; verify scope statement |
| Supplementation needed | Verify that Annex B (processor) controls are in scope; if only Annex A (controller), supplementary processor assessment required |
GDPR Certification per Article 42
| Aspect | Detail |
|---|---|
| Standard | Certification per criteria approved by supervisory authority or EDPB |
| Certification body | Accredited per Article 43 by national accreditation body and supervisory authority |
| GDPR relevance | Maximum — specifically designed for GDPR compliance demonstration |
| Acceptance criteria | Certificate issued by Article 43 accredited body; scope covers processing |
| Current status | Very few Article 42 certifications currently available (as of March 2026) |
| Supplementation needed | Minimal if scope covers all processing activities |
Tier B: Strong Security Certifications with Privacy Elements
Certifications primarily security-focused but including privacy-relevant controls.
SOC 2 Type II with Privacy Trust Services Criterion
| Aspect | Detail |
|---|---|
| Standard | AICPA Trust Services Criteria — Privacy criterion |
| Scope | Notice, choice, collection, use/retention/disposal, access, disclosure, security, quality, monitoring |
| Audit type | Independent CPA examination over minimum 6-month period |
| GDPR relevance | Moderate-High — covers many Article 28/32 requirements but US-centric |
| Acceptance criteria | Type II (not Type I); Privacy criterion included; no qualified opinions; scope covers relevant services |
| Verification | Request full report under NDA; review scope, findings, exceptions |
| Supplementation needed | GDPR-specific gap assessment required: cross-border transfer controls, DPA-specific obligations, sub-processor cascade |
SOC 2 Type II (Security Criterion Only)
| Aspect | Detail |
|---|---|
| Acceptance criteria | Type II; no qualified opinions; scope covers relevant services |
| GDPR relevance | Moderate — covers Article 32 security measures |
| Supplementation needed | Full privacy assessment required for non-security GDPR obligations |
ISO/IEC 27001:2022 — Information Security Management System
| Aspect | Detail |
|---|---|
| Acceptance criteria | Current version (2022 preferred); scope covers processing services; accredited certification body |
| GDPR relevance | Moderate — strong for Article 32 security; does not address privacy-specific requirements |
| Supplementation needed | Privacy gap assessment covering Art. 28(3) obligations, DSR assistance, breach notification, data handling |
Tier C: Domain-Specific Certifications
ISO/IEC 27018:2019 — Cloud Privacy
| Aspect | Detail |
|---|---|
| Scope | Cloud-specific PII protection controls |
| Acceptance | Relevant only for cloud service providers; supplements ISO 27001 |
| Supplementation | Must be combined with ISO 27001; does not stand alone |
CSA STAR Level 2 — Cloud Security
| Aspect | Detail |
|---|---|
| Scope | Cloud Controls Matrix (CCM) third-party audit |
| Acceptance | Level 2 (third-party audit) required; Level 1 (self-assessment) insufficient as standalone |
| Supplementation | Cloud security focus; privacy gap assessment required |
APEC Cross-Border Privacy Rules (CBPR) System
| Aspect | Detail |
|---|---|
| Scope | Asia-Pacific cross-border data transfer framework |
| Acceptance | Recognized for APEC economy vendors; does not substitute for GDPR compliance |
| GDPR relevance | Limited — different legal framework; may indicate privacy program maturity |
| Supplementation | Full GDPR compliance assessment still required |
EU Cloud Code of Conduct (SCOPE Europe)
| Aspect | Detail |
|---|---|
| Standard | GDPR Article 40 approved code of conduct for cloud services |
| Scope | Cloud service provider GDPR compliance |
| Acceptance | Approved by Belgian DPA as monitoring body (2021) |
| GDPR relevance | High — specifically mapped to GDPR obligations |
| Supplementation | Minimal for in-scope cloud processing; verify monitoring body oversight |
Tier D: Self-Assessments and Basic Certifications
| Certification | Acceptance Level |
|---|---|
| CSA STAR Level 1 (self-assessment) | Accepted as supplementary evidence only; not standalone |
| Vendor privacy policy / self-declaration | Not accepted as certification; supplementary only |
| HITRUST CSF | Accepted for healthcare contexts; GDPR gap assessment required |
| Cyber Essentials (UK) | Basic security only; full assessment required |
Certification Equivalence Matrix
Maps certification coverage against GDPR Article 28 requirements:
| GDPR Requirement | ISO 27701 | SOC 2 Privacy | SOC 2 Security | ISO 27001 | ISO 27018 | Art. 42 Cert |
|---|---|---|---|---|---|---|
| Art. 28(3)(a) Documented instructions | Full | Partial | None | None | Full | Full |
| Art. 28(3)(b) Confidentiality | Full | Full | Partial | Full | Full | Full |
| Art. 28(3)(c) Security (Art. 32) | Full | Full | Full | Full | Full | Full |
| Art. 28(3)(d) Sub-processor mgmt | Full | Partial | None | Partial | Full | Full |
| Art. 28(3)(e) DSR assistance | Full | Partial | None | None | Partial | Full |
| Art. 28(3)(f) Compliance assistance | Full | Partial | None | None | None | Full |
| Art. 28(3)(g) Deletion/return | Full | Full | None | Partial | Full | Full |
| Art. 28(3)(h) Audit rights | Full | Partial | None | Partial | Full | Full |
| Art. 33(2) Breach notification | Full | Full | Partial | Partial | Partial | Full |
| Ch. V International transfers | Partial | None | None | None | None | Full |
Legend: Full = requirement addressed, Partial = partially addressed, None = not addressed
Gap Supplementation Requirements
When a vendor holds certifications that do not fully cover GDPR requirements, Summit Cloud Partners requires supplementary evidence for uncovered obligations:
| Gap | Supplementation Method |
|---|---|
| DSR assistance capability | Vendor provides DSR handling procedure documentation and SLA commitments |
| Sub-processor management | Vendor provides sub-processor list, notification mechanism, and flow-down DPA sample |
| Breach notification process | Vendor provides incident response plan with notification timeframes |
| International transfer controls | Vendor provides Transfer Impact Assessment and supplementary measures documentation |
| Deletion/return capabilities | Vendor demonstrates deletion procedure and provides sample deletion certificate |
| Audit facilitation | DPA audit rights clause verified; vendor confirms practical audit access |
Certification Verification Process
| Step | Activity | Evidence |
|---|---|---|
| 1 | Obtain copy of certificate and audit report | PDF certificate; SOC 2 report under NDA |
| 2 | Verify certification body accreditation | Check national accreditation body registry |
| 3 | Verify certificate validity (not expired) | Certificate dates; annual surveillance confirmation |
| 4 | Verify scope covers relevant services | Scope statement includes services provided to Summit |
| 5 | Review exceptions or qualified opinions (SOC 2) | No material exceptions affecting Summit data |
| 6 | Identify gaps per equivalence matrix | Document uncovered requirements |
| 7 | Request supplementary evidence for gaps | Per gap supplementation table |
| 8 | Document acceptance decision | Record in vendor assessment file |
Key Regulatory References
- GDPR Article 42 — Data protection certification mechanisms
- GDPR Article 43 — Certification bodies
- GDPR Article 40 — Codes of conduct
- GDPR Article 28(5) — Adherence to certifications as element of sufficient guarantees
- EDPB Guidelines 07/2020 — Paragraph 86 on certifications as sufficiency indicators
- EDPB Guidelines 1/2018 — Certification and identifying certification criteria per Article 42
- ISO/IEC 27701:2019 — Privacy information management system
- AICPA Trust Services Criteria — Privacy criterion (2017 revision with 2022 updates)
- APEC Cross-Border Privacy Rules System — Policies, Rules, and Guidelines
- EU Cloud Code of Conduct — SCOPE Europe (approved 2021)
Vendor Privacy Monitoring Program
Overview
GDPR Article 28(1) imposes a continuing obligation on controllers to ensure that processors maintain sufficient guarantees. This is not a one-time assessment — the EDPB Guidelines 07/2020 (paragraph 87) explicitly state that the controller's assessment obligation is ongoing. The Vendor Privacy Monitoring Program at Summit Cloud Partners implements continuous oversight proportionate to the risk each vendor presents.
Monitoring Framework
Tier-Based Monitoring Schedule
| Activity | Tier 1 (High Risk) | Tier 2 (Standard) | Tier 3 (Low Risk) |
|---|---|---|---|
| Full reassessment | Annual | Biennial | Triennial |
| Privacy audit | Annual (Type 2/3) | Annual (Type 1) | Biennial (Type 1) |
| Sub-processor list verification | Quarterly | Semi-annual | Annual |
| DPA compliance review | Annual | Biennial | Triennial |
| Risk score recalculation | Semi-annual | Annual | Biennial |
| Certification status check | Quarterly | Semi-annual | Annual |
| Breach monitoring | Continuous | Continuous | Monthly check |
| Contract renewal privacy gate | 120 days before | 90 days before | 90 days before |
Continuous Monitoring Signals
Automated or semi-automated monitoring sources that provide ongoing visibility:
| Signal Source | What It Monitors | Frequency | Alert Trigger |
|---|---|---|---|
| Vendor risk intelligence platform | Public breach disclosures, enforcement actions, news | Daily | New incident involving a monitored vendor |
| Certification monitoring | ISO/SOC certificate validity and scope changes | Monthly | Certificate approaching expiry (60 days) |
| CASB/DLP | Data flows to vendor — volume and category anomalies | Continuous | Data transfer exceeding baseline by 200% |
| DNS/network monitoring | Connectivity patterns to vendor endpoints | Continuous | New endpoints, geographic changes |
| Vendor security scorecard | External security posture assessment | Monthly | Score drops below threshold |
| Regulatory database monitoring | New enforcement decisions involving vendor | Weekly | New published enforcement action |
| Sub-processor registry monitoring | Vendor-published sub-processor list changes | Weekly | New or changed sub-processor detected |
Annual Reassessment Process
For each vendor due for reassessment:
Phase 1: Preparation (30 days before reassessment)
| Activity | Responsible |
|---|---|
| Pull current vendor profile and risk score | Privacy Team |
| Review monitoring signals from prior period | Privacy Team |
| Compile open audit findings and remediation status | Privacy Team |
| Identify changes since last assessment | Privacy Team |
| Send reassessment questionnaire to vendor | Privacy Team |
Phase 2: Assessment (Assessment month)
| Activity | Responsible |
|---|---|
| Review vendor's updated questionnaire responses | Privacy Team |
| Verify current certifications | Privacy Team |
| Review sub-processor list for changes | Privacy Team |
| Assess any processing scope changes | Privacy Team |
| Conduct audit (per tier schedule) | Audit Team |
| Recalculate risk score | Privacy Team |
Phase 3: Decision and Documentation
| Activity | Responsible |
|---|---|
| Update sufficiency determination | DPO |
| Update vendor risk tier (if changed) | Privacy Team Lead |
| Update monitoring schedule | Privacy Team |
| Communicate outcomes to business unit | Privacy Team |
| File reassessment documentation | Privacy Team |
Contract Renewal Privacy Gate
When a vendor contract approaches renewal, a privacy gate ensures continued compliance:
| Timing | Activity |
|---|---|
| 120 days before renewal (Tier 1) / 90 days (Tier 2/3) | Privacy Team notified of upcoming renewal |
| 90 days before renewal | Review current privacy compliance status |
| 60 days before renewal | Complete any required reassessment |
| 30 days before renewal | Issue renewal privacy recommendation (Renew / Renew with conditions / Do not renew) |
| At renewal | Execute any required DPA amendments |
Renewal Privacy Decision Matrix:
| Compliance Status | Audit Status | Risk Trend | Recommendation |
|---|---|---|---|
| Fully compliant | Clean audit | Stable/improving | Renew |
| Minor gaps | Minor findings only | Stable | Renew with conditions |
| Material gaps | Major findings pending | Deteriorating | Renew with conditions + accelerated audit |
| Significant non-compliance | Critical findings open | Deteriorating | Do not renew (initiate termination planning) |
Performance Metrics and KPIs
Vendor Privacy Program KPIs
| KPI | Target | Measurement | Frequency |
|---|---|---|---|
| DPA coverage rate | 100% of data-processing vendors | Active DPAs / vendors processing personal data | Quarterly |
| Reassessment completion rate | 100% on schedule | Completed on time / due | Quarterly |
| Audit completion rate | 100% per tier schedule | Audits completed / audits due | Annual |
| Average vendor risk score | Trending downward | Mean weighted score across all vendors | Semi-annual |
| Open audit findings (Critical) | 0 past deadline | Count of overdue Critical findings | Monthly |
| Open audit findings (Major) | 0 past deadline | Count of overdue Major findings | Monthly |
| Sub-processor notification compliance | 100% | Changes notified before engagement / total changes | Quarterly |
| Mean time to acknowledge breach | < 2 hours | Average time from vendor notification to acknowledgment | Per incident |
| Deletion certification rate | 100% within DPA timeline | Certifications received on time / terminations | Annual |
| Shadow IT detection-to-remediation | < 30 days | Average days from detection to sanctioned/blocked | Quarterly |
Vendor Privacy Scorecard
Each vendor receives a quarterly privacy scorecard:
| Dimension | Weight | Score (1-5) | Trend |
|---|---|---|---|
| DPA compliance | 25% | [X] | [Up/Down/Stable] |
| Audit performance | 20% | [X] | [Up/Down/Stable] |
| Breach history (rolling 12 months) | 15% | [X] | [Up/Down/Stable] |
| Sub-processor management compliance | 15% | [X] | [Up/Down/Stable] |
| Certification currency | 15% | [X] | [Up/Down/Stable] |
| Cooperation and responsiveness | 10% | [X] | [Up/Down/Stable] |
| Weighted Total | 100% | [X.X] |
Governance Reporting
Monthly Privacy Team Report
| Section | Content |
|---|---|
| Vendor count and tier distribution | Current state |
| New vendors onboarded | Privacy review outcomes |
| Vendors terminated | Deletion certification status |
| Open audit findings by severity | Remediation timeline |
| Monitoring alerts actioned | Signal source and resolution |
| Shadow IT detections | Discovery and remediation |
| Upcoming deadlines | Reassessments, renewals, audits due |
Quarterly DPO Report
| Section | Content |
|---|---|
| Program KPIs vs targets | Dashboard with trend analysis |
| Risk tier changes | Escalations and de-escalations with rationale |
| Significant vendor events | Breaches, enforcement, certification changes |
| Regulatory developments | New guidance affecting vendor management |
| Recommendations | Program improvements, resource needs |
Key Regulatory References
- GDPR Article 28(1) — Continuing obligation to verify processor sufficiency
- GDPR Article 5(2) — Accountability principle requires demonstrated ongoing compliance
- GDPR Article 24 — Controller responsibility for appropriate measures
- EDPB Guidelines 07/2020 — Ongoing assessment obligation (paragraph 87)
- ISO 27001:2022 — A.5.19 Information security in supplier relationships (monitoring)
- NIST CSF 2.0 — ID.SC Supply chain risk management
Vendor Privacy Audit
Overview
GDPR Article 28(3)(h) requires that the processor "make available to the controller all information necessary to demonstrate compliance with the obligations laid down in Article 28, and allow for and contribute to audits, including inspections, conducted by the controller or another auditor mandated by the controller." This audit right is a cornerstone of the controller's accountability obligations and must be exercisable in practice.
The EDPB Guidelines 07/2020 (paragraph 110) emphasize that audit rights must be practical and exercisable, not merely theoretical. Controllers must develop structured audit programs proportionate to the risk of the processing.
At Summit Cloud Partners, the Vendor Privacy Audit Program provides a systematic approach to verifying processor compliance through on-site inspections, remote audits, and documentation reviews.
Audit Types
Type 1: Documentation-Based Audit (Remote)
Suitable for standard-risk vendors with current third-party certifications.
| Aspect | Detail |
|---|---|
| Scope | Review of processor-provided documentation and certifications |
| Duration | 3-5 business days |
| Frequency | Annual |
| Deliverable | Documentation Audit Report |
| Cost allocation | Controller bears own costs |
Evidence Reviewed:
- Current ISO 27001/27701 certificates and audit reports
- SOC 2 Type II report (including management assertions and exceptions)
- DPA compliance self-assessment questionnaire
- Sub-processor register and DPA coverage confirmation
- Incident log summary for audit period
- Training records and confidentiality agreement coverage
- Data subject request handling metrics
Type 2: Remote Technical Audit
Suitable for standard-to-high-risk vendors where on-site access is not practical.
| Aspect | Detail |
|---|---|
| Scope | Remote assessment including technical verification |
| Duration | 5-10 business days |
| Frequency | Annual for high-risk; biennial for standard-risk |
| Deliverable | Remote Audit Report |
| Cost allocation | Per DPA terms (typically split) |
Activities:
- All documentation review activities from Type 1
- Video-conference interviews with vendor privacy and security teams
- Screen-sharing walkthrough of access control configurations
- Review of logging and monitoring dashboards
- Live demonstration of data subject request handling process
- Review of encryption key management procedures
- Penetration test report review (vendor-provided under NDA)
Type 3: On-Site Inspection
Required for high-risk vendors and when triggered by compliance concerns.
| Aspect | Detail |
|---|---|
| Scope | Physical inspection of processing facilities and controls |
| Duration | 1-3 days on-site, plus pre/post work |
| Frequency | As needed; minimum biennial for highest-risk vendors |
| Deliverable | On-Site Inspection Report |
| Cost allocation | Per DPA terms |
Activities:
- All remote audit activities
- Physical security inspection of data processing facilities
- Server room and network infrastructure walkthrough
- Badge access system review and testing
- Clean desk policy verification
- Environmental controls inspection (fire suppression, climate, power)
- Personnel interviews (privacy officer, security team, operations staff)
- Observation of operational procedures (incident response, change management)
Audit Planning
Pre-Audit Activities
60 Days Before Audit:
| Activity | Responsible |
|---|---|
| Select vendors for audit based on risk tier and schedule | Privacy Team |
| Determine audit type (Documentation / Remote / On-Site) | Privacy Team Lead |
| Assign audit team lead and members | Privacy Team Lead |
| Notify vendor of audit intent per DPA notification requirements | Audit Team Lead |
30 Days Before Audit:
| Activity | Responsible |
|---|---|
| Issue formal audit notification letter to vendor | Audit Team Lead |
| Submit document request list to vendor | Audit Team |
| Schedule interview slots (for Type 2 and 3) | Audit Team |
| Book travel and facilities (for Type 3) | Operations |
| Prepare audit checklist customized for vendor's processing | Audit Team |
7 Days Before Audit:
| Activity | Responsible |
|---|---|
| Review vendor-provided documentation | Audit Team |
| Prepare interview question sets | Audit Team |
| Finalize on-site agenda (Type 3) | Audit Team Lead |
| Conduct team briefing | Audit Team Lead |
Audit Checklist
A. DPA Compliance Verification
| # | Check Item | Article | Evidence Required |
|---|---|---|---|
| A1 | Processing limited to documented controller instructions | 28(3)(a) | Processing logs, instruction register |
| A2 | All authorized personnel bound by confidentiality | 28(3)(b) | Signed confidentiality agreements, HR records |
| A3 | Article 32 security measures implemented per DPA Annex II | 28(3)(c) | Security configuration evidence |
| A4 | Sub-processors authorized and DPAs in place | 28(3)(d) | Sub-processor register, executed DPAs |
| A5 | DSR assistance capability demonstrated | 28(3)(e) | DSR handling procedures, response metrics |
| A6 | Compliance assistance provided for Art. 32-36 | 28(3)(f) | DPIA contributions, breach investigation support |
| A7 | Deletion/return capabilities verified | 28(3)(g) | Deletion procedures, test results |
| A8 | Audit information and access provided | 28(3)(h) | Audit cooperation evidence |
B. Technical Controls Verification
| # | Check Item | Evidence Required |
|---|---|---|
| B1 | Encryption at rest implemented per DPA specifications | Key management documentation, configuration screenshots |
| B2 | Encryption in transit per DPA specifications | TLS configuration, certificate management |
| B3 | Access controls configured per principle of least privilege | RBAC configuration, access review records |
| B4 | MFA enabled for all administrative access | MFA enrollment records, policy configuration |
| B5 | Logging enabled and retained per DPA retention period | Log storage configuration, sample logs |
| B6 | Vulnerability scanning performed per schedule | Scan reports, remediation records |
| B7 | Penetration testing performed per schedule | Pen test reports, finding remediation |
| B8 | Backup and recovery procedures tested | DR test results, RPO/RTO metrics |
C. Organizational Controls Verification
| # | Check Item | Evidence Required |
|---|---|---|
| C1 | Privacy training delivered to all relevant staff | Training records with completion dates |
| C2 | Incident response plan documented and tested | IRP document, tabletop exercise records |
| C3 | Change management process followed | Change log, approval records |
| C4 | Physical security controls in place (Type 3 only) | Badge access logs, CCTV coverage, visitor log |
| C5 | Data retention and deletion procedures operational | Retention schedule, deletion logs |
| C6 | Records of processing maintained per Art. 30(2) | ROPA documentation |
D. Breach Notification Readiness
| # | Check Item | Evidence Required |
|---|---|---|
| D1 | Breach detection capabilities operational | SIEM configuration, alert rules |
| D2 | Breach notification procedure documented with DPA-compliant timeframe | IRP with notification section, contact matrix |
| D3 | Breach notification contact details current | Verified contact information |
| D4 | Breach register maintained | Breach log (redacted if necessary) |
Finding Classification
| Severity | Definition | Remediation Timeline | Follow-Up |
|---|---|---|---|
| Critical | Immediate risk to personal data or fundamental DPA violation | Immediate (within 7 days) | Verification audit within 30 days |
| Major | Significant gap in controls or DPA non-compliance | 30 calendar days | Written evidence of remediation |
| Minor | Control weakness not immediately impacting data protection | 90 calendar days | Verified at next scheduled audit |
| Observation | Area for improvement, not a compliance gap | Noted for next assessment | Tracked in audit records |
Examples by Severity:
| Severity | Example |
|---|---|
| Critical | Personal data accessible to unauthorized personnel; no encryption at rest despite DPA requirement |
| Major | Sub-processor engaged without notification; MFA not enforced for administrative access |
| Minor | Privacy training completion at 85% (target 100%); access review 2 weeks overdue |
| Observation | Incident response plan would benefit from more specific processor notification procedures |
Remediation Tracking
All findings above Observation severity enter the remediation tracking system:
| Field | Description |
|---|---|
| Finding ID | Unique identifier |
| Vendor | Processor name |
| Audit date | When finding was identified |
| Severity | Critical / Major / Minor |
| Description | Detailed description of the finding |
| Root cause | Why the gap exists |
| Remediation plan | Vendor's proposed corrective action |
| Deadline | Date by which remediation must be complete |
| Evidence required | What the vendor must provide to close the finding |
| Status | Open / In Progress / Remediated / Verified / Overdue |
| Verification method | How Summit Cloud Partners will verify remediation |
Key Regulatory References
- GDPR Article 28(3)(h) — Audit rights and compliance information
- GDPR Article 5(2) — Accountability principle
- GDPR Article 24 — Responsibility of the controller
- GDPR Article 32 — Security of processing
- EDPB Guidelines 07/2020 — Controller and processor concepts (paragraph 110 on practical audit rights)
- Bavarian DPA (BayLDA) — Processor Audit Guidelines (2022)
- ISO 19011:2018 — Guidelines for auditing management systems
Vendor Privacy Due Diligence
Overview
GDPR Article 28(1) requires controllers to use only processors providing "sufficient guarantees to implement appropriate technical and organisational measures" to meet GDPR requirements and protect data subject rights. This obligation means controllers must conduct thorough privacy due diligence before engaging any vendor that will process personal data. The European Data Protection Board (EDPB) Guidelines 07/2020 on controller and processor concepts reinforce that this assessment must be documented and proportionate to the risk involved.
At Summit Cloud Partners, the Vendor Privacy Due Diligence Program establishes a structured process for evaluating prospective vendors before any personal data processing begins.
Due Diligence Framework
Phase 1: Initial Screening
Before engaging in detailed evaluation, determine whether the vendor will process personal data at all.
Processing Determination Checklist:
| Question | If YES |
|---|---|
| Will the vendor access, store, or transmit personal data? | Proceed to full due diligence |
| Will the vendor host systems containing personal data? | Proceed to full due diligence |
| Will the vendor have logical or physical access to infrastructure holding personal data? | Proceed to full due diligence |
| Is the vendor providing purely non-personal-data services (e.g., office supplies)? | No due diligence required — document determination |
Data Flow Preliminary Analysis:
Map the anticipated data flows before proceeding:
- What categories of personal data will the vendor process?
- How many data subjects are affected (approximate volume)?
- Will special category data (Article 9) be involved?
- Where will processing occur geographically?
- Will the vendor engage sub-processors?
Phase 2: Privacy Risk Questionnaire
Summit Cloud Partners issues a standardized Privacy Risk Questionnaire to all prospective vendors scoring above the initial screening threshold.
Section A — Legal and Governance
| # | Question | Expected Response |
|---|---|---|
| A1 | Does your organization have a designated Data Protection Officer (DPO) or equivalent privacy lead? | Named individual with contact details |
| A2 | In which jurisdictions is your organization established? | List of all establishment countries |
| A3 | What is your GDPR compliance governance structure? | Documented privacy program with assigned responsibilities |
| A4 | Have you been subject to any regulatory enforcement actions, fines, or investigations in the past 5 years? | Disclosure of any actions with remediation status |
| A5 | Do you maintain a Record of Processing Activities per Article 30(2)? | Confirmation with sample structure |
| A6 | What lawful bases do you rely on for your own processing activities? | Documented lawful basis assessment |
| A7 | Do you have a process for conducting Data Protection Impact Assessments per Article 35? | DPIA methodology description |
Section B — Technical Security Controls
| # | Question | Expected Response |
|---|---|---|
| B1 | Describe your encryption approach for data at rest and in transit | AES-256 for at-rest, TLS 1.2+ for in-transit minimum |
| B2 | How do you manage access controls and authentication? | RBAC, MFA, principle of least privilege |
| B3 | Describe your vulnerability management program | Regular scanning, patching cadence, penetration testing |
| B4 | What logging and monitoring controls are in place? | SIEM, access logging, anomaly detection |
| B5 | Describe your incident detection and response capabilities | 24/7 monitoring, documented IRP, mean time to detect |
| B6 | How do you secure development practices? | SDLC, code review, OWASP compliance |
| B7 | What physical security controls protect data processing facilities? | Access controls, CCTV, environmental controls |
Section C — Data Handling Practices
| # | Question | Expected Response |
|---|---|---|
| C1 | How do you segregate client data from other clients? | Logical or physical segregation description |
| C2 | What is your data retention and deletion approach? | Defined retention periods, certified deletion |
| C3 | How do you handle data subject access requests forwarded by controllers? | Process description with SLA commitments |
| C4 | Describe your data backup and recovery procedures | Backup frequency, encryption, tested recovery |
| C5 | Do you process personal data in any country outside the EEA? | List of all processing locations with transfer mechanisms |
| C6 | What is your sub-processor engagement process? | Notification mechanism, assessment requirements |
Section D — Certifications and Attestations
| # | Question | Expected Response |
|---|---|---|
| D1 | Do you hold ISO 27001 certification? | Certificate with scope and certification body |
| D2 | Do you hold ISO 27701 certification? | Certificate with scope |
| D3 | Do you hold SOC 2 Type II attestation? | Report with scope and period |
| D4 | Do you hold any cloud-specific certifications (CSA STAR, ISO 27017/27018)? | Certificate details |
| D5 | Do you adhere to any approved GDPR Code of Conduct per Article 40? | Code of Conduct reference and adherence documentation |
| D6 | Have you obtained any GDPR certification per Article 42? | Certification details |
Phase 3: Technical Controls Assessment
Beyond questionnaire responses, Summit Cloud Partners conducts independent verification of critical controls.
Assessment Methods:
- Documentation Review: Examine vendor security policies, procedures, and architectural documentation
- Certification Verification: Independently verify certification validity with issuing bodies
- Technical Testing: Where contractually permitted, conduct or review penetration test results
- Reference Checks: Contact existing clients of the vendor regarding privacy practices
- Public Record Search: Review breach notification databases, regulatory actions, and news reports
Control Verification Matrix:
| Control Domain | Questionnaire Claim | Verification Method |
|---|---|---|
| Encryption at rest | AES-256 | Review architecture docs, request encryption key management details |
| Encryption in transit | TLS 1.2+ | Technical scan of vendor endpoints |
| Access management | RBAC with MFA | Review IAM policy documentation |
| Incident response | 24/7 SOC | Review SOC 2 Type II report findings |
| Data segregation | Logical separation | Architecture review and documentation |
| Patch management | Monthly cycle | Review vulnerability management reports |
Phase 4: Data Flow Analysis
Document the complete data flow for the proposed processing arrangement.
Data Flow Documentation Requirements:
Data Flow: Summit Cloud Partners → [Vendor Name]
1. Data Categories:
- [List each category of personal data]
- Classification level per category (Public/Internal/Confidential/Restricted)
2. Data Subjects:
- [List each category of data subject]
- Approximate volume per category
3. Transfer Mechanism:
- Method: [API / SFTP / Direct database access / etc.]
- Encryption: [Protocol and strength]
- Authentication: [Method]
4. Processing Locations:
- Primary: [Country, City, Data Center]
- Backup/DR: [Country, City, Data Center]
- Support access: [Countries where staff may access data]
5. Sub-processors:
- [List known sub-processors with location and function]
6. Data Retention:
- Processing retention: [Duration]
- Backup retention: [Duration]
- Post-termination: [Return/deletion timeline]
7. Return Path:
- Data subject requests forwarded via: [mechanism]
- Response SLA: [timeframe]
Phase 5: Sufficiency Decision
The DPO or Privacy Team Lead reviews all collected evidence and issues a documented sufficiency decision.
Sufficiency Decision Criteria:
| Criterion | Weight | Scoring |
|---|---|---|
| Legal governance maturity | 15% | 1-5 scale |
| Technical security controls | 25% | 1-5 scale |
| Data handling practices | 20% | 1-5 scale |
| Certifications held | 15% | 1-5 scale |
| Breach and enforcement history | 10% | 1-5 scale (inverse) |
| Sub-processor management | 10% | 1-5 scale |
| Cross-border transfer safeguards | 5% | 1-5 scale |
Decision Outcomes:
- Approved (weighted score 4.0+): Vendor provides sufficient guarantees. Proceed to DPA negotiation.
- Conditionally Approved (weighted score 3.0–3.9): Vendor requires supplementary measures or contractual safeguards before engagement. Document conditions.
- Rejected (weighted score below 3.0): Vendor does not provide sufficient guarantees. Document reasons. May be reconsidered after vendor remediation.
Documentation Requirements per Article 5(2) Accountability:
The due diligence file must contain:
- Completed Privacy Risk Questionnaire with vendor responses
- Evidence of verification activities performed
- Data flow analysis documentation
- Sufficiency scoring worksheet
- Written decision with rationale
- Approval signature from DPO or designated privacy lead
- Date of assessment and scheduled reassessment date
Ongoing Obligations
Due diligence is not a one-time exercise. Article 28(1) imposes a continuing obligation to ensure processors maintain sufficient guarantees. Summit Cloud Partners conducts:
- Annual Reassessment: Full questionnaire refresh for high-risk vendors, abbreviated for standard risk
- Trigger-Based Review: Reassessment triggered by vendor breach, regulatory action, material service change, or certification lapse
- Continuous Monitoring: Automated alerts on vendor security posture changes via risk monitoring services
Key Regulatory References
- GDPR Article 28(1) — Controller obligation to use processors with sufficient guarantees
- GDPR Article 28(3) — Required DPA provisions
- GDPR Article 5(2) — Accountability principle
- GDPR Article 30(2) — Processor records of processing
- GDPR Article 35 — DPIA requirements
- EDPB Guidelines 07/2020 — Controller and processor concepts under GDPR
- EDPB Recommendations 01/2020 — Supplementary measures for international transfers
Vendor Privacy Risk Scoring
Overview
Effective vendor privacy management requires a risk-based approach that allocates oversight resources proportionate to the privacy risk each vendor presents. GDPR Recital 76 states that risk should be assessed based on "the likelihood and severity" of potential impact on data subjects. The EDPB Guidelines 07/2020 (paragraph 86) indicate that the controller's assessment of processor sufficiency must consider expert knowledge, reliability, and resources — factors that feed directly into risk scoring.
At Summit Cloud Partners, the Vendor Privacy Risk Scoring Model assigns each vendor a quantified risk score based on objective factors, enabling consistent risk tiering, proportionate oversight, and audit prioritization.
Risk Scoring Model
Scoring Dimensions
The model evaluates seven dimensions, each scored on a 1-5 scale where 1 = lowest risk and 5 = highest risk.
Dimension 1: Data Volume (Weight: 15%)
| Score | Criterion | Description |
|---|---|---|
| 1 | < 100 data subjects | Minimal volume processing |
| 2 | 100 – 1,000 data subjects | Low volume |
| 3 | 1,001 – 10,000 data subjects | Moderate volume |
| 4 | 10,001 – 100,000 data subjects | High volume |
| 5 | > 100,000 data subjects | Very high volume |
Dimension 2: Data Sensitivity (Weight: 25%)
| Score | Criterion | Description |
|---|---|---|
| 1 | Pseudonymized non-sensitive data only | Minimal identifiability |
| 2 | Non-sensitive personal data (names, email) | Standard personal data |
| 3 | Behavioral data, location data, financial identifiers | Elevated sensitivity |
| 4 | Government IDs, precise geolocation, communications content | High sensitivity |
| 5 | Special category data (Art. 9) or criminal convictions (Art. 10) | Maximum sensitivity |
Dimension 3: Transfer Locations (Weight: 15%)
| Score | Criterion | Description |
|---|---|---|
| 1 | Processing exclusively within EEA | No transfer risk |
| 2 | Processing in EEA + adequacy decision countries | Minimal transfer risk |
| 3 | Processing includes non-adequate countries with robust SCCs and supplementary measures | Managed transfer risk |
| 4 | Processing in jurisdictions with government surveillance concerns (per EDPB assessments) | Elevated transfer risk |
| 5 | Processing in jurisdictions lacking rule of law / no valid transfer mechanism | Maximum transfer risk |
Dimension 4: Certifications and Attestations (Weight: 15%)
Inverse scoring — higher certifications reduce risk.
| Score | Criterion | Description |
|---|---|---|
| 1 | ISO 27001 + ISO 27701 + SOC 2 Type II + sector-specific cert | Comprehensive certification |
| 2 | ISO 27001 + SOC 2 Type II (or equivalent combination) | Strong certification |
| 3 | ISO 27001 only or SOC 2 Type II only | Moderate certification |
| 4 | Self-assessment or CSA STAR Level 1 only | Limited certification |
| 5 | No recognized certifications or attestations | No certification |
Dimension 5: Breach and Enforcement History (Weight: 10%)
| Score | Criterion | Description |
|---|---|---|
| 1 | No breaches, no enforcement actions in past 5 years | Clean record |
| 2 | Minor incident(s) with prompt notification and remediation | Low incident history |
| 3 | One significant breach with adequate response | Moderate history |
| 4 | Multiple breaches or one enforcement action | Elevated history |
| 5 | Major enforcement action or pattern of breach non-compliance | High-risk history |
Dimension 6: Control Maturity (Weight: 10%)
| Score | Criterion | Description |
|---|---|---|
| 1 | Optimized — continuous improvement, metrics-driven, automated controls | Industry leading |
| 2 | Managed — controls measured and monitored, regular testing | Mature program |
| 3 | Defined — documented policies and procedures, periodic testing | Established program |
| 4 | Developing — basic controls in place, gaps in documentation | Emerging program |
| 5 | Initial — ad hoc controls, minimal documentation | Immature program |
Dimension 7: Processing Autonomy (Weight: 10%)
| Score | Criterion | Description |
|---|---|---|
| 1 | No discretion — purely technical processing per exact instructions | Minimal autonomy |
| 2 | Limited discretion — predefined processing options | Low autonomy |
| 3 | Moderate discretion — processor selects technical means | Standard autonomy |
| 4 | Significant discretion — processor defines processing logic | Elevated autonomy |
| 5 | High discretion — processor approaches controller boundary | Maximum autonomy |
Risk Score Calculation
Weighted Risk Score = Σ (Dimension Score × Dimension Weight)
Weighted Risk Score = (D1 × 0.15) + (D2 × 0.25) + (D3 × 0.15) + (D4 × 0.15)
+ (D5 × 0.10) + (D6 × 0.10) + (D7 × 0.10)
Risk Tier Assignment
| Tier | Score Range | Label | Oversight Level |
|---|---|---|---|
| Tier 1 | 3.5 – 5.0 | High Risk | Maximum oversight: annual on-site audit, quarterly monitoring, full due diligence refresh annually |
| Tier 2 | 2.5 – 3.4 | Standard Risk | Standard oversight: annual remote audit, semi-annual monitoring, due diligence refresh biennially |
| Tier 3 | 1.0 – 2.4 | Low Risk | Minimum oversight: biennial documentation audit, annual monitoring, due diligence refresh triennially |
Tier-Based Oversight Requirements
| Activity | Tier 1 (High) | Tier 2 (Standard) | Tier 3 (Low) |
|---|---|---|---|
| Due diligence refresh | Annual | Biennial | Triennial |
| Privacy audit | Annual (Type 2 or 3) | Annual (Type 1) | Biennial (Type 1) |
| Sub-processor review | Quarterly | Semi-annual | Annual |
| DPA review | Annual | Biennial | Triennial |
| Risk score recalculation | Semi-annual | Annual | Biennial |
| Continuous monitoring | Active monitoring | Periodic monitoring | Annual check |
Scoring Adjustments
Escalation Triggers
The following events trigger automatic tier escalation (one tier up):
| Trigger | Duration |
|---|---|
| Personal data breach at vendor | Until post-breach reassessment completed |
| Regulatory enforcement action | Until remediation verified |
| Certification lapse (> 30 days) | Until certification renewed |
| Material service change without prior notification | Until change assessed |
| Failed audit (Critical findings) | Until remediation verified |
De-escalation Criteria
Tier reduction requires:
- At least one completed audit cycle at current tier with no Major or Critical findings
- Updated certifications covering all processing in scope
- DPO approval of tier reduction
- Documentation of rationale
Aggregated Vendor Risk Dashboard
Summit Cloud Partners maintains an aggregated view of vendor privacy risk:
| Metric | Description |
|---|---|
| Total vendors processing personal data | Count of active vendor DPAs |
| Vendors by tier | Distribution across Tier 1/2/3 |
| Average risk score | Mean weighted score across all vendors |
| Trend | Quarter-over-quarter score movement |
| Overdue assessments | Vendors past their scheduled reassessment date |
| Open audit findings | Total by severity |
| Vendors with third-country transfers | Count and transfer mechanisms used |
Key Regulatory References
- GDPR Recital 76 — Risk assessment based on likelihood and severity
- GDPR Article 24 — Controller responsibility proportionate to risk
- GDPR Article 28(1) — Sufficient guarantees requirement
- GDPR Article 32(1) — Security measures accounting for risk
- EDPB Guidelines 07/2020 — Processor assessment factors (paragraph 86)
- NIST SP 800-30 Rev. 1 — Guide for Conducting Risk Assessments (methodology reference)
Vendor Termination Data Return and Deletion
Overview
GDPR Article 28(3)(g) requires that at the choice of the controller, the processor shall "delete or return all the personal data to the controller after the end of the provision of services relating to processing, and delete existing copies unless Union or Member State law requires storage of the personal data." This termination obligation ensures that personal data does not persist at a former processor beyond the legitimate processing period.
The EDPB Guidelines 07/2020 (paragraph 108) emphasize that this obligation extends to all copies, backups, and derived data — not just production data. The deletion must be verifiable, and the controller should obtain written certification.
At Summit Cloud Partners, the Vendor Termination Data Protocol provides a structured process for managing data return and deletion when vendor relationships end.
Termination Triggers
| Trigger | Description | Timeline Considerations |
|---|---|---|
| Contract expiry (non-renewal) | MSA/DPA term ends without renewal | 90-day notice per DPA |
| Termination for convenience | Controller elects to terminate | Per MSA notice period |
| Termination for cause | Material DPA breach by processor | Immediate or per cure period |
| Service migration | Controller moves to alternative provider | Overlap period for data migration |
| Vendor insolvency | Processor enters insolvency proceedings | Emergency data retrieval |
| Regulatory order | Supervisory authority orders cessation | Per order timeline |
Data Return Process
Step 1: Data Inventory and Mapping
Before initiating return, confirm the complete scope of personal data held by the processor:
| Data Category | Location | Format | Volume | Retention Basis |
|---|---|---|---|---|
| Production data | Primary database | Structured (SQL/JSON) | [Volume] | DPA processing |
| Backup data | Backup storage | Encrypted backup files | [Volume] | Business continuity per DPA |
| Log data | Log storage | Semi-structured (JSON/text) | [Volume] | Security monitoring |
| Derived/aggregated data | Analytics system | Structured | [Volume] | Processing output |
| Metadata | Various systems | Structured | [Volume] | System operation |
| Cached data | CDN/cache layers | Various | [Volume] | Performance |
Step 2: Data Export Format and Method
Standard Export Formats:
| Data Type | Preferred Format | Alternative Format | Notes |
|---|---|---|---|
| Structured data | CSV with defined schema | JSON, XML, Parquet | UTF-8 encoding required |
| Documents | Original format (PDF, DOCX) | ZIP archive | Preserve directory structure |
| Images/media | Original format (PNG, JPEG) | ZIP archive | Preserve metadata |
| Logs | JSON lines (JSONL) | CSV | Include timestamps |
| API-accessible data | Direct API extraction | Bulk export endpoint | Paginated if large |
Export Methods:
| Method | When to Use | Security Requirements |
|---|---|---|
| Encrypted file transfer (SFTP) | Large datasets | TLS 1.2+, PGP encryption |
| Secure API extraction | Structured, API-accessible data | OAuth 2.0, TLS 1.3 |
| Encrypted portable media | Very large datasets without bandwidth | AES-256 encryption, tracked courier |
| Cloud-to-cloud migration | Cloud provider transition | Encrypted transfer, access audit |
Step 3: Data Validation
Upon receiving returned data, Summit Cloud Partners validates:
| Validation Check | Method | Pass Criteria |
|---|---|---|
| Completeness | Record count comparison | Returned count matches source count |
| Integrity | Checksum verification (SHA-256) | Checksums match vendor-provided manifest |
| Format compliance | Schema validation | All fields present per agreed schema |
| Encoding | Character encoding verification | UTF-8 without corruption |
| Sample verification | Random sample manual review | Data content matches expectations |
Data Deletion Process
Deletion Scope
The processor must delete ALL copies of personal data, including:
- Production data — Primary databases and data stores
- Backup data — All backup copies including off-site backups
- Disaster recovery copies — DR site data
- Log data — Application logs, access logs, audit logs containing personal data
- Cached data — CDN caches, application caches, database caches
- Derived data — Analytics outputs, aggregated data containing personal data
- Metadata — System metadata referencing personal data
- Archived data — Any archived copies
- Sub-processor data — Data at all sub-processors
Deletion Methods
| Data Location | Deletion Method | Verification |
|---|---|---|
| Databases (SQL) | DELETE + VACUUM or DROP TABLE | Query confirmation; storage analysis |
| Object storage (S3/Blob) | Delete all objects + bucket | Bucket listing verification |
| File systems | Secure overwrite (NIST 800-88) | Disk analysis confirmation |
| SSD/Flash storage | Crypto-erase (destroy encryption key) | Vendor attestation |
| Backup tapes | Degaussing or physical destruction | Destruction certificate |
| Application caches | Cache flush + TTL expiry confirmation | Application verification |
| Log systems | Targeted log deletion or retention expiry | Log query confirmation |
| Sub-processors | Cascade deletion instruction | Sub-processor deletion certificate |
Deletion Timeline
| Phase | Activity | DPA Standard Timeline |
|---|---|---|
| T+0 | Controller elects deletion (or return + deletion) | Upon termination notice |
| T+0 to T+30 | Data return completed (if return elected) | 30 calendar days |
| T+30 to T+60 | Production data deletion | 60 calendar days from termination |
| T+60 to T+90 | Backup and archive deletion | 90 calendar days from termination |
| T+90 | Deletion certification issued | 90 calendar days from termination |
Deletion Exceptions
Article 28(3)(g) permits continued storage where "Union or Member State law requires storage of the personal data." Exceptions must be:
| Requirement | Processor Action |
|---|---|
| Documented in writing | Processor identifies specific legal requirement |
| Limited to required data | Only data subject to legal retention requirement |
| Isolated from production | Retained data moved to restricted storage |
| Time-limited | Retained only for legally required duration |
| Notified to controller | Controller informed of retention and legal basis |
Deletion Certification
The processor must provide a written deletion certification containing:
| Field | Content |
|---|---|
| Certifying party | Name and title of authorized processor representative |
| Controller name | Summit Cloud Partners |
| DPA reference | Reference to terminated DPA |
| Deletion scope | Description of all data deleted (categories, locations, formats) |
| Deletion date(s) | Date each deletion action was completed |
| Deletion method(s) | Technical method used for each data location |
| Sub-processor deletion | Confirmation that all sub-processors have also deleted data |
| Exceptions | Any data retained under legal obligation (with legal basis citation) |
| Certification date | Date of certification |
| Signature | Authorized officer signature |
Transition Planning
For service migrations, a transition plan ensures continuity while managing data protection obligations:
| Phase | Activity | Duration |
|---|---|---|
| Planning | Define data migration scope, format, timeline | 4-6 weeks |
| Parallel operation | Old and new vendor operate simultaneously | 2-4 weeks |
| Migration | Data transferred from old to new vendor | 1-2 weeks |
| Validation | Verify complete and accurate migration | 1 week |
| Cutover | Switch production to new vendor | 1 day |
| Decommission | Terminate old vendor; initiate deletion | Per DPA timeline |
| Deletion verification | Confirm old vendor data deletion | 90 days |
Key Regulatory References
- GDPR Article 28(3)(g) — Deletion or return of personal data upon termination
- GDPR Article 17 — Right to erasure (informs deletion standards)
- GDPR Article 5(1)(e) — Storage limitation principle
- EDPB Guidelines 07/2020 — Paragraph 108 on termination data obligations
- NIST SP 800-88 Rev. 1 — Guidelines for Media Sanitization
- ISO/IEC 27001:2022 — A.8.10 Information deletion
Sponsors
Details
- Marketplace
- mukul975/Privacy-Data-Protection-Skills
- Source
- plugins/vendor-privacy-management-skills
- Author
- Mahipal
- Category
- Compliance
- License
- Apache-2.0
- Keywords
- vendor-management, dpa, sub-processor, due-diligence
More from mukul975/Privacy-Data-Protection-Skills
All 21- ai-privacy-governance-skillsv1.0.0
- children-privacy-skillsv1.0.0
- consent-management-skillsv1.0.0
- cookie-consent-skillsv1.0.0
- cross-border-transfers-skillsv1.0.0
- data-breach-response-skillsv1.0.0
- data-classification-skillsv1.0.0
- data-retention-skillsv1.0.0
- data-subject-rights-skillsv1.0.0
- employee-privacy-skillsv1.0.0
- gdpr-compliance-skillsv1.0.0
- global-privacy-regulations-skillsv1.0.0
- healthcare-privacy-skillsv1.0.0
- privacy-audit-skillsv1.0.0
- privacy-by-design-skillsv1.0.0
- privacy-engineering-skillsv1.0.0
- privacy-impact-assessment-skillsv1.0.0
- privacy-skills-completev1.0.0
- records-of-processing-skillsv1.0.0
- us-state-privacy-skillsv1.0.0