When Someone Says They Deployed an "Autonomous Agent," Ask One Question
August 15, 2026
August 15, 2026
When someone tells you they deployed an "autonomous agent," ask one question: at what level of autonomy?
Autonomy is not an on/off switch. It is a scale.
Cloud Security Alliance's autonomy framework lays out a six-level taxonomy adapted from autonomous vehicles:
Agent sets its own goals
Human monitors only
Agent acts, escalates at boundaries
Human approves the plan
Human approves each action
Human execution
The agent informs; the human executes every single action. Think standard search and informational chatbots.
The agent performs distinct tasks, but every individual step requires separate human sign-off.
The human approves the overall plan upfront; the agent executes independently within strict boundaries. This is the dominant enterprise pattern today.
The agent operates autonomously within guardrails and escalates only on exceptions. Oversight shifts from approving every step to handling edge cases.
The agent executes across broad workflows; humans review audit logs retrospectively rather than approving actions upfront.
The agent defines its own goals and sub-tasks without operational boundaries. Human oversight is purely strategic.
The reality across enterprise production environments: nobody runs L5. The framework itself notes L5 is not suitable for enterprise deployments. Most enterprises sit at L1-L2 today. The incidents that make headlines happen when agents get pushed to L3-L5 without controls to match.
Never set autonomy at the agent level. Set it per action.
Base it on reversibility, blast radius, and whether a human can catch a failure before it impacts data or capital.
Generating an internal summary? L3 works. Triggering database migrations, transferring funds, or emailing clients? Keep it at L1 or L2 with a hard approval gate.
Autonomy is an operational governance decision, not a tech spec.