RFC
Detects RFC patterns.
- Type
- regex
- Engine
- universal
- Confidence
- low
- Confidence justification
- Low confidence: generic pattern format that may match unrelated data. Corroborative evidence keywords are essential for reliable detection. Added context gating and exclusion rules improve precision and reduce incidental matches.
- Detection quality
- Verified
- Jurisdictions
- mx
- Regulations
- LFPDPPP (MX)
- Frameworks
- ISO 27001, ISO 27701
- Data categories
- pii, government-id
- Scope
- wide
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Compatible, Netskope: Compatible
Pattern
\b[A-Z]{4}\d{6}[A-Z0-9]{3}\bCorroborative evidence keywords
identifier, number, ID, ID number, identification, ID card, license, permit, registration, certificate, transaction, transfer, payment, deposit, withdrawal, debit, credit, field, column, row (+23 more)
Proximity: 300 characters
Should match
GARS920101ABC— Individual RFC (4 letters)AAAA000101XY1— Alternate individual RFCABCD123456Z01— Standard individual RFC format
Should not match
GAR920101ABC— Only 3 initial letters instead of 4GARS92010ABC— Only 5 date digits instead of 6GARS920101AB— Only 2 homoclave characters instead of 3template example placeholder record identifier— Template/sample context should be excluded even when anchor words are present
Known false positives
- Common words and phrases related to rfc 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 Spanish (Mexico), 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.
- High-frequency pattern matches in large document corpora due to broad regex anchors. Expected match rate is significantly higher than specific identifier patterns. Mitigation: Tune confidence thresholds for bulk scanning. Consider using this pattern primarily as a pre-filter with secondary validation.