Platform / Discover

You know what sensitive data you have and where it is

Gigantics reads the schema of your databases, identifies personal information field by field and assigns it a risk level. Your team reviews and confirms it before moving on.

Schema

The complete map of your data

Gigantics connects to each source and reads its structure: tables, columns, types and relationships. It analyzes the structure and a bounded sample, not a copy of the database.

  • Tables, columns, types and relationships of every source
  • Include or exclude entities, also with regular expressions
  • Configurable sample size and concurrency
  • Analysis inside your infrastructure
Examplescope · acme_bank
included entitiescustomer.*, ordersregex
excluded entitiestmp_*regex
sample size1,000 rows·
concurrency2 processes·
The analysis is tuned to avoid loading the source database.

Classification

Every field, with its label and its risk

The engine combines field names, data patterns and sensitivity rules to propose a label. Your team reviews and confirms it, so an automatic classification never turns into insufficient protection.

  • System or custom labels
  • Risk level per field to prioritize
  • Review and confirmation workflow
  • Every label change is recorded with its reason
Exampleclassification · customers
emailcontact/emailhigh risk
nifperson/national_idhigh risk
birth_dateperson/birthdatehigh risk
countrylocation/countrylow risk
11 fields with personal information, pending confirmation.
Frequently asked questions

Questions about discovery

Does my data leave my infrastructure to be analyzed?

No. Schema analysis and personal information detection run inside your infrastructure. Sensitive data does not need to leave your perimeter to be classified.

Can I define my own classification labels?

Yes. Besides the system labels you can create your own labels for data types specific to your business, and then use them in the transformation rules.

Does discovery affect database performance?

You can scope it so it does not: choose which entities to analyze, exclude others with regular expressions and set the sample size and the concurrency of the analysis.

Next step

Find out what is in your schemas

We show you discovery on an architecture like yours.