How to Configure Windsurf Redshift Audit Log
You set up a windsurf redshift audit log by turning on native database logging. You then route those log files to a secure cloud storage bucket. Many teams give their AI coding tools broad database roles to speed up work. When permissions are too wide, the agent can run risky queries or read private data. A clear audit trail helps your team see every query the agent runs. How a windsurf redshift audit log works in practice Cognition renamed Windsurf to Devin Desktop on June 2, 2026. The app k
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 windsurf redshift audit log by turning on native database logging. You then route those log files to a secure cloud storage bucket. Many teams give their AI coding tools broad database roles to speed up work. When permissions are too wide, the agent can run risky queries or read private data. A clear audit trail helps your team see every query the agent runs.
How a windsurf redshift audit log works in practice
Cognition renamed Windsurf to Devin Desktop on June 2, 2026. The app keeps the same IDE features and uses the Cascade agent. This agent can run terminal commands on its own after the user gives permission. It uses a dedicated terminal that loads the user shell profile. That means the agent can read local aliases and stored database keys. The Cascade agent also reaches external systems through Model Context Protocol servers.
When the agent sends a query to Redshift, the database checks the user credentials. It treats the AI agent just like a human user with those same keys. Redshift can write these login events and user queries to internal system tables. Admins can also set up the cluster to export log files to cloud storage. This setup creates the base for your windsurf redshift audit log.
Why you should separate agent roles in the database
Because the agent loads the user shell profile, it often shares the developer login. If they share a login, the audit log shows them as the same person. Your security team will not know if a human or the agent ran a query. This makes it very hard to review incidents or check for bad commands.
To fix this, teams should create a separate database user just for the agent. You can give this new role read-only rights on specific schemas. When the agent connects through an MCP server, it uses this dedicated role. Now the native database log will tag every AI query with the agent username. Your team can filter the logs by this user to track agent behavior.
Audit Log Integrity + Redshift Security: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
What native logging solves and what it misses
Native database logs are great for looking at past events. They tell your team who logged in and when they did it. They also record the text of the SQL statements that ran on the cluster. Security teams use these records for audits and post-incident reviews.
Still, native logging has clear limits for live security. First, database logs only record actions after the query has already run. They cannot stop a bad drop table command while it is in flight. Second, native logs often Export in batches, which adds a time delay. Third, the database role decides who can log in, not what each query does. If an agent has read access to a table, it can pull every column. Native logs will record the read, but they will not mask emails or card numbers. The raw data still reaches the local terminal and the AI model context.
Govern statements and responses across databases and APIs
Good config and scoped roles are needed setup. They do not check single queries in flight or mask sensitive fields in returned rows. Across Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, and internal HTTP endpoints, hoop.dev sits inline in the protocol beside each supported service as an open-source proxy, a sidecar for your database or API. For every query or command an AI agent or engineer runs against production, hoop.dev decides to pass, mask, block, or hold it for human approval.
First, hoop.dev guardrails block banned queries before they run or hold risky ones for review, and hoop.dev data masking rewrites matched sensitive values in responses in memory. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.
Frequently asked questions
Does Devin Desktop work the same way as Windsurf for database queries?
Yes, Devin Desktop is the new name for Windsurf as of June 2, 2026. It uses the same Cascade agent, dedicated terminal, and MCP server setup to run queries.
Can Redshift audit logs tell human queries apart from AI agent queries?
Redshift only logs the database user that opens the session. If the agent uses the developer shell keys, the logs look the same. You must give the agent its own database user to tell them apart.
Do native audit logs stop the agent from reading sensitive columns?
No, native audit logs only record the query text after it runs. To hide emails, phone numbers, or national IDs in results, you need data masking in front of the database.
Related guides
In this post