The Two-Speed SOC: Why Autonomous AI and Analyst Copilots Need Different Guardrails

A design question inside a Fortune 50 security team points to a bigger governance gap for AI in the security operations centre.

ThreatVectr NewsdeskAI-assistedPublished Updated · Editor: Lee Brown· 4 min read
A dimly lit modern security operations centre viewed from behind an empty analyst chair, multiple large curved monitors glowing with abstract log data and netwo
Illustration made with AI. Not a photograph of the events described.
Share

Key points

  • A Fortune 50 chief information security officer is piloting Anthropic's Claude inside his security operations centre, according to a recent industry account.
  • The team is running the AI in two modes: autonomous agents that act on their own, and copilots that assist a human analyst.
  • Governance frameworks for AI in security work, including the US National Institute of Standards and Technology's AI Risk Management Framework released in January 2023, treat these two modes as different risk classes.
  • No regulator has yet issued a final rule specifically for AI use inside a security operations centre.
  • The European Union's AI Act, which entered into force on 1 August 2024, will phase in obligations for high-risk AI systems through 2026.

A senior security leader at one of the largest companies in America is quietly running an experiment that regulators haven't caught up with. His team has plugged an AI model into their security operations centre, the room where analysts watch for signs of hackers, and given it real work to do.

The account, first surfaced by The Hacker News, is anecdotal. But it maps neatly onto a question that policy staff at several agencies have been circling for a year: accountability for what an AI decides during a live incident investigation.

What is actually happening inside this security team?

The team has connected Claude, an AI assistant made by Anthropic, to a handful of detection tools. Two modes run side by side.

In the first mode, the AI works as an autonomous agent. It pulls logs and checks alerts without a human pressing a button each time. In the second, it works as a copilot: a human analyst asks questions, the AI drafts answers, and the analyst decides what to do.

The distinction sounds academic. It isn't. Under most emerging AI governance frameworks, an autonomous system that acts on its own sits in a higher risk tier than an assistant that only suggests. We first covered the governance race to define those tiers on 17 June 2026.

Why this matters for the rulebook

The US National Institute of Standards and Technology published its AI Risk Management Framework in January 2023 as voluntary guidance. That framework asks organisations to map and manage risk based on how much autonomy a system has and what harm it could cause.

A security operations centre is a high-stakes environment. An autonomous agent that shuts down the wrong server, or misreads a log and clears a real alert, causes real damage. That's not a hypothetical; it's the failure mode any final rulemaking on AI in critical operations will have to address. As our 22 June story on legacy infrastructure found, those frameworks also assume the underlying systems are secure, and they frequently aren't.

The EU's AI Act, which entered into force on 1 August 2024, goes further. Article 6 sets out which systems count as high-risk. Security tools that make consequential decisions about network defence may fall inside that scope depending on deployment. Obligations phase in through 2026, with several implementing acts still in public consultation.

US disclosure rules don't yet speak to this directly. Nothing currently requires organisations to log or report whether an autonomous AI agent made a consequential call inside an incident response process, even when that response touches a material event.

Should you worry?

If your team is piloting AI in the operations centre, keep a clear paper trail of which decisions the AI made alone and which a human approved. That record will matter if a regulator asks, and it'll matter more if something goes wrong.

Boards should press two questions. Where in the response process does an AI act without a human? Who signed off on that scope?

Here's the honest assessment: the governance gap isn't theoretical, it's structural. The rulemakers are watching deployments like this one to write the rules that come next. Teams that documented their choices early will have a far easier time explaining them when that moment arrives.

© 2026 Threat Vectr