Israel Bank Account Number
Detects Israel Bank Account Number patterns. This pattern is based on a Microsoft Purview built-in sensitive information type. Financial account numbers require corroborative evidence for reliable detection due to their generic numeric format.
- Type
- regex
- Engine
- universal
- Confidence
- medium
- Confidence justification
- Medium confidence: the 2-3-8 digit grouping pattern provides some structure. Bank-related keywords in Hebrew or English improve detection accuracy. Context label evidence plus explicit template/example exclusion improves precision for high-risk identifiers. Added context gating and exclusion rules improve precision and reduce incidental matches.
- Detection quality
- Verified
- Jurisdictions
- il
- Regulations
- Protection of Privacy Law (Israel), PCI-DSS
- Frameworks
- ISO 27001, ISO 27701, PCI-DSS, SOC 2
- Data categories
- pii, financial
- Scope
- narrow
- Risk rating
- 8
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Compatible, Netskope: Compatible
Pattern
\b\d{2}-?\d{3}-?\d{8}\b
Corroborative evidence keywords
bank account, חשבון בנק, מספר חשבון, branch, סניף, account number, savings, bank account number, savings account, [object Object], [object Object], [object Object], banking, [object Object], checking, chequing, financial institution, Kiwibank, routing, Westpac (+37 more)
Proximity: 300 characters
Should match
12-345-12345678— Israeli bank account with hyphen separators1234512345678— Israeli bank account continuous digits98-765-98765432— Israeli bank account format
Should not match
12-345-1234567— Only 7 digits in account section, too short12-345-123456789— 9 digits in account section, too longsample template placeholder number 123456789— Template/sample context should be excluded even when numeric-like values appeartemplate example placeholder record identifier— Template/sample context should be excluded even when anchor words are present
Known false positives
- Generic numeric sequences such as reference numbers, invoice numbers, or identifiers from other domains Mitigation: Require corroborative evidence keywords within the proximity window to distinguish financial account numbers from general numeric data.
- Phone numbers, postal codes, or other structured numbers with similar digit counts Mitigation: Layer with other detection patterns to deprioritise matches that overlap with phone number or postal code formats.