Personalausweis

Detects Personalausweis patterns. This pattern is based on a Microsoft Purview built-in sensitive information type. Users already running Purview may prefer to enable the built-in SIT directly, or use this version as a starting point for customisation.

Type: regex
Engine: universal
Confidence: medium
Confidence justification: Medium confidence: pattern has structural constraints but corroborative keywords are recommended to reduce false positive rates. Added context gating and exclusion rules improve precision and reduce incidental matches.
Detection quality: Verified
Jurisdictions: eu, de
Regulations: GDPR
Data categories: pii, government-id
Scope: narrow
Risk rating: 9
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Compatible, Netskope: Compatible

Pattern

\b[CFGHJKLMNPRTVWXYZ][CFGHJKLMNPRTVWXYZ0-9]{8}\d?\b

Corroborative evidence keywords

identifier, number, ID, ID number, identification, ID card, license, permit, registration, certificate, field, column, row, entry, record, value, form, register, database, extract (+16 more)

Proximity: 300 characters

Should match

CF1234567 — German identity card number
LM9876543 — Alternate ID card format
T12345678 — Newer format with check digit

Should not match

A12345678 — Invalid first character (A not in allowed set)
CF123456 — Only 7 characters after first instead of 8
CF12345678A — Too many characters (11 instead of 9-10)
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 personalausweis 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 multiple EU languages, 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.

References

Germany identity card number entity definition - Microsoft Learn