mukul975 avatar

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-skills

Run it inside Claude Code after adding the marketplace with /plugin marketplace add mukul975/Privacy-Data-Protection-Skills.

Contents

Discovered from source

Skills 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)

AspectController ResponsibilityProvider Responsibility
Data encryption at restConfigure and manage keysProvide encryption infrastructure
Access management (app level)Define and manageProvide IAM platform
Network security (app level)Configure security groups, firewall rulesProvide network infrastructure
Physical securityNoneFull responsibility
Patch management (OS)Controller (or managed service)Hypervisor and below
Data backupConfigure and manageProvide backup infrastructure
Incident detection (app)Application-level monitoringInfrastructure-level monitoring

PaaS (Platform as a Service)

AspectController ResponsibilityProvider Responsibility
Application code securityFull responsibilityNone
Data handling in applicationFull responsibilityNone
Runtime and middlewareLimited — configuration onlyManage platform components
OS and infrastructureNoneFull responsibility
Platform security patchingNoneFull responsibility
Identity managementConfigureProvide identity platform

SaaS (Software as a Service)

AspectController ResponsibilityProvider Responsibility
Data entered by usersDetermine what data to processProcess per controller instructions
Application securityNone (except configuration)Full responsibility
Infrastructure securityNoneFull responsibility
Data portabilityDefine export requirementsProvide export functionality
Data deletionRequest deletionImplement deletion per DPA
Access configurationConfigure user rolesProvide RBAC platform

Assessment Framework

Domain 1: Data Residency and Sovereignty

Assessment Questions:

#QuestionExpected Evidence
1.1In which regions/availability zones will personal data be stored at rest?Architecture documentation specifying data storage locations
1.2Can the controller restrict processing to specific geographic regions?Configuration documentation showing region-locking capability
1.3Are there any circumstances where data may be processed outside the selected region?Disclosure of any cross-region processing (DR, support, analytics)
1.4Where is metadata and telemetry data stored?Often stored in provider's home jurisdiction — must be disclosed
1.5Where do support staff access data from?List of countries from which support personnel may access data
1.6What 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

#QuestionExpected Evidence
2.1How is tenant data isolated from other customers' data?Architecture documentation — logical/physical separation details
2.2Are encryption keys unique per tenant?Key management architecture documentation
2.3Can one tenant's operations affect another tenant's data?Side-channel and cross-tenant risk assessment
2.4How are shared infrastructure components secured?Hypervisor security, shared storage controls
2.5What 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:

ControlRequirementAssessment Check
A.1PII processor consent — process only per controller instructionsVerify contractual terms and processing boundaries
A.2Purpose limitation — no processing beyond controller purposeReview processing scope documentation
A.3Use for marketing — no use of PII for marketing without consentConfirm no data monetization or marketing use
A.4Notification — notify controller of government access requestsVerify government access notification process
A.5Disclosure — document all disclosures of PIIReview disclosure logging mechanism
A.10Return, transfer, and disposal — secure data handling at terminationVerify deletion procedures and certification
A.11Confidentiality — binding confidentiality obligations on personnelVerify personnel agreements cover cloud-specific risks
A.12Sub-contracting — notification of sub-processor engagementVerify 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:

LevelDescriptionAssessment Method
Level 1: Self-AssessmentProvider completes CSA Consensus Assessments Initiative Questionnaire (CAIQ)Review self-assessment for completeness and substantiation
Level 2: Third-Party AuditIndependent audit against CSA Cloud Controls Matrix (CCM)Review audit report, scope, and findings
Level 3: Continuous MonitoringReal-time monitoring of control effectivenessReview continuous monitoring dashboard and alerts

Key CCM Control Domains for Privacy:

DomainControlsPrivacy Relevance
DSP (Data Security & Privacy)DSP-01 through DSP-19Data classification, retention, inventory, privacy by design
GRC (Governance, Risk, Compliance)GRC-01 through GRC-08Governance framework, risk assessment, policy management
IAM (Identity & Access Management)IAM-01 through IAM-16Access control, credential management, MFA
SEF (Security Incident Management)SEF-01 through SEF-08Incident response, breach notification

Domain 5: SOC 2 Type II Privacy Criterion

The AICPA Trust Services Criteria Privacy criterion evaluates:

CriterionAreaAssessment Focus
P1NoticeProvider discloses privacy practices to controllers
P2Choice and consentController can configure privacy settings
P3CollectionData collection limited to stated purposes
P4Use, retention, disposalProcessing per instructions; retention per DPA; certified deletion
P5AccessController can access and retrieve their data
P6Disclosure to third partiesSub-processor disclosure and management
P7Security for privacyTechnical controls protecting PII
P8QualityData integrity and accuracy controls
P9Monitoring and enforcementCompliance monitoring and breach response

Domain 6: Shared Responsibility Model Mapping

Document the shared responsibility boundary for every control domain:

Control DomainController ResponsibilityProvider ResponsibilityGap/Risk
Data classificationClassify data before uploadProvide 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

DomainWeightScore (1-5)Weighted
Data residency and sovereignty20%
Multi-tenancy and isolation20%
ISO 27018 compliance15%
CSA STAR level15%
SOC 2 Privacy criterion15%
Shared responsibility clarity15%
TOTAL100%

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:

ElementDescriptionExample
Subject-matterThe specific service being provided"Cloud-hosted customer analytics platform"
DurationPeriod of processing"Duration of the Master Services Agreement plus 90-day data return/deletion period"
Commencement dateWhen processing begins"Effective as of the MSA effective date"
Survival clausesObligations surviving termination"Confidentiality, deletion certification, and audit rights survive for 3 years"

Provision 2: Nature and Purpose of Processing

Required Elements:

ElementDescriptionExample
Nature of processingOperations performed on personal data"Collection via API ingestion, storage in encrypted database, automated analysis, aggregated reporting, deletion upon contract termination"
Purpose of processingWhy processing occurs"To provide Summit Cloud Partners with customer behavior analytics enabling product improvement decisions"
Processing instructions scopeBoundaries 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 CategoryDescriptionSensitivity Level
Contact informationName, email address, phone numberStandard
Account identifiersUser ID, account number, tenant IDStandard
Usage dataFeature usage logs, session duration, click pathsStandard
Device informationIP address, browser type, OS versionStandard
Location dataCity/region derived from IP address (not precise GPS)Elevated
Payment metadataTransaction dates, plan type (not card numbers)Elevated

