Registro Geral
Detects Registro Geral 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
- br
- Regulations
- LGPD
- 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{2}\.?\d{3}\.?\d{3}-?\d\bCorroborative evidence keywords
RG, registro geral, identidade, ID number, identification, ID card, license, permit, registration, certificate, data record, database record, record set, data extract, data export, database table, spreadsheet, data registry, registry entry, master data (+13 more)
Proximity: 300 characters
Should match
12.345.678-9— RG with dots and dash123456789— RG without separators98.765.432-1— Another formatted RG
Should not match
12.345.678— Missing check digit1234567890— 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 numeric sequences with optional separators may match financial or administrative reference numbers. Mitigation: Require corroborative evidence keywords such as "RG" or "registro geral" 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.