Skip to content

GatorSet Overview

GatorSet provides bulk, policy-driven data protection for Extract, Transform, Load (ETL), migration, replication, and batch processing workloads. It protects sensitive data before it leaves the source system, ensuring production data is never copied or transferred in an unprotected form.

Unlike traditional ETL and data migration solutions, GatorSet does not require temporary staging areas containing unprotected production data. Privacy Enhancing Technologies (PETs) are applied inline as data is moved from the source to the target, eliminating temporary exposure windows and significantly reducing the risk of data leakage into non-production environments.

Using the same eXate Manifests, Policies, and Privacy Enhancing Technologies (PETs) as the rest of the platform, GatorSet applies consistent protection during bulk data movement while preserving data usability, referential integrity, and database structure.

Key Capabilities

  • Bulk protection of structured data during ETL, migration, replication, and batch processing.
  • Inline protection during data movement without creating temporary staging environments containing unprotected production data.
  • Policy-driven enforcement using eXate Manifests and Policies.
  • Support for masking, tokenisation, encryption, decryption, and other Privacy Enhancing Technologies (PETs).
  • Protection of primary and foreign keys while preserving referential integrity across related datasets.
  • Replication of database schema (DDL) to recreate the target database structure.
  • High-performance processing of large datasets.
  • Production-to-non-production data provisioning.
  • Secure data provisioning for development, testing, UAT, analytics, AI, and third-party environments.
  • Ensures sensitive data is protected before it leaves the source system.
  • Minimal changes required to existing ETL, migration, and replication workflows.

Typical Use Cases

GatorSet is commonly used to:

  • Provision protected copies of production databases for development, testing, and UAT.
  • Migrate databases while protecting sensitive information.
  • Protect data flowing through ETL and batch processing pipelines.
  • Replicate production data safely to cloud or on-premises environments.
  • Deliver protected datasets to third-party suppliers and offshore development teams.
  • Create compliant datasets for analytics, reporting, machine learning, and AI workloads.
  • Populate CI/CD pipelines with protected production data.

Bulk Protection Flow

GatorSet reads data directly from the source system, evaluates the configured Manifest and Policies, applies the required Privacy Enhancing Technologies (PETs) inline, and writes only protected data to the target system. At no point is an unprotected copy of the production data written to an intermediate staging database or file.

Where configured, GatorSet also replicates the source database schema (DDL), allowing the target environment to maintain the same structure as the source while ensuring sensitive values remain protected.

sequenceDiagram
    autonumber

    participant Source as Source Database
    participant GS as GatorSet
    participant PE as eXate Protection Engine
    participant Target as Target Database

    Source->>GS: Read schema (DDL)
    GS->>Target: Recreate target schema

    Source->>GS: Stream source data
    GS->>PE: Evaluate Manifest and Policies
    PE-->>GS: Protection requirements

    GS->>PE: Apply required PETs
    PE-->>GS: Protected data

    GS->>Target: Write protected data

Bulk Processing

  1. GatorSet connects to the source and target systems.
  2. The source database schema (DDL) is read and, where configured, recreated on the target system.
  3. Data is streamed directly from the source system without being written to an intermediate staging area.
  4. The configured Manifest and Policies are evaluated.
  5. Required Privacy Enhancing Technologies (PETs) are applied inline to the data.
  6. Primary and foreign keys are protected while preserving referential integrity across related tables.
  7. Only protected data is written to the target system.
  8. The target environment contains a structurally equivalent, policy-compliant copy of the source data, ready for development, testing, analytics, migration, or other downstream workloads. At no point is an unprotected copy of the production data stored outside the source system.

Documentation

For step-by-step configuration guides, see the GatorSet Manifest Walkthrough: bulk anonymization workflow, partitioning, write operations, table features, and DB permissions.