Provision 4: Categories of Data Subjects

CategoryDescriptionApproximate Volume
Enterprise customersNamed users of Summit Cloud Partners platform50,000
Trial usersUsers on free trial accounts15,000
API consumersDevelopers using Summit Cloud Partners API5,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:

  1. Right to issue instructions: The controller has the right to issue documented written instructions regarding processing
  2. Right to audit: The controller may audit the processor's compliance (Article 28(3)(h))
  3. Obligation to determine lawful basis: The controller confirms that processing is lawful under Article 6
  4. Obligation to respond to data subjects: The controller is responsible for responding to data subject requests, with processor assistance
  5. 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:

ProvisionDescription
Authorization mechanismGeneral written authorization with notification of changes
Notification periodMinimum 30 calendar days before engaging new sub-processor
Objection rightController may object within the notification period
Objection consequenceIf objection not resolved, either party may terminate affected services
Flow-down obligationsSub-processor contract must impose equivalent Article 28(3) obligations
LiabilityProcessor 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 ScenarioRequired Mechanism
EEA to Adequacy country (per Art. 45)Reference adequacy decision
EEA to non-adequate countryStandard Contractual Clauses (Commission Decision 2021/914)
EEA to non-adequate country with supplementary measuresSCCs plus technical/organizational/contractual supplementary measures per EDPB Recommendations 01/2020

DPA Drafting Checklist

#RequirementArticleStatus
1Subject-matter and duration specified28(3)[ ]
2Nature and purpose of processing defined28(3)[ ]
3Types of personal data listed28(3)[ ]
4Categories of data subjects listed28(3)[ ]
5Controller obligations and rights defined28(3)[ ]
6Processor processes only on documented instructions28(3)(a)[ ]
7Confidentiality obligations for authorized personnel28(3)(b)[ ]
8Article 32 security measures implemented28(3)(c)[ ]
9Sub-processor conditions and authorization28(3)(d)[ ]
10Assistance with data subject rights28(3)(e)[ ]
11Assistance with Articles 32-36 compliance28(3)(f)[ ]
12Deletion or return upon termination28(3)(g)[ ]
13Audit rights and information access28(3)(h)[ ]
14Sub-processor flow-down obligations per Art. 28(4)28(4)[ ]
15International transfer mechanism (if applicable)28(3), Ch. V[ ]
16Breach notification obligations per Art. 33(2)33(2)[ ]
17DPA 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.

FieldDescription
Vendor nameLegal entity name
Product/service nameSaaS product name
CategoryCRM, HR, Analytics, Communication, DevOps, etc.
Business ownerDepartment and named individual
Procurement dateWhen the service was contracted
DPA statusExecuted / In negotiation / Not required
DPA referenceDPA document reference number
Privacy review statusCompleted / In progress / Pending
Risk tierPer vendor risk scoring model
Personal data categoriesWhat personal data is processed
Data subjectsWhose data is processed
Processing purposesWhy data is processed
Processing locationsWhere data is stored/processed
Integration methodSSO, API, manual upload, etc.
Data flow directionInbound / Outbound / Bidirectional
Contract expiryWhen the contract term ends
Auto-renewal dateWhen auto-renewal triggers
Annual costTotal annual spend
License countNumber of active users/seats

Tier 2: Known Unsanctioned — Shadow IT Detected

Applications detected through discovery tools that lack formal procurement or privacy review.

FieldDescription
Application nameAs detected
Detection methodCASB, DNS, expense, SSO log, etc.
Detection dateWhen first observed
Usage scopeEstimated users and frequency
Likely data categoriesInferred from application type
Risk assessmentPreliminary risk level
Remediation statusUnder review / Sanctioning in progress / Blocked / Accepted
Business unitDepartment(s) using the application

Tier 3: Evaluated and Excluded

Applications evaluated and determined to not process personal data.

FieldDescription
Application nameProduct name
Evaluation dateWhen reviewed
DeterminationNo personal data processing
RationaleWhy excluded from inventory
Next review dateWhen 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:

ComponentDetail
CASB vendorDeployed as inline proxy and API connector
CoverageAll corporate network egress and managed endpoints
Discovery scopeHTTP/HTTPS traffic to known SaaS domains
Update frequencyReal-time discovery, weekly consolidated reporting
IntegrationFeeds 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:

  1. Aggregate DNS query logs from internal resolvers
  2. Match resolved domains against SaaS provider domain databases
  3. Cross-reference with sanctioned vendor list
  4. 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

StepActivityResponsible
1Extract current CASB discovery reportInfoSec
2Extract current sanctioned vendor listPrivacy Team
3Compare: identify new unsanctioned applicationsPrivacy Team
4Compare: identify sanctioned apps no longer in usePrivacy Team
5Verify DPA status for all sanctioned vendorsPrivacy Team
6Check contract expiry dates (90-day lookahead)Legal/Procurement
7Update inventory recordsPrivacy Team
8Report to DPOPrivacy Team Lead

Reconciliation Outcomes

FindingAction
New unsanctioned SaaS discoveredInitiate shadow IT remediation workflow
Sanctioned SaaS no longer in useInitiate vendor termination data workflow
DPA expired or missingExpedite DPA execution or service suspension
Contract approaching expiryTrigger renewal privacy review
Data processing scope change detectedInitiate DPA amendment review

Contract Status Tracking

StatusDefinitionAction Required
Active — CompliantContract active, DPA executed, privacy review currentStandard monitoring
Active — DPA PendingContract active, DPA in negotiationExpedite DPA; restrict data sharing if > 30 days
Active — Review OverdueContract active, privacy review past dueSchedule immediate review
Expiring (< 90 days)Contract approaching expiryInitiate renewal assessment
ExpiredContract term endedInitiate termination data workflow
SuspendedService suspended pending privacy issue resolutionTrack resolution
TerminatedContract terminated, data return/deletion in progressTrack 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:

StepActionTimeline
1Processor identifies need for new sub-processor—
2Processor submits sub-processor details to controllerPre-engagement
3Controller conducts due diligence on proposed sub-processor15 business days
4Controller issues written approval or rejection5 business days
5If approved, processor executes sub-processor DPABefore processing begins
6Processor provides controller with confirmation of sub-processor DPA execution5 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:

