Kartu Tanda Penduduk (KTP)
Detects Kartu Tanda Penduduk (KTP) 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
- id
- 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{16}\b
Corroborative evidence keywords
KTP, kartu tanda penduduk, NIK, identity card, ID number, identification, ID card, license, permit, registration, certificate, field, column, row, entry, record, value, form, register, database (+20 more)
Proximity: 300 characters
Should match
3201011234567890— KTP from West Java province3175011234567890— KTP from DKI Jakarta5101011234567890— KTP from Bali province
Should not match
320101123456789— Too few digits (15)32010112345678901— Too many digits (17)template example placeholder record identifier— Template/sample context should be excluded even when anchor words are present
Known false positives
- Sixteen-digit numeric sequences may match credit card numbers, long account numbers, or barcodes. Mitigation: Require corroborative evidence keywords such as "KTP", "NIK", or "kartu tanda penduduk" 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.