國民身分證統一編號
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
- high
- Confidence justification
- High confidence: pattern has strong structural constraints (specific format, prefix, or character class restrictions) that significantly reduce false positive rates. Added context gating and exclusion rules improve precision and reduce incidental matches.
- Detection quality
- Verified
- Jurisdictions
- tw
- Frameworks
- ISO 27001, ISO 27701
- 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[A-Z][12]\d{8}\bCorroborative evidence keywords
身分證, national ID, 統一編號, ID number, identification, ID card, license, permit, registration, certificate, field, column, row, entry, record, value, form, register, database, extract (+19 more)
Proximity: 300 characters
Should match
A123456789— Taiwan ID (male, Taipei)B234567890— Taiwan ID (female, Taichung)F198765432— Taiwan ID (male, New Taipei)
Should not match
A312345678— Invalid gender digit (3)1A23456789— Letter not in first positiontemplate example placeholder record identifier— Template/sample context should be excluded even when anchor words are present
Known false positives
- The letter-digit-8digits format with gender constraint (1 or 2) provides good structural validation. Mitigation: The structured format with region letter and gender digit reduces false positives. Keyword context further improves accuracy.
- 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.