Security reviews at Databricks relied on automation but still consumed expert time on predictable work, leaving less room for genuinely novel, high-risk architectures. The author built an agent-based layer on Databricks using Unity Catalog for governed tables containing standards, request data, and decisions; Databricks-hosted foundation models (Claude Haiku, Sonnet, Opus) for classification and reasoning; and Lakeflow Jobs for orchestrating notebook-based workflows on serverless compute. A conversational intake app built with Databricks Apps turns plain-language descriptions into structured requests and provides preliminary risk indications before a formal request is created. Seven focused agents each have a bounded responsibility—intake, risk assessment, requirements, specialized reviews, validation, workflow, and learning—ensuring behavior remains inspectable and testable. Routine requests that once waited days in the queue can now be completed in minutes, and security engineers spend more time on designs requiring genuine expertise.
Approach / What changed
A multi-agent system on Databricks using Unity Catalog for governed tables of standards, request data, and decisions; Databricks-hosted foundation models (Claude Haiku, Sonnet, Opus) for classification and reasoning; Lakeflow Jobs for orchestrating seven focused notebook-based agents on serverless compute; and Databricks Apps for the conversational intake experience and an executive dashboard.
Takeaways
1
Separate process from judgment: automate repeatable steps only when criteria are explicit, evidence is required, and uncertainty is escalated to a human.
2
Seven focused agents with bounded responsibilities (intake, risk assessment, requirements, specialized reviews, validation, workflow, learning) keep the system inspectable and testable.
3
Building on a unified platform (Unity Catalog, Databricks models, Lakeflow Jobs, Databricks Apps) allowed a working system in under two hours instead of weeks.
FAQ
What platform components were used to build the agent system?
The system used Unity Catalog for governed tables, Databricks-hosted foundation models (Claude Haiku, Sonnet, Opus) for classification and reasoning, Lakeflow Jobs for orchestration on serverless compute, and Databricks Apps for the intake experience and dashboard.
How does the system handle requests that the agents cannot resolve?
When information is missing or contradictory, the system asks for clarification or routes the request to a human reviewer. The system does not infer its way to approval; it escalates when uncertain.
What metrics are tracked to measure the system's impact?
The executive dashboard tracks request volume, risk distribution, automated completion, human escalation, cycle time, and estimated time saved by reviewers, all derived from operational records in Unity Catalog.
Boards of directors turn ownership into a governance control loop: shareholders elect directors, directors set strategy and guardrails, committees verify independently, and management executes inside those limits.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.