# What should a data breach response plan include?

Guide, read 16 November 2026

**The short answer.** A data breach response plan should include a written policy, a map of where personal data lives, monitoring, training, a response sequence from validation to notification, and notice content that meets the law. This page, read on 16 November 2026, gives the checklist drawn from PTAC, HIPAA and GDPR.

## What should a data breach response plan include?

It should include the building blocks the PTAC checklist lists for use before a breach, and the response steps it lists during one. Before: a written breach response policy; a review of where personally identifiable information is stored, including backups and archives; continuous monitoring for leakage; and recurring training.

During: validate the breach, determine its scope and composition, notify the data owners, decide whether to notify law enforcement, and decide whether and how to notify affected individuals. PTAC says the checklist is not linear and that some activities happen at once.

1. Written breach policy and named breach team with a deputy.
2. Data map: what, where, who has access.
3. Monitoring and loss detection.
4. Recurring staff training.
5. Validate and scope the breach.
6. Notify data owners.
7. Decide on law enforcement.
8. Decide on, write and send notices.
9. Document and review.

## What must the notice itself contain?

The content lists in the sources agree on the core. HIPAA 164.404(c) requires a brief description of what happened with dates, the types of information involved, steps individuals should take, what the entity is doing, and contact procedures including a toll-free number, email address, website or postal address, in plain language.

GDPR Article 33(3) requires the nature of the breach with categories and approximate numbers of people and records, a contact point, likely consequences and the measures taken or proposed.

| Element | HIPAA 164.404(c) | GDPR 33(3) |
| --- | --- | --- |
| What happened | Yes, with dates | Nature, categories and numbers |
| Data involved | Types of information | Categories of records |
| Advice to people | Steps to protect themselves | Via Article 34 for individuals |
| Our response | Investigation, mitigation, prevention | Measures taken or proposed |
| Contact | Toll-free number, email, website or postal address | Name and contact of DPO or contact point |
| Consequences | Not listed | Likely consequences |

What must the notice itself contain?

## Does a breach plan have to be separate?

Not necessarily. Many organizations keep one incident response plan with a breach section. Keeping a [separate template](/data-breach/data-breach-response-plan-template/) is useful when a privacy team owns the notification decision. See the [overview](/data-breach/) for the seven parts.

## Related pages

- [Data breach response plan: what it is and how to write one](/data-breach/)
- [Free incident response plan template](/)
- [Data breach response plan template](/data-breach/data-breach-response-plan-template/)
- [Data breach response plan under GDPR](/data-breach/data-breach-response-plan-gdpr/)
- [Incident response plan templates: the full set](/templates/)
- [Incident response plan: what it contains and how to build one](/plans/)

## Sources

- U.S. Department of Education PTAC, Data Breach Response Checklist (September 2012): https://studentprivacy.ed.gov/sites/default/files/resource_document/file/checklist_data_breach_response_092012_0.pdf (read 16 November 2026)
- eCFR, 45 CFR 164.404, Notification to individuals: https://www.ecfr.gov/current/title-45/section-164.404 (read 16 November 2026)
- Regulation (EU) 2016/679 (GDPR), EUR-Lex: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32016R0679 (read 16 November 2026)

Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/data-breach/what-should-a-data-breach-response-plan-include/
