A Comparison of all Data Types

This article presents a high-level comparison at all the standard (AnyFind) and Custom data types in Spirion Sensitive Data Platform.

To help you choose the right tool for your discovery needs, here is a comparison of all Spirion Data Types.

  • In Spirion, AnyFinds, Keywords, Regular Expression (Regex), Dictionaries, and SearchAPI are "Detectors" - they find things.
  • SDDs and Exact Match are "Logic Layers" - they refine what was found.

Comparison Table

Data Type

Best Used For...

Logic Type

Complexity

AnyFind

Common regulated data (SSN, Credit Cards, DOB).

Built-in / Pattern

Low (Out-of-the-box)

Keyword

Specific, literal words or phrases (for example, "Confidential").

Literal String

Low

Dictionary

Large lists of known terms (for example, 5,000 client names).

Bulk Literal

Medium

Regex

Structured patterns (for example, Employee IDs like EMP-12345).

Pattern-based

Medium

Exact Match

Specific records from a database (for example, your customers).

Structured Data

High

SearchAPI

Complex, multi-step validation or checksums.

Custom Code

Very High

SDD

Contextual relationships (for example, SSN near a Name).

Orchestration

Medium

Detailed Breakdown

1. AnyFind (The Baseline)

  • What it is: Pre-configured, highly refined detectors provided by Spirion.
  • Use Case: Use these first for standard privacy data (PII, PCI, PHI). They include built-in validation to reduce false positives.

2. Keyword (The Simple Signal)

  • What it is: A search for a specific, literal string of text.
  • Use Case: Best for single terms like "Internal Use Only," "Project X," or specific legal disclaimers.

3. Dictionary (The Vocabulary)

  • What it is: A way to search for any match from a large list (uploaded as a file).
  • Use Case: Use this when you have a "controlled vocabulary," such as a list of all current product codenames or a list of sensitive vendors.

4. Regular Expression / Regex (The Shape)

  • What it is: A pattern-matching string (Perl syntax).
  • Use Case: Use when you know the format of the data but not the value (for example, a 10-digit internal account number that always starts with "99").

5. Exact Match / EDM (The Fingerprint)

  • What it is: A search against a hashed index of your actual database records.
  • Use Case: The "Gold Standard" for accuracy. Use this to ensure you only flag data that actually belongs to your organization (for example, matching a specific SSN to a specific Name in your HR system).

6. SearchAPI (The Power Tool)

  • What it is: Advanced detection logic that can include conditional checks and multi-step validation.
  • Use Case: Use when RegEx or Keywords aren't enough—for example, if you need to perform a mathematical checksum on a custom identifier to verify it's valid.

7. Sensitive Data Definition / SDD (The Context)

  • What it is: A logical rule that combines other Data Types using AND, OR, NEAR, or NOT.
  • Use Case: Use this to define "Risk Situations." For example, an Email Address by itself might be low risk, but an Email Address near a Password (Regex) is a high-risk SDD.

Summary Recommendation

  • If it's standard PII: Use AnyFind.
  • If it's a specific word: Use Keyword.
  • If it's a list of words: Use Dictionary.
  • If it's a formatted ID: Use Regex.
  • If it's a specific record from your DB: Use Exact Match.
  • If it's a combination of the above: Use an SDD.