Δελτίο Ταυτότητας
Detects Δελτίο Ταυτότητας 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, cy
- 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\d{8}\bCorroborative evidence keywords
δελτίο ταυτότητας, identity card, kimlik, ID number, identification, ID card, license, permit, registration, certificate, data record, database record, record set, data extract, data export, database table, spreadsheet, data registry, registry entry, master data (+13 more)
Proximity: 300 characters
Should match
12345678— Eight-digit Cypriot ID card98765432— Another Cypriot ID card45678901— Valid format Cypriot ID
Should not match
1234567— Too few digits (7)123456789— Too many digits (9)template example placeholder record identifier— Template/sample context should be excluded even when anchor words are present
Known false positives
- Eight-digit numeric sequences are extremely common in dates, phone numbers, and other non-identity contexts. Mitigation: Require corroborative evidence keywords in Greek, Turkish, or English 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.