Australian Citizenship Certificate
Detects Australian Citizenship Certificate number patterns including prefixed formats (ACC, CDM, ACS, CAS followed by 4-8 digits) and numeric-only formats (0 + 10 digits).
- Type
- regex
- Engine
- universal
- Confidence
- medium
- Confidence justification
- Medium confidence: the 3-letter prefix (ACC, CDM, ACS, CAS) provides good structural specificity. Corroborative keywords are recommended to distinguish from other prefixed reference codes.
- Jurisdictions
- au
- Regulations
- AML/CTF Act (Cth), IPA 2009 (Qld), NDB Scheme (Cth), Privacy Act 1988 (Cth)
- Frameworks
- ISO 27001
- Data categories
- pii, government-id
- Scope
- narrow
- Risk rating
- 8
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Compatible, Netskope: Unsupported
Pattern
\b(?:ACC|CDM|ACS|CAS)\s?\d{4,8}\b
Corroborative evidence keywords
citizenship, citizenship certificate, Australian citizen, evidence number, stock number, naturalisation, naturalization, certificate of citizenship, immigration, Home Affairs, visa grant, visa subclass, ID number, identification, ID card, license, permit, registration, certificate
Proximity: 300 characters
Should match
ACC12345678— Citizenship certificate ACC prefix with 8 digitsCDM 1234— CDM prefix with space and 4 digitsACS56789— ACS prefix certificate number with 5 digits
Should not match
XYZ12345— Invalid prefix (XYZ instead of ACC/CDM/ACS/CAS)ACC123— Too few digits after prefix (3 instead of 4-8)ACC123456789— Too many digits after prefix (9 instead of 4-8)
Known false positives
- Common words and phrases related to australian citizenship certificate 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.