Dowód osobisty

Detects Dowód osobisty 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, pl
Regulations: BDSG, CNIL / LIL, GDPR
Frameworks: ISO 27001, ISO 27701
Data categories: pii, government-id
Scope: narrow
Risk rating: 7
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Compatible, Netskope: Compatible

Pattern

\b[A-Z]{3}\d{6}\b

Corroborative evidence keywords

dowód osobisty, identity card, ID card, ID number, identification, license, permit, registration, certificate, field, column, row, entry, record, value, form, register, database, extract, export (+18 more)

Proximity: 300 characters

Should match

ABC123456 — Polish ID card with three-letter series
XYZ987654 — Another Polish ID card
MNO456789 — Valid format Polish ID

Should not match

AB123456 — Only two letters
ABC12345 — Only five digits
template example placeholder record identifier — Template/sample context should be excluded even when anchor words are present

Known false positives

Three uppercase letters followed by six digits may match airline booking codes, tracking numbers, or product serial numbers. Mitigation: Require corroborative evidence keywords such as "dowód osobisty" or "identity card" within the proximity window.
In multiple 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

Poland Identity Card entity definition - Microsoft Learn