StepActionTimeline
1Processor notifies controller of intended sub-processor change30 days before engagement
2Notification includes: name, location, function, data access scopeWith notification
3Controller evaluates notification and exercises objection right if neededWithin 14 days
4If no objection, processor may engage sub-processorAfter objection period expires
5If objection raised, parties negotiate resolutionWithin 30 days
6If unresolved, either party may terminate affected servicesPer 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:

FieldDescriptionExample
Sub-processor legal nameFull legal entity name"Datastream Analytics Inc."
JurisdictionCountry of establishment"United States (Delaware)"
Processing locationWhere personal data will be processed"AWS us-east-1, Virginia, USA"
Processing functionWhat the sub-processor will do"Real-time event processing and aggregation"
Data access scopeWhat personal data the sub-processor accesses"Pseudonymized usage events, IP addresses"
Engagement dateProposed start date"2026-05-01"
Transfer mechanismIf outside EEA, the legal transfer basis"EU-US Data Privacy Framework certification"
Security certificationsRelevant 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:

  1. Objection grounds: Reasonable data protection concerns (not arbitrary)
  2. Objection period: Minimum 14 calendar days from notification receipt (Summit Cloud Partners standard: 30 days)
  3. Objection format: Written notice to processor's designated privacy contact
  4. Resolution process: Good-faith negotiation within defined timeframe
  5. Escalation: If unresolved, termination right for affected services without penalty

Objection Decision Matrix:

ConcernActionEscalation
Sub-processor in jurisdiction with inadequate protection and no valid transfer mechanismObject — require alternative sub-processor or supplementary measuresDPO review
Sub-processor lacks adequate security certificationsObject — request vendor provide evidence of equivalent controlsPrivacy Team review
Sub-processor has history of data breachesObject — require enhanced contractual safeguards or alternativeDPO review
Sub-processor change is administrative (name change, corporate restructure)No objection — acknowledge notificationPrivacy Team acknowledgment
Sub-processor adds processing location within EEAEvaluate — generally no objection if controls equivalentPrivacy 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:

ObligationController → Processor DPAProcessor → Sub-Processor DPA
Process only on documented instructionsArticle 28(3)(a)Must mirror
Confidentiality obligationsArticle 28(3)(b)Must mirror
Security measures (Art. 32)Article 28(3)(c)Must mirror or exceed
Further sub-processing restrictionsArticle 28(3)(d)Must cascade
DSR assistanceArticle 28(3)(e)Must mirror
Compliance assistance (Art. 32-36)Article 28(3)(f)Must mirror
Deletion/return on terminationArticle 28(3)(g)Must mirror
Audit rightsArticle 28(3)(h)Must provide controller with audit path
Breach notificationArticle 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:

  1. Direct audit rights over sub-processor (contractually passed through)
  2. Processor audits sub-processor on controller's behalf and shares results
  3. 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:

FieldDescription
Primary processorVendor with direct DPA
Sub-processor nameLegal entity name
Sub-processor locationCountry and specific processing location
Processing functionWhat the sub-processor does
Data access scopeCategories of personal data accessed
Authorization typeSpecific or general authorization
Authorization dateDate of approval
DPA statusSub-processor DPA executed / pending
Transfer mechanismIf applicable — SCC, adequacy, DPF
CertificationsCurrent certifications
Last review dateMost recent assessment
Risk classificationHigh / Standard / Low

Monitoring and Compliance

Ongoing Monitoring Activities

  1. Quarterly sub-processor list reconciliation: Compare processor-provided lists against register
  2. Certification tracking: Monitor sub-processor certification expiry dates
  3. Change notification tracking: Verify all sub-processor changes were properly notified
  4. Annual flow-down verification: Sample sub-processor DPAs to verify equivalent terms

Key Performance Indicators

KPITargetMeasurement
Sub-processor notification compliance100% of changes notified before engagementQuarterly audit
Objection response time100% within 14 calendar daysContinuous
Flow-down DPA coverage100% of sub-processors have executed DPAsQuarterly audit
Sub-processor register accuracy100% match with processor-provided listsQuarterly 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

NotificationGDPR RequirementSummit Cloud Partners DPA Standard
Processor → Controller"Without undue delay" (Art. 33(2))Within 24 hours of becoming aware
Controller → Supervisory AuthorityWithin 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 → ProcessorPer sub-processor DPAWithin 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:

StepActionResponsibleTimeframe
1.1Log notification in breach registerPrivacy Team on-callImmediate
1.2Verify notification came from authorized vendor contactPrivacy Team15 minutes
1.3Acknowledge receipt to vendorPrivacy Team30 minutes
1.4Alert Summit Cloud Partners Breach Response TeamPrivacy Team30 minutes
1.5Classify initial severityBreach Response Team Lead1 hour
1.6Activate appropriate response levelBreach Response Team Lead1 hour

Severity Classification:

LevelCriteriaResponse Level
CriticalSpecial category data exposed; > 10,000 data subjects; criminal access confirmedFull incident response — all hands
HighSensitive data exposed; 1,000-10,000 data subjects; active threatExpanded response team
MediumStandard personal data exposed; < 1,000 data subjects; containedCore response team
LowLimited exposure; pseudonymized data; no evidence of accessPrivacy Team + InfoSec lead

Phase 2: Assessment and Investigation (T+2 to T+24 hours)

StepActionResponsible
2.1Request detailed incident report from vendorPrivacy Team
2.2Identify affected Summit Cloud Partners data and data subjectsPrivacy Team + IT
2.3Assess whether breach is "likely to result in a risk" (Art. 33(1) threshold)DPO
2.4Assess whether breach results in "high risk" (Art. 34(1) threshold)DPO
2.5Coordinate with vendor on containment confirmationInfoSec Team
2.6Determine if other controllers are affected (multi-tenant breach)Privacy Team
2.7Engage legal counsel if liability implications existLegal Team
2.8Draft preliminary supervisory authority notification (if threshold met)DPO + Legal

Vendor Information Requests:

Information RequiredPurpose
Root cause analysis (even preliminary)Understand attack vector and likelihood of ongoing risk
Exact data categories compromisedAssess risk to data subjects
Exact data subject count or best estimateDetermine notification scope
Timeline: when breach occurred, when detected, when containedAssess detection capability
Containment measures implementedVerify 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 completionPlanning input

Phase 3: Regulatory Notification Decision (T+24 to T+48 hours)

DecisionCriteriaAction
Notify SABreach likely to result in risk to data subjectsFile notification within 72 hours of awareness
Do not notify SABreach unlikely to result in risk (documented assessment)Document decision and rationale; retain in breach register
Notify in phasesCannot provide full details within 72 hoursFile initial notification within 72 hours; provide updates as available

