Trailox for Google BigQuery
Connect BigQuery principals to the jobs and tables they touch.
Detect behavioral changes and investigate historical activity across every project.
Unusual read by a service account
Google BigQuery
02:58 UTCIllustrative
- Identity
- reporting-sa, service account
- Dataset
- prod_customers, first read by this account
- Volume
- Bytes processed far above its baseline
- Timing
- Outside its established pattern
Next step: Disable the service account, then use the same record to see what it read.
What it shows
What Trailox shows in BigQuery
- Every job, attributed: the user or service account, and the tool behind it.
- Datasets and tables: the datasets and tables each job read.
- Access history: a table's complete access history over time.
Detections
Behavioral detections for BigQuery
What it catches
- Stolen keys and logins that still work
- Data copied out of BigQuery
- Service accounts and AI agents reading outside their task
- Insider misuse by a valid user
FAQ
Questions buyers ask
Does Trailox read my BigQuery data?
No. Trailox reads access logs and metadata only. Your data is never read.
Does Trailox modify my datasets or jobs?
No. No datasets or jobs are modified.
Can Trailox see which application ran a job?
Yes, where identifiable: the console, the API, a client library or a BI tool.
How do we start?
With a free 14-day Data Access Review. Read-only. First findings in 48 hours.
Start with proof,
not a pitch.
Free 14-day Data Access Review. Read-only. First findings in 48 hours.