Call detail record datasets

Identifies documents containing references to call detail record datasets in Australian contexts. This information type is classified as personally identifiable information under the Privacy Act 1988.

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: Anti-Money Laundering and Counter-Terrorism Financing Act 2006 (Cth), Information Privacy Act 2009 (Qld), NDB Scheme (Cth), Privacy Act 1988 (Cth), GDPR
Frameworks: ISO 27001
Data categories: government-id, 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(?:call\s+detail\s+record\s+datasets|call\s+detail\s+record|CDR\s+data|telecommunications\s+metadata|call\s+log|phone\s+records|metadata\s+retention|subscriber\s+data|communications\s+data|law\s+enforcement|call\s+history|telephony\s+records)\b

Corroborative evidence keywords

call detail record datasets, call, detail, record, datasets, law, enforcement, justice, government, agency, department, ministry, public sector, civil service, welfare, social services, public administration, statutory authority, regulatory body, public servant (+27 more)

Proximity: 300 characters

Should match

call detail record datasets — Primary topic phrase match
call detail record — Case-insensitive topic phrase match
CDR data — Alternative topic phrase match
telecommunications metadata — Additional topic phrase match
Call detail record datasets 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 present
placeholder value 12345 — Random text should not match topic-specific regex
mugshot victim — Generic word pair from old broad template should not match
Call detail record datasets: 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 call detail record datasets 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 call detail record datasets 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.