Vehicle Identification Number
Detects Vehicle Identification Number patterns. Excludes I, O, Q characters
- Type
- regex
- Engine
- universal
- Confidence
- high
- Confidence justification
- High confidence: validated with Check digit at position 9 (weights: 8,7,6,5,4,3,2,10,0,9,8,7,6,5,4,3,2) and supported by corroborative keyword evidence. Added context gating and exclusion rules improve precision and reduce incidental matches.
- Detection quality
- Verified
- Jurisdictions
- global
- Frameworks
- CIS Controls, ISO 27001, NIST CSF, SOC 2
- Data categories
- device-id
- Scope
- specific
- Risk rating
- 6
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Compatible, Netskope: Compatible
Pattern
\b[A-HJ-NPR-Z0-9]{17}\bCorroborative evidence keywords
device, identifier, serial number, hardware, ID number, identification, ID card, license, permit, registration, certificate, field, column, row, entry, record, value, form, register, database (+19 more)
Proximity: 300 characters
Should match
1HGBH41JXMN109186— Honda Civic VIN (excludes I, O, Q)WVWZZZ3CZWE123456— Volkswagen Golf VIN5YJSA1E26MF123456— Tesla Model S VIN
Should not match
1HGBH41JXMN10918— Only 16 characters instead of 171HGBH41JXMN1091861— 18 characters instead of 171HGBH4IJXMN109186— Contains letter I (excluded from VIN)template example placeholder record identifier— Template/sample context should be excluded even when anchor words are present
Known false positives
- Technical identifiers appearing in public documentation, network configuration guides, or example configurations without representing actual infrastructure. Mitigation: Cross-reference with known documentation patterns and reserved address ranges. Require proximity to infrastructure-specific context.
- Placeholder and example values commonly used in technical tutorials and vendor documentation. Mitigation: Maintain exclusion lists for well-known example values (RFC 5737 documentation addresses, example MAC addresses).