Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.dataharbor.co/llms.txt

Use this file to discover all available pages before exploring further.

Schema & Key Analytics

Your schema, under surveillance. Continuous monitoring of your data’s shape. DataHarbor learns schema over time and surfaces emerging risks automatically.

How it works

As Virtual APIs are used, DataHarbor:
  1. Learns schema shape over time
  2. Detects schema drift as new fields appear
  3. Flags uncovered keys that may contain sensitive data
  4. Identifies risky combinations that enable re-identification
  5. Surfaces compliance violations

Schema drift detection

When your upstream API adds new fields, DataHarbor notices. New fields are not automatically protected — you receive an alert to review and apply appropriate controls.

Uncovered key detection

DataHarbor flags fields that may contain sensitive data but have no controls applied.

Risky combination detection

Some field combinations enable re-identification even when individual fields seem safe. DataHarbor identifies these patterns — for example, the combination of zip code, date of birth, and gender can identify 87% of the US population.

Compliance detection

Automatic detection of potential compliance violations:
RegulationDetection
GDPR Article 4(1)Personal data exposed without consent basis
CCPACalifornia resident PII without disclosure
HIPAAPHI fields without BAA coverage

Dashboard view

The Schema Analytics dashboard shows:
  • Schema coverage: Percentage of fields with controls applied
  • Risk score: Aggregate risk based on uncovered and risky fields
  • Field inventory: Complete list of observed fields with control status
  • Alert history: Timeline of detected issues

Next steps

Data Remediation

Define how emerging risks should be remediated

Data Control

Apply controls to newly flagged fields