TAJ szám
Detects TAJ szám 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, hu
- Regulations
- BDSG, CNIL / LIL, GDPR
- 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\d{3}\s?\d{3}\s?\d{3}\bCorroborative evidence keywords
TAJ, társadalombiztosítási, social security, 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
123 456 789— TAJ number with spaces987654321— TAJ number without spaces456 789 012— Another spaced TAJ number
Should not match
12345678— Too few digits (8)1234567890— Too many digits (10)template example placeholder record identifier— Template/sample context should be excluded even when anchor words are present
Known false positives
- Nine-digit sequences with optional spaces match phone numbers, postal codes, and other numeric references. Mitigation: Require corroborative evidence keywords such as "TAJ" or "társadalombiztosítási" 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.