Skip to main content

Detectors and the Detector Catalog

Detectors are the building blocks of Data Governance: each one recognizes a single type of sensitive data, such as a credit card number, API key, email address, or medical record number. You choose detectors when you create a policy.

Open Data Governance → Detectors to understand what the gateway can detect. The page has three views:

ViewPurpose
Your coverageShows detectors referenced by your enabled policies
CatalogBrowses all shipped, custom, and composite detectors
Catalog managementManages the active detector bundle version; available to administrators

Your coverage​

Use Your coverage to answer: What is my organization actively protecting right now?

This view is policy-driven. A detector appears here when an enabled policy uses it. Follow See policies links to find the policies responsible for that coverage.

Catalog​

Use Catalog to:

  • Browse detectors by coverage area, regulation, industry, or region
  • Open a detector to inspect how it works
  • Review custom and composite detectors
  • Test sample text against text-pattern detectors in the active catalog

The in-browser test evaluates text-pattern detectors. AI-entity detectors are evaluated by the gateway at scan time and are not included in that local test.

Custom and composite detectors​

Security administrators can build detectors for organization-specific data, such as employee IDs, ticket numbers or project code names.

To create a custom detector:

  1. Select Create custom detector.
  2. Under What kind of detector?, choose Match a pattern or keywords to find your own IDs, codes or terms, or Combine detectors to build a composite detector.
  3. Under Build the detector, choose Regex pattern or Keywords, enter what to match, and add any rules.
  4. Select Continue and finish the remaining steps.

Regex patterns​

A regex pattern matches exactly as written, including case. To ignore case, start the pattern with (?i), for example (?i)emp-\d{4}.

The builder checks your pattern as you type, and won't let you continue with a pattern the gateway can't run:

What you enteredWhat the builder tells you
A lookahead or lookbehind, such as (?!…) or (?<=…)These aren't supported. To leave out specific values, use Exclude exact values instead.
A pattern that could run very slowly, such as a repeated group that itself repeats, like (a+)+The engine wouldn't run it. Rewrite it without the nested repetition.
Any other syntax the gateway can't read, such as a backreference like \1The detection engine can't read the pattern, and why.
A pattern longer than 4,096 charactersPatterns can be up to 4,096 characters.

Rules​

Rules narrow what a detector reports:

RuleWhat it does
Require a validity checkReports a match only if it passes a check, such as a checksum.
Exclude exact valuesNever reports the values you list. Regex patterns only.
Require a word nearbyReports a match only when one of your words appears close to it.
Exclude when a word is nearbyDoesn't report a match when one of your words appears close to it.

For the word rules, choose how close the word must be: Close or Wider.

Both exclude rules win over everything else: a match they exclude isn't reported, even if it passes every other rule.

Exclude exact values​

Use Exclude exact values for known values that look sensitive but aren't, such as test IDs or placeholder numbers. Enter one value per line.

A value is excluded only when it is exactly equal to what the pattern matched, including case. Values are plain text, not patterns.

For example, with the pattern EMP-\d{4}:

  • EMP-0000 excludes the match EMP-0000.
  • 0000 excludes nothing, because the pattern never matches 0000 on its own. The builder warns you about values like this.

To compare only part of a match, wrap that part of the pattern in parentheses. With EMP-(\d{4}), the value 0000 excludes EMP-0000. When the pattern has parentheses, the detector also reports and redacts only the part inside the first pair. Sometimes the builder suggests where to add the parentheses, with an Apply fix button.

Keywords​

A Keywords detector matches the words you list. Keywords ignore case and match whole words. Turn on Detect keywords inside longer words to also match inside longer words, so that acme matches acmecorp.

Composite detectors​

A composite detector represents a meaningful class that depends on multiple findings occurring together—for example, a subscriber number together with billing information.

When creating a composite detector, you can define:

  • Findings that must all be present
  • Groups where at least one finding must be present
  • Findings that must not be present
  • A minimum number of distinct findings
  • A minimum confidence
  • The synthesized name reported when the combination matches
tip

Test custom logic with representative positive and negative samples before adding it to a blocking policy.