Uimhir PSP
Detects Uimhir PSP 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, ie
- 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{7}[A-Z]{1,2}\b
Corroborative evidence keywords
PPS, personal public service, RSI, 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
1234567A— PPS number with single check letter9876543AB— PPS number with two check letters4567890W— Another PPS number format
Should not match
123456A— Too few digits (6)1234567— Missing check lettertemplate example placeholder record identifier— Template/sample context should be excluded even when anchor words are present
Known false positives
- Seven digits followed by one or two letters may match postal codes, reference numbers, or product codes. Mitigation: Require corroborative evidence keywords such as "PPS" or "personal public service" 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.