Article 33(3) Notification Content:

Required ElementDescription
(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

ActivityResponsibleTimeline
Monitor vendor's ongoing investigationPrivacy TeamOngoing
Request and review vendor's root cause analysisPrivacy Team + InfoSecWithin 30 days
Assess vendor's remediation planPrivacy Team + InfoSecWithin 30 days
Verify remediation implementationInfoSecWithin 60 days
Update vendor risk scorePrivacy TeamImmediate
Evaluate contractual remediesLegal TeamWithin 30 days
Conduct lessons-learned reviewBreach Response TeamWithin 90 days

Liability Allocation

DPA Liability Provisions

The DPA should address breach-related liability:

ProvisionDescription
Processor indemnificationProcessor indemnifies controller for losses caused by processor breach (including fines to the extent legally permissible)
Cooperation obligationProcessor must cooperate fully with controller's investigation and regulatory notifications
Forensic costsAllocation of forensic investigation costs
Notification costsAllocation of data subject notification costs
Credit monitoringAllocation of credit monitoring / identity protection costs for affected data subjects
Regulatory engagementProcessor must participate in regulatory inquiries
Limitation of liabilityCarve-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:

RoleResponsibilities
Sub-processorNotify 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 AuthorityMay 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)

AspectDetail
StandardExtension to ISO 27001/27002 for PII management
ScopePII controller (Annex A) and PII processor (Annex B) controls
Certification bodyAccredited ISO certification bodies
Audit typeThird-party certification audit (Stage 1 + Stage 2)
Validity3-year cycle with annual surveillance audits
GDPR relevanceHigh — maps directly to GDPR requirements per Annex D
Acceptance criteriaCertificate scope must cover processing services provided to Summit
VerificationCheck accreditation body registry; verify scope statement
Supplementation neededVerify that Annex B (processor) controls are in scope; if only Annex A (controller), supplementary processor assessment required

GDPR Certification per Article 42

AspectDetail
StandardCertification per criteria approved by supervisory authority or EDPB
Certification bodyAccredited per Article 43 by national accreditation body and supervisory authority
GDPR relevanceMaximum — specifically designed for GDPR compliance demonstration
Acceptance criteriaCertificate issued by Article 43 accredited body; scope covers processing
Current statusVery few Article 42 certifications currently available (as of March 2026)
Supplementation neededMinimal 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

AspectDetail
StandardAICPA Trust Services Criteria — Privacy criterion
ScopeNotice, choice, collection, use/retention/disposal, access, disclosure, security, quality, monitoring
Audit typeIndependent CPA examination over minimum 6-month period
GDPR relevanceModerate-High — covers many Article 28/32 requirements but US-centric
Acceptance criteriaType II (not Type I); Privacy criterion included; no qualified opinions; scope covers relevant services
VerificationRequest full report under NDA; review scope, findings, exceptions
Supplementation neededGDPR-specific gap assessment required: cross-border transfer controls, DPA-specific obligations, sub-processor cascade

SOC 2 Type II (Security Criterion Only)

AspectDetail
Acceptance criteriaType II; no qualified opinions; scope covers relevant services
GDPR relevanceModerate — covers Article 32 security measures
Supplementation neededFull privacy assessment required for non-security GDPR obligations

ISO/IEC 27001:2022 — Information Security Management System

AspectDetail
Acceptance criteriaCurrent version (2022 preferred); scope covers processing services; accredited certification body
GDPR relevanceModerate — strong for Article 32 security; does not address privacy-specific requirements
Supplementation neededPrivacy gap assessment covering Art. 28(3) obligations, DSR assistance, breach notification, data handling

Tier C: Domain-Specific Certifications

ISO/IEC 27018:2019 — Cloud Privacy

AspectDetail
ScopeCloud-specific PII protection controls
AcceptanceRelevant only for cloud service providers; supplements ISO 27001
SupplementationMust be combined with ISO 27001; does not stand alone

CSA STAR Level 2 — Cloud Security

AspectDetail
ScopeCloud Controls Matrix (CCM) third-party audit
AcceptanceLevel 2 (third-party audit) required; Level 1 (self-assessment) insufficient as standalone
SupplementationCloud security focus; privacy gap assessment required

APEC Cross-Border Privacy Rules (CBPR) System

AspectDetail
ScopeAsia-Pacific cross-border data transfer framework
AcceptanceRecognized for APEC economy vendors; does not substitute for GDPR compliance
GDPR relevanceLimited — different legal framework; may indicate privacy program maturity
SupplementationFull GDPR compliance assessment still required

EU Cloud Code of Conduct (SCOPE Europe)

AspectDetail
StandardGDPR Article 40 approved code of conduct for cloud services
ScopeCloud service provider GDPR compliance
AcceptanceApproved by Belgian DPA as monitoring body (2021)
GDPR relevanceHigh — specifically mapped to GDPR obligations
SupplementationMinimal for in-scope cloud processing; verify monitoring body oversight

Tier D: Self-Assessments and Basic Certifications

CertificationAcceptance Level
CSA STAR Level 1 (self-assessment)Accepted as supplementary evidence only; not standalone
Vendor privacy policy / self-declarationNot accepted as certification; supplementary only
HITRUST CSFAccepted 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 RequirementISO 27701SOC 2 PrivacySOC 2 SecurityISO 27001ISO 27018Art. 42 Cert
Art. 28(3)(a) Documented instructionsFullPartialNoneNoneFullFull
Art. 28(3)(b) ConfidentialityFullFullPartialFullFullFull
Art. 28(3)(c) Security (Art. 32)FullFullFullFullFullFull
Art. 28(3)(d) Sub-processor mgmtFullPartialNonePartialFullFull
Art. 28(3)(e) DSR assistanceFullPartialNoneNonePartialFull
Art. 28(3)(f) Compliance assistanceFullPartialNoneNoneNoneFull
Art. 28(3)(g) Deletion/returnFullFullNonePartialFullFull
Art. 28(3)(h) Audit rightsFullPartialNonePartialFullFull
Art. 33(2) Breach notificationFullFullPartialPartialPartialFull
Ch. V International transfersPartialNoneNoneNoneNoneFull

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:

