Whistleblower identity records

Identifies records that reveal a whistleblower's identity - public interest / protected disclosure intake and case records, whistleblower reports and discloser identity registers - when the disclosure phrase sits with populated discloser identifiers and disclosure case fields.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: Medium: enforce tiers need a populated discloser identifier or case reference; 85 also needs a disclosure field and protection evidence. PID procedures, annual reporting and news stay at 65.
Detection quality: Topic false positive
Jurisdictions: global
Regulations: Public Interest Disclosure Act 2010 (Qld), Public Interest Disclosure Act 2013 (Cth), Corporations Act 2001 (Cth), Privacy Act 1988 (Cth), Information Privacy Act 2009 (Qld), 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

(?i)\b(?:(?:whistleblower|discloser)\s+identity|protected\s+disclosure(?:\s+(?:record|report|register|file))?|public\s+interest\s+disclosure|(?:qualifying|confidential)\s+disclosure|whistleblower\s+report|eligible\s+whistleblower)\b

Corroborative evidence keywords

reprisal, detrimental action, strictly confidential, eligible recipient, Ombudsman, Crime and Corruption Commission

Proximity: 300 characters

Should match

PUBLIC INTEREST DISCLOSURE - intake record PID reference: PID-2026-0417 Discloser name: Avery Teston Position: Senior Procurement Officer Work unit: Regional Contracts Date received: 12/08/2026 Alleged wrongdoing: Contract splitting to avoid tender thresholds Reprisal risk rating: High - identity must not be disclosed to the subject officer. — Populated PID intake record with discloser, disclosure fields and protection evidence (85)
Whistleblower report received Case number: WB-88120 Contact phone: 0412 345 678 — Whistleblower report with a labelled case reference and contact only (75)
Protected disclosure register - entry 2026/031 (STRICTLY CONFIDENTIAL) Disclosure ref: PD-031 Whistleblower name: Jordan Kestrel Employee number: 118802 Received by: Ethics and Integrity Unit, eligible recipient Subject officer: Fleet Services Manager Referred to: Crime and Corruption Commission on 09/10/2026 Identity must not be disclosed outside the case team. — Disclosure register entry with whistleblower name, employee number, received by, subject officer and referral plus protection evidence (85)

Should not match

unrelated generic text without domain phrases — No relevant topic phrases present
placeholder value 12345 — Random text should not match topic-specific regex
employee interview — Generic word pair from old broad template should not match
Policy guidance: this procedure explains how public interest disclosure records are collected, stored and shared, who may access them and how long they are kept. Staff should read the privacy section before completing any form. It contains no details about any individual. — Policy/guidance text naming the topic without any populated record (65 discovery at most)
Protected disclosure intake form Discloser name: ____________________ Position: ____________________ Date received: ____________________ Alleged wrongdoing: ____________________ Signature: ____________ Date: __/__/____ — Blank form with unpopulated labelled fields (placeholder guard keeps it below 75)
News: the Ombudsman's annual report shows public interest disclosure numbers rose, and agencies were reminded that whistleblower identity must be protected from reprisal. — News/training prose about the topic without a populated record (65 discovery at most)

Known false positives

Common words and phrases related to whistleblower identity 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 Australian English, 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.