Episode 01
Securing the Agent-to-Database Connection
This episode follows a single request: a customer asks an agent, “What is the status of my order #104?” It starts from the top-level picture of a user, an agent and a database, and drills down hop by hop to the low-level details: which token travels on each call, which SQL runs, and whose identity the database sees. At each level it shows what can go wrong and which guardrail prevents it, so that the detailed architecture at the end still reads as one picture. That architecture brings together workload identity, gateways, engine-level access rules, private networking, human approval, and audit on Google Cloud.
What the stages add
- Tool boundary. Fixed, parameterized queries replace model-written SQL.
- Identity. The agent gets its own workload identity and exchanges the user’s token for a short-lived, narrowly scoped one.
- Database. The engine enforces row- and column-level security on every query.
- Gateways. Ingress and egress proxies authorize each call and screen content in both directions.
- Network. Private connectivity and a data perimeter remove the routes out.
- Writes. A human approves each change, and stored procedures make it idempotent.
- Audit. One trace follows a request across every hop, backed by a kill switch.
- Mapping. Each control is mapped to the OWASP Agentic Top 10 (2026) and LLM Top 10 (2025).
Each stage links to a companion reference page with full configuration. A hands-on lab is in preparation; its implementation plan is published.