Security leaders are about to hand AI agents a lot more authority. In a recent a16z survey of CISOs at organizations with more than 1,000 employees, 36% said they are comfortable today letting AI agents act autonomously on low-risk security actions. In 12 months from now, 60% expect to be comfortable at that level. Overall, AI SOC was the highest ranking initiative for 2027.
The pressure behind the shift is easy to see. In the same survey, the most common worry was AI-accelerated attacks outpacing the team's ability to respond, selected by 55% of respondents. Analyst time is the scarcest resource in the SOC, and every alert still means pulling evidence from several systems, reconstructing what happened and deciding whether it matters.
The same respondents are cautious at the top end. Only 1% are comfortable with agents acting autonomously on most actions today, and only 7% expect to be a year from now. Most teams want more autonomy, just not all of it.
Autonomy is not “all or nothing”, but rather a spectrum
The question "how much do we trust the AI" is too broad to answer. Researchers worked this out decades ago, in a framework later applied widely in aviation and air traffic control, long before anyone was building SOC agents. In a widely cited 2000 paper, Parasuraman, Sheridan and Wickens proposed that automation applies to four broad functions. Those are information acquisition, information analysis, decision and action selection, and action implementation. Each function can sit at a different level of automation, from fully manual to fully automatic, within the same system.
Mapped onto security operations, the four stages look like this:
- Evidence collection. Querying the SIEM and EDR, pulling process trees, enriching indicators, gathering identity and cloud context.
- Analysis and verdict. Correlating what was collected, reconstructing what happened and deciding whether the alert is a real threat.
- Response recommendation. Proposing what should happen next, such as containing a host, resetting credentials or closing the case.
- Response execution. Actually changing something in the environment.
This split gives security leaders a cleaner set of choices. A team can automate the first two stages heavily, since that is where analyst hours go and where mistakes are cheapest to catch. The same team can stay conservative on the fourth stage, where a wrong move disrupts the business.
Human IN the loop vs. Human ON the loop
Once autonomy is split by stage, teams need a shared way to describe how much of it each stage gets. A useful vocabulary comes from researchers at the University of Washington, who define five levels of agent autonomy by the role the human plays.
- L1 Operator – The human directs and decides, and the agent carries out instructions
- L2 Collaborator – Human and agent plan and execute together
- L3 Consultant – The agent leads and checks in for expertise or preferences
- L4 Approver – The agent works independently and asks for approval only in risky or predefined cases
- L5 Observer – The agent acts on its own while the human monitors and can hit the stop button
The authors make a point every SOC leader should take to heart. Autonomy is a deliberate design choice, separate from how capable the agent is. A highly capable agent can still run at L2 if the stakes call for it.
Read through this lens, the a16z data describes a market moving from roughly L2 today toward L4 for low-risk actions within a year. Gartner offers a complementary distinction between a human in the loop, who approves each action, and a human on the loop, whose oversight is strategic.
How to decide where and how much autonomy to grant an AI SOC
The levels mentioned above tell you what the options are. Deciding where each SOC action belongs takes a rubric, and three questions do most of the work: Reversibility, Blast radius, and Receipts. Scoring real actions against those questions produces a map that most security teams will recognize, ranging from fully autonomous log queries at L5 to human-decided isolation of production servers at L2.
Autonomy you earn, autonomy you lose
The OWASP Top 10 for Agentic Applications gives this approach a name. It extends least privilege into least agency, granting agents only the minimum autonomy needed for safe, bounded tasks and letting that autonomy grow as it is earned. A practical set of graduation criteria includes measured agreement, dry runs, complete evidence trails, and rollback paths. Autonomy should also move down when agreement rates drop or the environment changes significantly.
Govern the agent like a privileged identity
Every level of autonomy granted to a SOC agent raises the damage that agent can do if it is wrong, manipulated or compromised. In the a16z survey, 46% of CISOs listed AI agents acting outside their intended permissions, or compromised agents, among their five biggest worries. Security leaders should give the AI SOC agent its own identity, scope its permissions, log every action, and monitor it with the same detections applied to new admin accounts.
Note: This article has been written and contributed by Zev Schonberg, PMM at Intezer.


