GDPR Vendor Management Compliance Checklist
Last updated: 2026-04-28 — ComplianceStack Editorial Team
Generate Your Personalized GDPR Checklist
Tell us about your organization and we'll tailor this 20-item checklist to your situation — highlighting your gaps, marking what you already have, and calculating your readiness score. Free. Instant. Downloadable.
GDPR Article 28 imposes strict requirements on controllers when engaging processors to handle personal data, including mandatory Data Processing Agreements (DPAs), due diligence obligations, and liability for processor non-compliance. Organizations face fines up to €20 million or 4% of annual global turnover under Article 83(4)(a) for failing to use processors providing sufficient guarantees or for unauthorized sub-processor engagement. This checklist covers vendor assessment, DPA requirements, sub-processor management, international transfer mechanisms, and ongoing monitoring obligations for GDPR-compliant vendor relationships.
Generate Your Personalized Checklist
Tell us about your vendor management and we'll filter this checklist to what applies to you — with a readiness score and priority gaps highlighted.
📄 Reference Checklist
Generic — use the generator above for a personalized versionGDPR Reference Checklist for Vendor Management
SEO ReferenceUse the generator above for your personalized checklist. The complete reference checklist is below.
GDPR Compliance Checklist for Vendor Management
Conduct pre-contract data protection due diligence on all vendors
Before engaging any processor, assess their technical and organizational measures, security certifications (ISO 27001, SOC 2), previous data breaches, and GDPR compliance capabilities. Document findings and approval decision.
Execute written Data Processing Agreements with all processors
Ensure all processors sign written DPAs before processing begins, containing all mandatory elements under Article 28(3): subject matter, duration, nature and purpose of processing, type of personal data, categories of data subjects, controller obligations and rights.
Include processor obligations to process only on documented instructions
DPA must specify that processor will process personal data only on documented instructions from controller, including transfers to third countries. Include procedures for processor to inform controller if instructions violate GDPR or Member State law.
Require confidentiality commitments from all processor personnel
DPA must mandate that all processor employees, contractors, and agents authorized to process personal data are subject to legally binding confidentiality obligations or professional duty of confidentiality.
Specify technical and organizational security measures in DPA
Document specific security measures processor must implement per Article 32, including encryption, pseudonymization, access controls, security testing frequency, and incident response procedures. Reference processor's security certifications.
Establish sub-processor authorization and notification requirements
Define whether controller provides specific or general authorization for sub-processors. For general authorization, require processor to inform controller of any sub-processor changes with minimum 30-day notice and right to object.
Maintain current sub-processor registry for each vendor
Require processors to provide and maintain an up-to-date list of all sub-processors, including name, location, processing activities, and applicable data protection measures. Review and approve each sub-processor per DPA terms.
Ensure sub-processor agreements impose same data protection obligations
Verify that processor imposes the same data protection obligations from your DPA onto sub-processors through written sub-processing agreements. Processor remains fully liable to controller for sub-processor performance.
Include processor assistance obligations for data subject rights
DPA must require processor to assist controller in responding to data subject requests (access, rectification, erasure, portability) by appropriate technical and organizational measures, considering the nature of processing.
Require processor assistance with security and breach obligations
DPA must obligate processor to assist controller in ensuring Article 32 security compliance, conducting DPIAs under Article 35, and prior consultations with supervisory authorities under Article 36.
Establish data breach notification timeline from processor
DPA must require processor to notify controller without undue delay and within specified timeframe (recommended: 24 hours) after becoming aware of a personal data breach, with sufficient detail to assess Article 33 notification obligations.
Define data deletion or return obligations upon contract termination
DPA must specify that processor deletes or returns all personal data to controller at controller's choice after end of provision of services, and deletes existing copies unless storage required by EU or Member State law.
Include audit rights and information provisions in DPA
DPA must grant controller and auditors the right to conduct audits and inspections of processor facilities and records. Specify audit frequency, notice period, scope, and processor cooperation obligations. Require annual third-party audit reports.
Implement international transfer mechanisms for non-EEA vendors
For processors located outside EEA or using non-EEA sub-processors, implement valid transfer mechanisms: adequacy decisions, Standard Contractual Clauses (SCCs), Binding Corporate Rules, or certification mechanisms. Conduct Transfer Impact Assessments.
Execute EU Standard Contractual Clauses for non-adequate transfers
Use the European Commission's 2021 SCCs (Decision 2021/914) for transfers to third countries without adequacy decisions. Complete all modules and annexes appropriate to controller-processor relationship. Conduct and document Transfer Impact Assessments.
Conduct Transfer Impact Assessments for international vendors
Assess whether destination country laws enable public authority access that undermines SCC protections. Document assessment of legal framework, practical experience, and supplementary measures. Follow EDPB Recommendations 01/2020.
Maintain vendor inventory in Records of Processing Activities
Document all processors and categories of recipients in Article 30 ROPA, including processor name, processing activities, location, transfer mechanisms if applicable, and DPA execution date.
Conduct annual vendor compliance reviews and audits
Review each processor's continued compliance with DPA obligations annually. Collect SOC 2/ISO 27001 reports, review security incident reports, verify sub-processor list accuracy, and assess any material changes to processing activities.
Establish vendor offboarding and data deletion verification
Create documented procedures to terminate vendor access, verify data deletion per Article 28(3)(g), obtain written certification of deletion, and update ROPA. Test procedures with sample vendor quarterly.
Train procurement and legal teams on GDPR vendor requirements
Provide training to procurement, legal, and business teams on Article 28 requirements, DPA negotiation, vendor due diligence, and escalation procedures. Update training annually to reflect enforcement trends and regulatory guidance.
See How Your Vendor Management Scores on GDPR
Run a free gap analysis to find out which items you have covered and where the risks are.
Gap Analyzer → Training Tracker →Common Mistakes That Trigger Enforcement
Frequently Asked Questions
What's the difference between a processor and a controller under GDPR, and why does it matter for vendor management?
Controllers determine the purposes and means of processing (Article 4(7)) while processors process personal data on behalf of controllers (Article 4(8)). This distinction is critical because Article 28 imposes mandatory DPA requirements only on controller-processor relationships. If a vendor determines 'why' or 'how' data is processed, they are a joint controller requiring Article 26 agreements instead. Misclassifying controllers as processors leaves you without proper legal safeguards and potentially liable for their violations. The EDPB guidelines on controller/processor concepts provide detailed examples for classification.
Can we use processors located in the United States after the Schrems II decision?
Yes, but only with valid transfer mechanisms and documented Transfer Impact Assessments. The CJEU Schrems II decision (C-311/18, July 2020) invalidated the EU-US Privacy Shield but upheld Standard Contractual Clauses as a valid transfer mechanism under Article 46(2)(c). However, you must assess whether US laws (particularly FISA Section 702 and Executive Order 12333) create risks that SCCs cannot mitigate per EDPB Recommendations 01/2020. The new EU-US Data Privacy Framework (adequacy decision adopted July 2023) provides an alternative for certified US organizations, but many processors have not yet certified. Document your analysis and implement supplementary measures where necessary.
Who is liable if our processor causes a data breach - us or the processor?
Both can be liable under GDPR's joint and several liability framework. Article 82(2) states controllers are liable for damage caused by processing that violates their obligations, while Article 82(3) makes processors liable for damage when they fail to comply with processor-specific obligations or act outside lawful instructions. Article 82(4) provides joint and several liability, meaning data subjects can claim full compensation from either party. Controllers must conduct due diligence per Article 28(1) and can only escape liability by proving they are not responsible for the damage per Article 82(3). The Hamburg DPA fined a controller €195,000 in 2020 for a processor's data breach, reasoning the controller failed to ensure sufficient guarantees.
✉ Save This Checklist
Enter your email and we'll send you a clean copy — plus updates when requirements change.
We also offer a free personalized gap analysis for your specific situation.
Related Resources
- Complete GDPR Framework Guide
- GDPR for SaaS Companies
- GDPR Tier 1 Fines
- GDPR Tier 2 Fines
- HIPAA Compliance Checklist for Dental Practices
- HIPAA Compliance Checklist for Mental Health Providers
- HIPAA Compliance Checklist for Pharmacies
- Free Compliance Gap Analyzer
- Employee Training Tracker
- 5-Minute Compliance Quiz