GapSupplementation Method
DSR assistance capabilityVendor provides DSR handling procedure documentation and SLA commitments
Sub-processor managementVendor provides sub-processor list, notification mechanism, and flow-down DPA sample
Breach notification processVendor provides incident response plan with notification timeframes
International transfer controlsVendor provides Transfer Impact Assessment and supplementary measures documentation
Deletion/return capabilitiesVendor demonstrates deletion procedure and provides sample deletion certificate
Audit facilitationDPA audit rights clause verified; vendor confirms practical audit access

Certification Verification Process

StepActivityEvidence
1Obtain copy of certificate and audit reportPDF certificate; SOC 2 report under NDA
2Verify certification body accreditationCheck national accreditation body registry
3Verify certificate validity (not expired)Certificate dates; annual surveillance confirmation
4Verify scope covers relevant servicesScope statement includes services provided to Summit
5Review exceptions or qualified opinions (SOC 2)No material exceptions affecting Summit data
6Identify gaps per equivalence matrixDocument uncovered requirements
7Request supplementary evidence for gapsPer gap supplementation table
8Document acceptance decisionRecord 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

ActivityTier 1 (High Risk)Tier 2 (Standard)Tier 3 (Low Risk)
Full reassessmentAnnualBiennialTriennial
Privacy auditAnnual (Type 2/3)Annual (Type 1)Biennial (Type 1)
Sub-processor list verificationQuarterlySemi-annualAnnual
DPA compliance reviewAnnualBiennialTriennial
Risk score recalculationSemi-annualAnnualBiennial
Certification status checkQuarterlySemi-annualAnnual
Breach monitoringContinuousContinuousMonthly check
Contract renewal privacy gate120 days before90 days before90 days before

Continuous Monitoring Signals

Automated or semi-automated monitoring sources that provide ongoing visibility:

Signal SourceWhat It MonitorsFrequencyAlert Trigger
Vendor risk intelligence platformPublic breach disclosures, enforcement actions, newsDailyNew incident involving a monitored vendor
Certification monitoringISO/SOC certificate validity and scope changesMonthlyCertificate approaching expiry (60 days)
CASB/DLPData flows to vendor — volume and category anomaliesContinuousData transfer exceeding baseline by 200%
DNS/network monitoringConnectivity patterns to vendor endpointsContinuousNew endpoints, geographic changes
Vendor security scorecardExternal security posture assessmentMonthlyScore drops below threshold
Regulatory database monitoringNew enforcement decisions involving vendorWeeklyNew published enforcement action
Sub-processor registry monitoringVendor-published sub-processor list changesWeeklyNew or changed sub-processor detected

Annual Reassessment Process

For each vendor due for reassessment:

Phase 1: Preparation (30 days before reassessment)

ActivityResponsible
Pull current vendor profile and risk scorePrivacy Team
Review monitoring signals from prior periodPrivacy Team
Compile open audit findings and remediation statusPrivacy Team
Identify changes since last assessmentPrivacy Team
Send reassessment questionnaire to vendorPrivacy Team

Phase 2: Assessment (Assessment month)

ActivityResponsible
Review vendor's updated questionnaire responsesPrivacy Team
Verify current certificationsPrivacy Team
Review sub-processor list for changesPrivacy Team
Assess any processing scope changesPrivacy Team
Conduct audit (per tier schedule)Audit Team
Recalculate risk scorePrivacy Team

Phase 3: Decision and Documentation

ActivityResponsible
Update sufficiency determinationDPO
Update vendor risk tier (if changed)Privacy Team Lead
Update monitoring schedulePrivacy Team
Communicate outcomes to business unitPrivacy Team
File reassessment documentationPrivacy Team

Contract Renewal Privacy Gate

When a vendor contract approaches renewal, a privacy gate ensures continued compliance:

TimingActivity
120 days before renewal (Tier 1) / 90 days (Tier 2/3)Privacy Team notified of upcoming renewal
90 days before renewalReview current privacy compliance status
60 days before renewalComplete any required reassessment
30 days before renewalIssue renewal privacy recommendation (Renew / Renew with conditions / Do not renew)
At renewalExecute any required DPA amendments

Renewal Privacy Decision Matrix:

Compliance StatusAudit StatusRisk TrendRecommendation
Fully compliantClean auditStable/improvingRenew
Minor gapsMinor findings onlyStableRenew with conditions
Material gapsMajor findings pendingDeterioratingRenew with conditions + accelerated audit
Significant non-complianceCritical findings openDeterioratingDo not renew (initiate termination planning)

Performance Metrics and KPIs

Vendor Privacy Program KPIs

KPITargetMeasurementFrequency
DPA coverage rate100% of data-processing vendorsActive DPAs / vendors processing personal dataQuarterly
Reassessment completion rate100% on scheduleCompleted on time / dueQuarterly
Audit completion rate100% per tier scheduleAudits completed / audits dueAnnual
Average vendor risk scoreTrending downwardMean weighted score across all vendorsSemi-annual
Open audit findings (Critical)0 past deadlineCount of overdue Critical findingsMonthly
Open audit findings (Major)0 past deadlineCount of overdue Major findingsMonthly
Sub-processor notification compliance100%Changes notified before engagement / total changesQuarterly
Mean time to acknowledge breach< 2 hoursAverage time from vendor notification to acknowledgmentPer incident
Deletion certification rate100% within DPA timelineCertifications received on time / terminationsAnnual
Shadow IT detection-to-remediation< 30 daysAverage days from detection to sanctioned/blockedQuarterly

Vendor Privacy Scorecard

Each vendor receives a quarterly privacy scorecard:

DimensionWeightScore (1-5)Trend
DPA compliance25%[X][Up/Down/Stable]
Audit performance20%[X][Up/Down/Stable]
Breach history (rolling 12 months)15%[X][Up/Down/Stable]
Sub-processor management compliance15%[X][Up/Down/Stable]
Certification currency15%[X][Up/Down/Stable]
Cooperation and responsiveness10%[X][Up/Down/Stable]
Weighted Total100%[X.X]

Governance Reporting

Monthly Privacy Team Report

SectionContent
Vendor count and tier distributionCurrent state
New vendors onboardedPrivacy review outcomes
Vendors terminatedDeletion certification status
Open audit findings by severityRemediation timeline
Monitoring alerts actionedSignal source and resolution
Shadow IT detectionsDiscovery and remediation
Upcoming deadlinesReassessments, renewals, audits due

Quarterly DPO Report

