SIM card identifiers

Identifies documents containing references to sim card identifiers in Australian contexts. This information type is classified as personally identifiable information under applicable data protection regulations.

Type

regex

Engine

boost_regex

Confidence

medium

Confidence justification

identifier/document-structure anchored regex with constrained context replaces phrase-only detection. Added context gating and exclusion rules improve precision and reduce incidental matches.

Detection quality

Mixed

Jurisdictions

global

Regulations

AML/CTF Act (Cth), HRIPA (Cth), IPA 2009 (Qld), My Health Records Act 2012 (Cth), NDB Scheme (Cth), Privacy Act 1988 (Cth), TIA Act 1979 (Cth)

Frameworks

ISO 27001, ISO 27701

Data categories

pii

Scope

wide

Platform compatibility

Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:sim\s+card\s+identifiers)\b\s{0,80}\b[A-Z0-9][A-Z0-9\-/ ]{4,24}\b

Corroborative evidence keywords

sim card identifiers, sim, card, identifiers, contact, location, data, ID, identifier, number, reference, code, index, serial, account, file number, case number, record number, ref, field (+16 more)

Proximity: 300 characters

Should match

• SIM card identifiers — Exact phrase marker match
• sim card identifiers — Case-insensitive phrase match
• SIM card identifiers — Normalized whitespace phrase
• structured record with identifier and contextual anchors — Structural anchor sample

Should not match

• unrelated generic text — No relevant phrase context
• placeholder value 12345 — Random text should not match phrase marker
• generic narrative without identifier/document anchors — Should not match plain mention
• template example placeholder record identifier — Template/sample context should be excluded even when anchor words are present

Known false positives

• Common words and phrases related to sim card identifiers 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.

References

• https://www.oaic.gov.au/privacy/your-privacy-rights/your-personal-information/what-is-personal-information
• https://www.oaic.gov.au/privacy/your-privacy-rights/your-personal-information/what-is-sensitive-information
• https://www.oaic.gov.au/privacy/australian-privacy-principles-guidelines
• https://www.service.nsw.gov.au/transaction/check-a-vehicle-registration
• https://www.gsma.com/get-involved/working-groups/terminal-steering-group/imei-database/
• https://www.itu.int/rec/T-REC-E.118.1/en