This article contains information on using validators in Content Examination definitions to verify content legitimacy, such as credit card numbers, using LUHN algorithms to reduce false positives in regular expression matches.
Below are examples of using validators as part of a Content Examination definition. This information should be utilized after reading the following pages:
Validators are used to identify if specific content in messages or attachments is legitimate (e.g., Credit cards). These numbers are validated via the use of LUHN algorithms that are defined by the issuer for confirmation purposes.
All validators are case-sensitive and must be entered in lowercase within the Word/Phrase Match List To be considered.
Using validators greatly reduces the false positives when finding matches based on regular expressions alone, as the LUHN check must pass before any regular expression matches are attempted.
Below is a list of all the validators currently supported by Content Examination policies.
Regular expressions in the examples below are only for illustration purposes and may not catch all possible examples.
Activation Score = 1
| Validator Type | Word / Phrase Match List | Email Content Required to Trigger Definition |
|---|---|---|
| ABA Number (American Banking Association Number) | 1 regex aba (\d){9} | A valid ABA number (e.g. 021000322) |
| CHI Number (Community Health Index Number) | 1 regex chinumber (([^\w\t]?\s)?\d){10} | A valid CHI Number (e.g., 3110130017) |
| CardNumber (Credit Card Numbers) Includes the following card types: Visa, Mastercard, American Express (Amex), Diner Club, Discover Card, JCB Cards |
1 regex cardnumber 4(?<=\b(?)) The Regular Expression example provided above only works for Visa cards. The validator portion used works for the other card types, the regex does not. |
A valid Credit Card Number (e.g., a valid Visa Credit Card number of 4444333322221111) |
| Email Address | 1 regex email (\w+[@\.]\s*\w+\.*\w+) | A valid Email Address (e.g., name@domain.com, name_2@domain.com, or name@domain2.com. |
| IBAN Number (International Bank Account Number) | 1 regex iban GB\s(\d){2}\sBARC(\s*\d){14} | A valid IBAN number (e.g. GB 37 BARC 2004 1538 2900 08) |
| NI Number (UK National Insurance Number) | 1 regex nin \s*[a-zA-Z]{2}(?:\s*\d\s*){6}[a-zA-Z]?\s* | A valid National Insurance Number (e.g., BN102966C) |
| NHS Number (National Health Service Number) | 1 regex nhsnumber (([^\w\t]?\s)?(-)?\d){10} 1 regex nhsnumber (([^\w\t]?\s)?(_)?\d){10} |
A valid NHS Number (Hyphen Separated) (e.g., 499-999-9994) A valid NHS Number (e.g., 499 999 9994) |
| NPI Number (Health Identification Card Number) | 1 regex npi (?<!\\d)\\d{10}(?!\\d)|80840\\d{10}(?!\\d) | A valid Standard Health Identification Card Number (e.g., 808401234567893 1234567893). |
| MOD10 (Modulus 10, used to validate Canadian Health and US Postal Service PIC numbers). | 1 regex mod10 (\d){9} | A valid Canada Health Number or US Postal Service PIC number consisting of 9 digits.
|
| SIN Number (Canadian Social Insurance) | 1 regex sin (\d){9} | A valid number (e.g., 046 454 286) |
| SSN (US Social Security Number) | 1 regex ssn ([^0-9-]|^)([0-9]{3}-[0-9]{2}-[0-9]{4})([^0-9-]|$) | A valid US Social Security Number (e.g., 078-05-1125). |
| PhoneNumber Or PhoneNumber+Region - Can be used to minimize false positives or to target specific regions. Includes support for the following regions: AU, UK, US |
1 regex phoneNumberAU (\+?)\d{1,3}(\s)?(\(\d{1}\))?[\s\d-]+ 1 regex,phoneNumber (\+?)\d{1,3}(\s)?(\(\d{1}\))?[\s\d-]+ |
A valid AU-based telephone number (e.g., 1300 307 318) Or A valid telephone number - including country code (e.g., +44 (0)20 7847 8700) |
| PostCode+Region (postcodeau) Includes support for the following regions: AU, CA, UK, US, ZA |
1 regex postalcodeau [0-9]{4} | A valid AU Post Code (e.g., NSW 2060) |
| VIN Number (Vehicle Identification Number) | 1 regex vin [0-9A-HJ-NPR-Z]{17} | A valid VIN number (e.g., 1M8GDM9AXKP042788) |
Comments
Please sign in to leave a comment.