SectionContent
Program KPIs vs targetsDashboard with trend analysis
Risk tier changesEscalations and de-escalations with rationale
Significant vendor eventsBreaches, enforcement, certification changes
Regulatory developmentsNew guidance affecting vendor management
RecommendationsProgram 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.

AspectDetail
ScopeReview of processor-provided documentation and certifications
Duration3-5 business days
FrequencyAnnual
DeliverableDocumentation Audit Report
Cost allocationController 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.

AspectDetail
ScopeRemote assessment including technical verification
Duration5-10 business days
FrequencyAnnual for high-risk; biennial for standard-risk
DeliverableRemote Audit Report
Cost allocationPer 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.

AspectDetail
ScopePhysical inspection of processing facilities and controls
Duration1-3 days on-site, plus pre/post work
FrequencyAs needed; minimum biennial for highest-risk vendors
DeliverableOn-Site Inspection Report
Cost allocationPer 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:

ActivityResponsible
Select vendors for audit based on risk tier and schedulePrivacy Team
Determine audit type (Documentation / Remote / On-Site)Privacy Team Lead
Assign audit team lead and membersPrivacy Team Lead
Notify vendor of audit intent per DPA notification requirementsAudit Team Lead

30 Days Before Audit:

ActivityResponsible
Issue formal audit notification letter to vendorAudit Team Lead
Submit document request list to vendorAudit 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 processingAudit Team

7 Days Before Audit:

ActivityResponsible
Review vendor-provided documentationAudit Team
Prepare interview question setsAudit Team
Finalize on-site agenda (Type 3)Audit Team Lead
Conduct team briefingAudit Team Lead

Audit Checklist

A. DPA Compliance Verification

#Check ItemArticleEvidence Required
A1Processing limited to documented controller instructions28(3)(a)Processing logs, instruction register
A2All authorized personnel bound by confidentiality28(3)(b)Signed confidentiality agreements, HR records
A3Article 32 security measures implemented per DPA Annex II28(3)(c)Security configuration evidence
A4Sub-processors authorized and DPAs in place28(3)(d)Sub-processor register, executed DPAs
A5DSR assistance capability demonstrated28(3)(e)DSR handling procedures, response metrics
A6Compliance assistance provided for Art. 32-3628(3)(f)DPIA contributions, breach investigation support
A7Deletion/return capabilities verified28(3)(g)Deletion procedures, test results
A8Audit information and access provided28(3)(h)Audit cooperation evidence

B. Technical Controls Verification

#Check ItemEvidence Required
B1Encryption at rest implemented per DPA specificationsKey management documentation, configuration screenshots
B2Encryption in transit per DPA specificationsTLS configuration, certificate management
B3Access controls configured per principle of least privilegeRBAC configuration, access review records
B4MFA enabled for all administrative accessMFA enrollment records, policy configuration
B5Logging enabled and retained per DPA retention periodLog storage configuration, sample logs
B6Vulnerability scanning performed per scheduleScan reports, remediation records
B7Penetration testing performed per schedulePen test reports, finding remediation
B8Backup and recovery procedures testedDR test results, RPO/RTO metrics

C. Organizational Controls Verification

#Check ItemEvidence Required
C1Privacy training delivered to all relevant staffTraining records with completion dates
C2Incident response plan documented and testedIRP document, tabletop exercise records
C3Change management process followedChange log, approval records
C4Physical security controls in place (Type 3 only)Badge access logs, CCTV coverage, visitor log
C5Data retention and deletion procedures operationalRetention schedule, deletion logs
C6Records of processing maintained per Art. 30(2)ROPA documentation

D. Breach Notification Readiness

#Check ItemEvidence Required
D1Breach detection capabilities operationalSIEM configuration, alert rules
D2Breach notification procedure documented with DPA-compliant timeframeIRP with notification section, contact matrix
D3Breach notification contact details currentVerified contact information
D4Breach register maintainedBreach log (redacted if necessary)

Finding Classification

SeverityDefinitionRemediation TimelineFollow-Up
CriticalImmediate risk to personal data or fundamental DPA violationImmediate (within 7 days)Verification audit within 30 days
MajorSignificant gap in controls or DPA non-compliance30 calendar daysWritten evidence of remediation
MinorControl weakness not immediately impacting data protection90 calendar daysVerified at next scheduled audit
ObservationArea for improvement, not a compliance gapNoted for next assessmentTracked in audit records

Examples by Severity:

SeverityExample
CriticalPersonal data accessible to unauthorized personnel; no encryption at rest despite DPA requirement
MajorSub-processor engaged without notification; MFA not enforced for administrative access
MinorPrivacy training completion at 85% (target 100%); access review 2 weeks overdue
ObservationIncident response plan would benefit from more specific processor notification procedures

Remediation Tracking

All findings above Observation severity enter the remediation tracking system:

FieldDescription
Finding IDUnique identifier
VendorProcessor name
Audit dateWhen finding was identified
SeverityCritical / Major / Minor
DescriptionDetailed description of the finding
Root causeWhy the gap exists
Remediation planVendor's proposed corrective action
DeadlineDate by which remediation must be complete
Evidence requiredWhat the vendor must provide to close the finding
StatusOpen / In Progress / Remediated / Verified / Overdue
Verification methodHow 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:

QuestionIf 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:

  1. What categories of personal data will the vendor process?
  2. How many data subjects are affected (approximate volume)?
  3. Will special category data (Article 9) be involved?
  4. Where will processing occur geographically?
  5. 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

#QuestionExpected Response
A1Does your organization have a designated Data Protection Officer (DPO) or equivalent privacy lead?Named individual with contact details
A2In which jurisdictions is your organization established?List of all establishment countries
A3What is your GDPR compliance governance structure?Documented privacy program with assigned responsibilities
A4Have you been subject to any regulatory enforcement actions, fines, or investigations in the past 5 years?Disclosure of any actions with remediation status
A5Do you maintain a Record of Processing Activities per Article 30(2)?Confirmation with sample structure
A6What lawful bases do you rely on for your own processing activities?Documented lawful basis assessment
A7Do you have a process for conducting Data Protection Impact Assessments per Article 35?DPIA methodology description

Section B — Technical Security Controls

#QuestionExpected Response
B1Describe your encryption approach for data at rest and in transitAES-256 for at-rest, TLS 1.2+ for in-transit minimum
B2How do you manage access controls and authentication?RBAC, MFA, principle of least privilege
B3Describe your vulnerability management programRegular scanning, patching cadence, penetration testing
B4What logging and monitoring controls are in place?SIEM, access logging, anomaly detection
B5Describe your incident detection and response capabilities24/7 monitoring, documented IRP, mean time to detect
B6How do you secure development practices?SDLC, code review, OWASP compliance
B7What physical security controls protect data processing facilities?Access controls, CCTV, environmental controls

