Skip to main content

Identifier Detectors for Personal, Health and Financial Data

Part of Security rules.

Personal, health, or financial identifier recognizes specific number formats, applies built-in validity checks such as checksums and issued-number ranges, and, for weaker formats, requires a nearby word such as "SSN" or "routing". It finds patterns, not people. A valid-looking number that was never issued will match, and an issued number written in an unusual way may not. It does not read images, scanned documents, or content in unsupported attachments. It is available only when your deployment administrator has opened the detector library.

One rule can watch several kinds, and the editor shows each kind's validation strength and whether Block is reasonable for it:

KindValidationNearby wordBlock
US Social Security numberShape and issued-number rangesNot needed for dashed or spaced numbersReasonable for dashed numbers
US taxpayer identification number (ITIN)Shape and middle-group rangesNot needed for dashed or spaced numbersReasonable
IBANCountry length and mod-97 checkNot neededReasonable
UK National Insurance numberLetter and prefix rules from HMRC guidanceNot neededReasonable
Canadian Social Insurance NumberLuhn checkNeeded for numbers without separatorsMonitor recommended
Australian Tax File NumberWeighted modulus-11 checkAlways neededMonitor recommended
US Medicare Beneficiary IdentifierPublished letter and digit positionsNot neededReasonable
US bank routing number3-7-1 check and Federal Reserve prefixAlways neededMonitor recommended
Medical record numberDigits after a label such as MRNThe label, before the numberMonitor recommended
Bank account number after a labelDigits after a label such as "account number"The label, before the numberMonitor recommended
Email addressConservative address shapeNot neededMonitor with a minimum count
Phone numberInternational numbers valid in bundled numbering-plan data; US, Canadian, UK, and Australian national formatsInternational: not needed. National: neededMonitor with a minimum count

Options:

  • Sensitivity. Standard finds formatted numbers and checks for a nearby word where there is no checksum. Strict wants the printed form and a nearby word. Broad also looks for unformatted nine-digit Social Security and ITIN numbers, but only next to a word. The editor shows what each setting does for every selected kind.
  • Nearby word means within about 40 characters before or after the number (before only for medical record and bank account numbers) on the normalized text. A field name beside its value, such as "ssn": "...", counts. Required demands a word for every kind. Extra context words adds up to 20 of your own words, such as an internal field name.
  • Minimum matches with Count distinct values turns "any email address" into "a list of 25 email addresses".

Identifier detectors read the same normalized copy as payment card version 2, so numbers split by non-breaking spaces, zero-width characters, or written with fullwidth digits are found. For HTTP content, the existing percent-encoded, base64, and nested JSON views are read too. Not claimed: dots as separators in Social Security numbers, spelled-out digits, letter-for-digit substitution, reversed values, values split across fields, and text in images.

Findings and rule evaluations record only the detector, its version, and counts per kind. Test detector adds counts of numbers found with and without a nearby word and the reasons candidates were rejected (failed check digits, outside the valid shape or range, valid but no nearby word, or found only at another sensitivity). None of this includes the number. Email addresses and phone numbers are not tracked as model-request exposure digests because they appear in nearly every request.

If your Organization turns on Capture full evidence, the content of a matching action is stored encrypted for the evidence retention period, and for an identifier rule that content contains the identifier. Only credentials are redacted from evidence. Review who can reveal evidence before enabling identifier rules together with full evidence.

Back to Security rules.