Get Demo
↑

GDPR Data Processing Agreement (Article 28): Template and Checklist

Article 28 requires a binding processor contract covering instructions, security, sub-processors, assistance with rights, breach notice.

Published: September 2026 Compliance · GDPR 8–12 min read

When a processor processes personal data on a controller’s behalf, Article 28 requires a binding contract (the Data Processing Agreement). Controllers must use only processors that provide sufficient guarantees.

CyberSilo’s own processor terms live at cybersilo.tech/dpa. This page is the educational template/checklist for your broader vendor estate.

Related: GDPR hub · GDPR for SaaS · RoPA.

Art 28 essentials: documented instructions, confidentiality, Art 32 security, sub-processor authorisation and flow-down, assistance with rights/DPIA/breach, audit/information rights, and deletion or return at end of service.

Article 28 Checklist

Template Section Headings

Use these headings in counsel-reviewed agreements: Definitions · Processing details (annex) · Instructions · Security · Sub-processors · International transfers (Chapter V) · Assistance · Breach notice timelines · Audit · Term & deletion · Liability / insurance (commercial).

How CyberSilo Helps

Close the Processor Contract Gap

Inventory processors, attach Art 28 DPAs, and track sub-processor changes before the next supervisory review.

Frequently Asked Questions

Is a click-through ToS enough?

Only if it includes the Article 28 mandatory content and is binding. Many SaaS ToS packages need a dedicated DPA annex.

Who notifies the supervisory authority of a breach?

Controllers notify under Article 33. Processors must notify the controller without undue delay after becoming aware.

Where is CyberSilo’s DPA?

https://cybersilo.tech/dpa

GDPR hub · CyberSilo DPA · SaaS obligations · Transfers · CSA

📰 More from CyberSilo

Latest Articles

Stay ahead of evolving cyber threats with our expert insights

Fintech Compliance Automation: Multi-Jurisdiction Requirements (PCI, SOC 2, GDPR, MAS, SAMA)
Compliance
Oct 11, 2026 ⏱ 17 min

Fintech Compliance Automation: Multi-Jurisdiction Requirements (PCI, SOC 2, GDPR, MAS, SAMA)

Harmonize fintech compliance across PCI DSS, SOC 2, GDPR, MAS, and SAMA CSF with unified controls and Compliance Standards Automation.

Read Article
How MSSPs Help Clients Achieve PCI DSS Compliance at Scale
Compliance
Oct 11, 2026 ⏱ 15 min

How MSSPs Help Clients Achieve PCI DSS Compliance at Scale

Learn how MSSPs deliver PCI DSS Requirement 10 and audit-ready evidence at scale with ThreatHawk MSSP SIEM and Compliance Standards Automation.

Read Article
The 5 Biggest Operational Mistakes MSSPs Make When Managing Multiple Client SOCs
Partners
Oct 11, 2026 ⏱ 15 min

The 5 Biggest Operational Mistakes MSSPs Make When Managing Multiple Client SOCs

Avoid the top MSSP multi-tenant SOC mistakes—customization sprawl, weak isolation, alert floods, shallow QBRs, and sloppy onboarding—with ThreatHawk MSSP SIEM and Agentic SOC AI.

Read Article
What Is ISO 27001? A Practical 2026 Guide for Security and GRC Teams
Compliance
Oct 11, 2026 ⏱ 16 min

What Is ISO 27001? A Practical 2026 Guide for Security and GRC Teams

ISO/IEC 27001 explained for 2026: ISMS scope, Annex A controls, certification stages, and how continuous monitoring supports audit-ready evidence.

Read Article
What Is the NIST Cybersecurity Framework? CSF 2.0 Explained for 2026
Compliance
Oct 11, 2026 ⏱ 15 min

What Is the NIST Cybersecurity Framework? CSF 2.0 Explained for 2026

The NIST Cybersecurity Framework (CSF) 2.0 explained: six Functions, Profiles, Tiers, and how to operationalize outcomes with SIEM and GRC in 2026.

Read Article
How NIST Helps Cybersecurity Programs Mature in 2026
Compliance
Oct 11, 2026 ⏱ 14 min

How NIST Helps Cybersecurity Programs Mature in 2026

How NIST publications improve cybersecurity: CSF 2.0, SP 800-53, incident guidance, and practical ways to turn NIST outcomes into SOC metrics and audit evidence.

Read Article
✅ Link copied!