Section C — Data Handling Practices

#QuestionExpected Response
C1How do you segregate client data from other clients?Logical or physical segregation description
C2What is your data retention and deletion approach?Defined retention periods, certified deletion
C3How do you handle data subject access requests forwarded by controllers?Process description with SLA commitments
C4Describe your data backup and recovery proceduresBackup frequency, encryption, tested recovery
C5Do you process personal data in any country outside the EEA?List of all processing locations with transfer mechanisms
C6What is your sub-processor engagement process?Notification mechanism, assessment requirements

Section D — Certifications and Attestations

#QuestionExpected Response
D1Do you hold ISO 27001 certification?Certificate with scope and certification body
D2Do you hold ISO 27701 certification?Certificate with scope
D3Do you hold SOC 2 Type II attestation?Report with scope and period
D4Do you hold any cloud-specific certifications (CSA STAR, ISO 27017/27018)?Certificate details
D5Do you adhere to any approved GDPR Code of Conduct per Article 40?Code of Conduct reference and adherence documentation
D6Have 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:

  1. Documentation Review: Examine vendor security policies, procedures, and architectural documentation
  2. Certification Verification: Independently verify certification validity with issuing bodies
  3. Technical Testing: Where contractually permitted, conduct or review penetration test results
  4. Reference Checks: Contact existing clients of the vendor regarding privacy practices
  5. Public Record Search: Review breach notification databases, regulatory actions, and news reports

Control Verification Matrix:

Control DomainQuestionnaire ClaimVerification Method
Encryption at restAES-256Review architecture docs, request encryption key management details
Encryption in transitTLS 1.2+Technical scan of vendor endpoints
Access managementRBAC with MFAReview IAM policy documentation
Incident response24/7 SOCReview SOC 2 Type II report findings
Data segregationLogical separationArchitecture review and documentation
Patch managementMonthly cycleReview 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:

CriterionWeightScoring
Legal governance maturity15%1-5 scale
Technical security controls25%1-5 scale
Data handling practices20%1-5 scale
Certifications held15%1-5 scale
Breach and enforcement history10%1-5 scale (inverse)
Sub-processor management10%1-5 scale
Cross-border transfer safeguards5%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:

  1. Completed Privacy Risk Questionnaire with vendor responses
  2. Evidence of verification activities performed
  3. Data flow analysis documentation
  4. Sufficiency scoring worksheet
  5. Written decision with rationale
  6. Approval signature from DPO or designated privacy lead
  7. 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%)

ScoreCriterionDescription
1< 100 data subjectsMinimal volume processing
2100 – 1,000 data subjectsLow volume
31,001 – 10,000 data subjectsModerate volume
410,001 – 100,000 data subjectsHigh volume
5> 100,000 data subjectsVery high volume

Dimension 2: Data Sensitivity (Weight: 25%)

ScoreCriterionDescription
1Pseudonymized non-sensitive data onlyMinimal identifiability
2Non-sensitive personal data (names, email)Standard personal data
3Behavioral data, location data, financial identifiersElevated sensitivity
4Government IDs, precise geolocation, communications contentHigh sensitivity
5Special category data (Art. 9) or criminal convictions (Art. 10)Maximum sensitivity

Dimension 3: Transfer Locations (Weight: 15%)

ScoreCriterionDescription
1Processing exclusively within EEANo transfer risk
2Processing in EEA + adequacy decision countriesMinimal transfer risk
3Processing includes non-adequate countries with robust SCCs and supplementary measuresManaged transfer risk
4Processing in jurisdictions with government surveillance concerns (per EDPB assessments)Elevated transfer risk
5Processing in jurisdictions lacking rule of law / no valid transfer mechanismMaximum transfer risk

Dimension 4: Certifications and Attestations (Weight: 15%)

Inverse scoring — higher certifications reduce risk.

ScoreCriterionDescription
1ISO 27001 + ISO 27701 + SOC 2 Type II + sector-specific certComprehensive certification
2ISO 27001 + SOC 2 Type II (or equivalent combination)Strong certification
3ISO 27001 only or SOC 2 Type II onlyModerate certification
4Self-assessment or CSA STAR Level 1 onlyLimited certification
5No recognized certifications or attestationsNo certification

Dimension 5: Breach and Enforcement History (Weight: 10%)

ScoreCriterionDescription
1No breaches, no enforcement actions in past 5 yearsClean record
2Minor incident(s) with prompt notification and remediationLow incident history
3One significant breach with adequate responseModerate history
4Multiple breaches or one enforcement actionElevated history
5Major enforcement action or pattern of breach non-complianceHigh-risk history

Dimension 6: Control Maturity (Weight: 10%)

ScoreCriterionDescription
1Optimized — continuous improvement, metrics-driven, automated controlsIndustry leading
2Managed — controls measured and monitored, regular testingMature program
3Defined — documented policies and procedures, periodic testingEstablished program
4Developing — basic controls in place, gaps in documentationEmerging program
5Initial — ad hoc controls, minimal documentationImmature program

Dimension 7: Processing Autonomy (Weight: 10%)

ScoreCriterionDescription
1No discretion — purely technical processing per exact instructionsMinimal autonomy
2Limited discretion — predefined processing optionsLow autonomy
3Moderate discretion — processor selects technical meansStandard autonomy
4Significant discretion — processor defines processing logicElevated autonomy
5High discretion — processor approaches controller boundaryMaximum 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

TierScore RangeLabelOversight Level
Tier 13.5 – 5.0High RiskMaximum oversight: annual on-site audit, quarterly monitoring, full due diligence refresh annually
Tier 22.5 – 3.4Standard RiskStandard oversight: annual remote audit, semi-annual monitoring, due diligence refresh biennially
Tier 31.0 – 2.4Low RiskMinimum oversight: biennial documentation audit, annual monitoring, due diligence refresh triennially

Tier-Based Oversight Requirements

ActivityTier 1 (High)Tier 2 (Standard)Tier 3 (Low)
Due diligence refreshAnnualBiennialTriennial
Privacy auditAnnual (Type 2 or 3)Annual (Type 1)Biennial (Type 1)
Sub-processor reviewQuarterlySemi-annualAnnual
DPA reviewAnnualBiennialTriennial
Risk score recalculationSemi-annualAnnualBiennial
Continuous monitoringActive monitoringPeriodic monitoringAnnual check

