Skip to content

Data Flows

Where your data moved, and who moved it.

Trailox maps how data moves between your stores, with the person, role and key behind each copy.

Start a free Data Access ReviewHow it works

Trailox processes over 100 billion S3 requests per month across customers.

Illustrative example data movement

Data movement

Between two data storesIllustrative

02:14 UTC
Identity
prod-etl-worker, service account
Operation
Copy
Source
Amazon S3, prod-events
Destination
Snowflake, EXPORT.EVENTS
Data movementIllustrative
Illustrative data movement between two data stores: four recent moves, one to a destination not seen before for that identity
  1. prod-etl-workerService accountFrom: prod-eventsAmazon S3To: EXPORT.EVENTSSnowflakeOperation: Copy12m ago
  2. dbt-transformService accountFrom: RAW.EVENTSSnowflakeTo: MARTS.EVENTSSnowflakeOperation: Load40m ago
  3. m.leeData analystFrom: CRM.CUSTOMERSSnowflakeTo: adhoc-exportsAmazon S3Operation: Copy1h agoNew destinationNot seen before
  4. backup-runnerService accountFrom: prod-martsAmazon S3To: backup-archiveAmazon S3Operation: Copy3h ago

A copy is an access too

Each load or copy puts your data under different controls, and access reviews rarely check where the copy went. Trailox shows both ends of each move, what was read and where it was written, and who was behind it. When a move does not fit the usual pattern, you get a finding. Your data is never read.

Book a demo to see how

Related

Start with a free
Data Access Review.

Read-only. First findings in 48 hours.

Start a free Data Access ReviewHow it works