How to Configure JetBrains AI Bigquery Audit Log
You set up a jetbrains ai bigquery audit log by turning on cloud data access logs. Then you route those log records from your editor sessions into your warehouse tables. Most teams start this process by creating a shared cloud service account. They give this account broad read and write roles across the whole project. Broad roles make the initial setup fast for the team. Still, wide permissions let any developer or coding assistant query sensitive tables at will. How the jetbrains ai bigquery
Your coding agents run with your access.
Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.
You set up a jetbrains ai bigquery audit log by turning on cloud data access logs. Then you route those log records from your editor sessions into your warehouse tables. Most teams start this process by creating a shared cloud service account. They give this account broad read and write roles across the whole project. Broad roles make the initial setup fast for the team. Still, wide permissions let any developer or coding assistant query sensitive tables at will.
How the jetbrains ai bigquery audit log setup works
Your code editor talks to your cloud data warehouse through standard database drivers. When a developer asks the assistant to write or run a query, the editor sends that request. The cloud platform checks the identity attached to that local editor session. After the query runs, the cloud logging system writes an audit record. This record holds the user identity, the query text, and the time of the run.
To keep these records for a long time, teams set up a log sink. A log sink is a rule that copies log entries to a target location. You point this sink to a dedicated dataset inside your data warehouse. The cloud platform then streams every new log event into partitioned tables. Security teams can then run standard queries to check who read which table. They can also track how much data each editor session scanned during the week.
How to scope cloud roles for editor sessions
Before you turn on logging, you must fix how developers log in. Do not put static service account keys on developer laptops. Local key files are easy to steal and hard to rotate on time. Instead, tell developers to log in with their own work identities. This links every action in the audit table to a real person.
Next, separate the roles that run queries from the roles that read logs. Developers need permissions to run jobs and read specific test datasets. They should not have permission to edit or delete the audit dataset itself. Put the audit sink in a separate security project if you can. Grant the log sink writer role only to the cloud logging service account. Give your security team read access to that central audit dataset. This layout stops users from changing their own log history after a bad query.
AI Audit Trails + Audit Log Integrity: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
What native logging solves and where gaps remain
Native cloud logging gives your team a strong record of past database events. It proves which identity logged in and when a job started. It also shows the exact query text that ran against your warehouse. This historical record helps teams pass audits and investigate past incidents.
Still, native setup only controls who can log in at the start. It does not inspect or block individual statements while they are in flight. Once a developer or assistant has a valid role, every query runs right away. If a coding assistant queries a table with emails or card numbers, the query succeeds. The native audit log only tells you about the leak after the data leaves. Native logs also cannot mask phone numbers or national IDs in query results. When masking is in place, it rewrites matched fields in results before they reach the screen. Without inline controls, your team relies on slow reviews of past log tables.
Check database and API queries on the wire
Identity tools, roles, and network rules decide who opens a session. Setup alone cannot check what each query does or mask sensitive values in a response once a session starts. When workflows touch Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, or internal HTTP APIs, hoop.dev runs beside those services as an open-source proxy, a sidecar for your Postgres or API. It inspects requests coming in and results going back on the wire.
Your login details and client tools stay as they are while hoop.dev guardrails refuse bad deletes or drops before they run. On responses, hoop.dev data masking rewrites matched sensitive values in memory. Furthermore, hoop.dev holds SOC 2 Type II, is MIT licensed, and writes every query and decision to an audit trail that generates evidence for HIPAA, GDPR, and PCI DSS. See the source on GitHub.
Frequently asked questions
Does the cloud platform log read queries by default?
No, most cloud platforms only log admin changes and table creation by default. You must turn on data access logs manually to record read queries and job runs.
How do we tell assistant queries apart from manual queries?
Look at the user agent and job label fields inside your exported log table. Database tools attach client tags that show which app sent the query.
Can native audit logs block a bad query before it runs?
No, audit logs only record events after the database processes the request. You need inline controls to pause or reject risky queries before they run.
Related guides
In this post