Us ABA Routing
Detects Us ABA Routing 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
- high
- Confidence justification
- High confidence: validated with Weighted sum: 3*(d1+d4+d7) + 7*(d2+d5+d8) + (d3+d6+d9) mod 10 = 0 and supported by corroborative keyword evidence.
- Detection quality
- Verified
- Jurisdictions
- us
- Regulations
- CCPA/CPRA, FTC Act s5, GLBA, HIPAA, SOX, State Breach Laws (US)
- Frameworks
- ISO 27001, ISO 27701, PCI-DSS, SOC 2
- Data categories
- financial
- Scope
- narrow
- Risk rating
- 9
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Compatible, Netskope: Compatible
Pattern
\b\d{9}\bCorroborative evidence keywords
bank account, account number, account no, BSB, routing number, sort code, IBAN, SWIFT, BIC
Proximity: 300 characters
Should match
021000021— JPMorgan Chase routing number011401533— Bank of America routing number091000019— Federal Reserve routing number
Should not match
12345678— Only 8 digits instead of 91234567890— 10 digits instead of 912345678A— Contains a letter instead of all digits
Known false positives
- Financial terminology appearing in published reports, accounting textbooks, regulatory guidance, or template documents without actual transaction data. Mitigation: Require corroborative evidence keywords within the proximity window. Cross-reference with structured financial identifiers to confirm actual sensitive data.
- In American English, standard business terminology overlapping with financial detection keywords in routine correspondence and documentation. Mitigation: Increase confidence threshold when scanning business correspondence. Layer with transaction-specific patterns for higher precision.