BSN
Detects BSN 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. Context label evidence plus explicit template/example exclusion improves precision for high-risk identifiers.
- Detection quality
- Verified
- Jurisdictions
- eu, nl
- 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{8,9}\bCorroborative evidence keywords
identifier, number, ID, ID number, identification, ID card, license, permit, registration, certificate
Proximity: 300 characters
Should match
123456789— Standard 9-digit BSN12345678— 8-digit BSN999999999— Upper-range BSN
Should not match
1234567— Only 7 digits (below minimum of 8)1234567890— 10 digits (above maximum of 9)12345678A— Contains a letter instead of all digitssample template placeholder number 123456789— Template/sample context should be excluded even when numeric-like values appear
Known false positives
- Common words and phrases related to bsn appearing in policy documents, training materials, HR templates, or compliance guidelines without actual personal data. Mitigation: Require corroborative evidence keywords within the proximity window to confirm sensitive data context rather than general discussion.
- In multiple EU 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.