Scoring Adjustments

Escalation Triggers

The following events trigger automatic tier escalation (one tier up):

TriggerDuration
Personal data breach at vendorUntil post-breach reassessment completed
Regulatory enforcement actionUntil remediation verified
Certification lapse (> 30 days)Until certification renewed
Material service change without prior notificationUntil change assessed
Failed audit (Critical findings)Until remediation verified

De-escalation Criteria

Tier reduction requires:

  1. At least one completed audit cycle at current tier with no Major or Critical findings
  2. Updated certifications covering all processing in scope
  3. DPO approval of tier reduction
  4. Documentation of rationale

Aggregated Vendor Risk Dashboard

Summit Cloud Partners maintains an aggregated view of vendor privacy risk:

MetricDescription
Total vendors processing personal dataCount of active vendor DPAs
Vendors by tierDistribution across Tier 1/2/3
Average risk scoreMean weighted score across all vendors
TrendQuarter-over-quarter score movement
Overdue assessmentsVendors past their scheduled reassessment date
Open audit findingsTotal by severity
Vendors with third-country transfersCount 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

TriggerDescriptionTimeline Considerations
Contract expiry (non-renewal)MSA/DPA term ends without renewal90-day notice per DPA
Termination for convenienceController elects to terminatePer MSA notice period
Termination for causeMaterial DPA breach by processorImmediate or per cure period
Service migrationController moves to alternative providerOverlap period for data migration
Vendor insolvencyProcessor enters insolvency proceedingsEmergency data retrieval
Regulatory orderSupervisory authority orders cessationPer 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 CategoryLocationFormatVolumeRetention Basis
Production dataPrimary databaseStructured (SQL/JSON)[Volume]DPA processing
Backup dataBackup storageEncrypted backup files[Volume]Business continuity per DPA
Log dataLog storageSemi-structured (JSON/text)[Volume]Security monitoring
Derived/aggregated dataAnalytics systemStructured[Volume]Processing output
MetadataVarious systemsStructured[Volume]System operation
Cached dataCDN/cache layersVarious[Volume]Performance

Step 2: Data Export Format and Method

Standard Export Formats:

Data TypePreferred FormatAlternative FormatNotes
Structured dataCSV with defined schemaJSON, XML, ParquetUTF-8 encoding required
DocumentsOriginal format (PDF, DOCX)ZIP archivePreserve directory structure
Images/mediaOriginal format (PNG, JPEG)ZIP archivePreserve metadata
LogsJSON lines (JSONL)CSVInclude timestamps
API-accessible dataDirect API extractionBulk export endpointPaginated if large

Export Methods:

MethodWhen to UseSecurity Requirements
Encrypted file transfer (SFTP)Large datasetsTLS 1.2+, PGP encryption
Secure API extractionStructured, API-accessible dataOAuth 2.0, TLS 1.3
Encrypted portable mediaVery large datasets without bandwidthAES-256 encryption, tracked courier
Cloud-to-cloud migrationCloud provider transitionEncrypted transfer, access audit

Step 3: Data Validation

Upon receiving returned data, Summit Cloud Partners validates:

Validation CheckMethodPass Criteria
CompletenessRecord count comparisonReturned count matches source count
IntegrityChecksum verification (SHA-256)Checksums match vendor-provided manifest
Format complianceSchema validationAll fields present per agreed schema
EncodingCharacter encoding verificationUTF-8 without corruption
Sample verificationRandom sample manual reviewData content matches expectations

Data Deletion Process

Deletion Scope

The processor must delete ALL copies of personal data, including:

  1. Production data — Primary databases and data stores
  2. Backup data — All backup copies including off-site backups
  3. Disaster recovery copies — DR site data
  4. Log data — Application logs, access logs, audit logs containing personal data
  5. Cached data — CDN caches, application caches, database caches
  6. Derived data — Analytics outputs, aggregated data containing personal data
  7. Metadata — System metadata referencing personal data
  8. Archived data — Any archived copies
  9. Sub-processor data — Data at all sub-processors

Deletion Methods

Data LocationDeletion MethodVerification
Databases (SQL)DELETE + VACUUM or DROP TABLEQuery confirmation; storage analysis
Object storage (S3/Blob)Delete all objects + bucketBucket listing verification
File systemsSecure overwrite (NIST 800-88)Disk analysis confirmation
SSD/Flash storageCrypto-erase (destroy encryption key)Vendor attestation
Backup tapesDegaussing or physical destructionDestruction certificate
Application cachesCache flush + TTL expiry confirmationApplication verification
Log systemsTargeted log deletion or retention expiryLog query confirmation
Sub-processorsCascade deletion instructionSub-processor deletion certificate

Deletion Timeline

PhaseActivityDPA Standard Timeline
T+0Controller elects deletion (or return + deletion)Upon termination notice
T+0 to T+30Data return completed (if return elected)30 calendar days
T+30 to T+60Production data deletion60 calendar days from termination
T+60 to T+90Backup and archive deletion90 calendar days from termination
T+90Deletion certification issued90 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:

RequirementProcessor Action
Documented in writingProcessor identifies specific legal requirement
Limited to required dataOnly data subject to legal retention requirement
Isolated from productionRetained data moved to restricted storage
Time-limitedRetained only for legally required duration
Notified to controllerController informed of retention and legal basis

Deletion Certification

The processor must provide a written deletion certification containing:

FieldContent
Certifying partyName and title of authorized processor representative
Controller nameSummit Cloud Partners
DPA referenceReference to terminated DPA
Deletion scopeDescription 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 deletionConfirmation that all sub-processors have also deleted data
ExceptionsAny data retained under legal obligation (with legal basis citation)
Certification dateDate of certification
SignatureAuthorized officer signature

Transition Planning

For service migrations, a transition plan ensures continuity while managing data protection obligations:

PhaseActivityDuration
PlanningDefine data migration scope, format, timeline4-6 weeks
Parallel operationOld and new vendor operate simultaneously2-4 weeks
MigrationData transferred from old to new vendor1-2 weeks
ValidationVerify complete and accurate migration1 week
CutoverSwitch production to new vendor1 day
DecommissionTerminate old vendor; initiate deletionPer DPA timeline
Deletion verificationConfirm old vendor data deletion90 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