How it works

Five steps. One consistent audit trail.

Every VestraData workflow follows the same sequence, from credential to evidence, regardless of data source or deployment model.

01 Connect Add a source. Credentials are encrypted per-tenant. Scope is defined before any scan runs. [ENCRYPTED_CREDENTIAL · TENANT_SCOPED]
02 Discover Lightweight schema pass. Maps tables, estimates volume, surfaces likely-sensitive fields. [SAMPLE_RATE: adaptive · NO_FULL_SCAN]
03 Scan Deep field-level scan with confidence scores, row counts, and context evidence for review. [ENGINE: GLiNER-v2 · ZERO_SHOT: true]
04 Act Apply the right control: mask, anonymize, generate a synthetic export, or prepare a governed copy. [AUDIT_LOG: tamper_evident · POLICY: enforced]
05 Prove The decision trail is complete. Show regulators what was found, what changed, and who approved it. [GDPR:Art.30 · HIPAA:§164 · PCI:4.0]
First session

Use the first conversation to test fit, not to sit through a pitch.

The right outcome of an initial review is clarity: can it run where it needs to run, does it fit your first workflow, and is a pilot justified?