Breach notification draft communications
Identifies documents containing references to breach notification draft communications in international contexts. Sensitive pre-release breach communications may contain personal-impact data — incident scope, affected individuals and groups, regulator engagement, and unverified legal conclusions; the matched phrases are not themselves personally identifiable information.
- Type
- regex
- Engine
- boost_regex
- Confidence
- medium
- Confidence justification
- category-aware structural regex with anchor and context constraints replaces phrase-only detection. Added context gating and exclusion rules improve precision and reduce incidental matches.
- Detection quality
- Topic false positive
- Jurisdictions
- global
- Regulations
- GDPR
- Frameworks
- ISO 27001, ISO 27701
- Data categories
- pii
- Scope
- wide
- Risk rating
- 8
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported
Pattern
(?is)\b(?:breach\s+notification\s+draft\s+communications|breach\s+notification|data\s+breach|notifiable\s+data\s+breach|affected\s+individuals|notification\s+letter|breach\s+assessment|incident\s+response|privacy\s+commissioner|mandatory\s+reporting|eligible\s+data\s+breach|remediation\s+steps)\bCorroborative evidence keywords
breach notification draft communications, breach, notification, draft, communications, corporate, legal, governance
Proximity: 300 characters
Should match
breach notification draft communications— Primary topic phrase matchbreach notification— Case-insensitive topic phrase matchdata breach— Alternative topic phrase matchnotifiable data breach— Additional topic phrase matchBreach notification draft communications To: Executive Committee From: Chief Financial Officer Date: 14 August 2026 Subject: Breach notification draft communications - FY27 review— Populated document header reaching the 75/85 structure gate
Should not match
unrelated generic text without domain phrases— No relevant topic phrases presentplaceholder value 12345— Random text should not match topic-specific regexboard policy— Generic word pair from old broad template should not matchBreach notification draft communications: To: From: Date: Subject:— Empty form: the heading and field labels without values must not corroborate themselves (discovery only)Policy guidance: this procedure explains how records about breach notification draft communications are handled, who may access them and how long they are kept. It contains no records about any person or system.— Policy guidance naming the topic without any record (discovery only)
Known false positives
- Common words and phrases related to breach notification draft communications appearing in policy documents, training materials, HR templates, or compliance guidelines without actual personal data. Mitigation: Require corroborative evidence keywords within the proximity window to confirm sensitive data context rather than general discussion.
- In English (as the primary international business language), similar terminology used in formal or administrative contexts (education, professional documentation) that does not constitute sensitive data collection. Mitigation: Layer with additional contextual signals such as structured identifiers, form fields, or database column headers to distinguish sensitive records from general references.
- High-frequency pattern matches in large document corpora due to broad regex anchors. Expected match rate is significantly higher than specific identifier patterns. Mitigation: Tune confidence thresholds for bulk scanning. Consider using this pattern primarily as a pre-filter with secondary validation.