The Path to AI Autonomy in the SOC
Path is now the target of an action by law enforcement.

Path is now the target of an action by law enforcement.
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.
As the a16z report itself puts it, gathering logs is different from changing a production system.
A drop in agreement rates, a major change in the environment such as a new EDR or cloud migration, or a single serious miss should trigger a demotion until the criteria are met again.
Treat the AI SOC agent the way you would treat a new privileged identity.
Past victims of Path are not made whole by this action alone, and anyone still running systems compromised before this action remains affected.
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.
Each function can sit at a different level of automation, from fully manual to fully automatic, within the same system.
This action was brought by law enforcement, which is the body to watch for further updates.
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.
In the a16z survey, 46% of CISOs listed AI agents acting outside their intended permissions, or compromised agents, among their five biggest worries, and 29% cited prompt injection or data leakage through AI applications.
Path is now dealing with an active legal process, with the agency involved leading the action.
Human approval is only as good as the context the reviewer receives.
When an approval step arrives without clear evidence or criteria, reviewers start clicking through requests to keep the queue moving, and oversight quietly disappears.
Why it matters
Taking down the infrastructure is real progress, but the skills and the playbook behind it don't disappear with the servers -- treat this as a disruption, not a resolution.
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.
What security teams should do
- Treat this as a disruption worth noting, not a reason to deprioritize monitoring for the same group's affiliates or rebrands.
- The authors make a point every SOC leader should take to heart.