Whistleblower protection case records
Identifies documents containing references to whistleblower protection case records in international contexts. This information type is classified as personally identifiable information under applicable data protection regulations.
- 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(?:whistleblower\s+protection\s+case\s+records|whistleblower\s+protection|protected\s+disclosure|public\s+interest\s+disclosure|complainant\s+identity|anonymous\s+report|integrity\s+commission|disclosure\s+officer|reprisal\s+protection|whistleblowing\s+scheme)\b
Corroborative evidence keywords
whistleblower protection case records
Proximity: 240 characters
Should match
whistleblower protection case records— Primary topic phrase matchwhistleblower protection— Case-insensitive topic phrase matchprotected disclosure— Alternative topic phrase matchpublic interest disclosure— Additional topic phrase matchWhistleblower protection case records Name: Avery Teston Date of birth: 14/02/1988 Client number: C4471820— Populated person/client record 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 regexvoter sovereign debt— Generic word pair from old broad template should not matchWhistleblower protection case records: Name: Date of birth:— Empty form: the heading and field labels without values must not corroborate themselves (discovery only)Policy guidance: this procedure explains how records about whistleblower protection case records 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 whistleblower protection case records 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.