How security leaders see AI being used in the SOC An Elastic report on AI adoption in the SOC, based on a survey of more than 400 cybersecurity professionals, found that 96% of security teams now use AI while only 18% have structured and enforced frameworks governing that use. Of the respondents, 52% require a human to authorize all AI decisions before action, 43% trust AI with low-risk tasks but require verification for higher-consequence outputs, and 3% permit AI to act without a human in the loop; 89% say the future of AI in security operations is agentic workflows paired with detailed human oversight. How security leaders see AI being used in the SOC 96% of security teams are now using AI. Whether it's through chatbots, native platform features, in-house agents, or custom-built tools, AI has become standard equipment in the SOC. Yet, only 18% of teams have structured and enforced frameworks for how AI should be used in the SOC. Security leaders aren't struggling to adopt AI. They're struggling to control it, explain it, and defend it when a board or a regulator asks What happened? Why did the system do that? Without an answer to these questions, the technology isn't the risk… the lack of insight into its process is. Different levels of AI autonomy Data from the recent AI Adoption in the SOC report https://www.elastic.co/resources/security/report/ai-adoption-soc — based on a survey of more than 400 cybersecurity professionals using AI in their day-to-day — reveals what teams are actually allowing their AI agents to do: - 52% require a human to authorize all AI decisions before it takes any action. - 43% trust low-risk tasks but require verification for higher-consequence outputs. - 3% permit AI to take actions it deems appropriate with no human in the loop. Looking ahead, 89% of respondents say the future of AI in security operations is agentic workflows paired with detailed human oversight. This means security professionals aren't rejecting agentic AI; they're asking for it with a human as a central part of the approval chain. This is a deliberate design choice, and it's the right one. We insist agents have all the guardrails — show your work, ask for sources, then verify, verify, verify. Director of Security, Financial Services This is a necessary, calculated approach toward a practical tool that’s only going to grow as a share of analyst usage. Security is held to different standards with AI Every function in the business benefits from faster AI: Sales wants faster account research, finance wants faster forecasts, and IT wants faster ticket resolution. But security operations as a function carries the burden of higher consequence when AI gets ahead of itself. If, for example, an AI agent flags an incident, takes action, and something breaks, then a legitimate business process gets blocked, a false positive triggers a costly response, or worse, a real threat slips through because the agent made a probabilistic guess that looked confident but wasn't correct. And now, you're in front of the board or a regulator. They want to know what happened, why the system acted the way it did, and who approved it. "We trusted AI" isn't a viable answer. Human oversight in AI-driven security is business risk reduction. A transparent, explainable AI workflow gives you something to point to: here's what the system saw, here's what it recommended, here's who approved the action, and here's why. That paper trail is what separates a defensible incident response from a credibility crisis. And it works both ways, too. While AI is incredible at flagging anomalies that may otherwise have been missed, only human analysts understand the broader business implication of halting operations for every low-incident flag. Analysts need this visibility into exactly how the AI reached its conclusion in order to tune it appropriately to scale with the business. AI will find a vulnerability in legacy code and just decide the application can't be used. A human is the one who has to do that risk analysis. Sometimes you override security because you actually have to run a business. That's the human piece: knowing what risks are necessary to enable business operations. CISO, Transportation The leadership-practitioner gap that needs to close Here's something that should concern every CISO reading this report: Your frontline team may be experiencing a very different reality than the one you're describing upward. Executives are more than four times as likely as practitioners to say AI adoption has had no negative impacts 26% versus 6% . Team managers and practitioners are more likely to be disappointed that AI didn't meet expectations than leadership is 38% versus 28% . Executives also overestimate how often their teams rely on native AI tools 75% reported versus 60% actual and underestimate how often teams build their own workarounds 38% believed versus 49% actual . This gap reveals a false confidence surveyed CISOs have about their teams' AI adoption. If frontline analysts are quietly patching together chatbots, in-house scripts, and sidecar AI tools because the native AI tooling in their existing platform isn't getting the job done, you won't find out from a dashboard. Closing this gap starts with asking practitioners directly what they're actually using to get the job done, rather than assuming the AI solution one team or manager chose at a point in time is scaling across every analysts’ workload into today’s applications. What makes AI trustworthy enough to act on So, how does a CISO move from "AI gives us faster answers" to "AI gives us answers we can defend?” As with most anything around discussions of AI performance, it all comes down to context. An AI recommendation is only as trustworthy as the data behind it. If your threat intelligence, alert history, and investigation context live in disconnected systems, AI doesn't have the full picture, and neither do you. Teams in this research cited exactly this problem: 29% said their data lacks the structure needed for effective automation, and 37% said they struggle to meet governance, compliance, or audit requirements as a direct barrier to adopting automated workflows. A unified, searchable data foundation https://www.elastic.co/platform changes that equation. When an AI agent can draw on the complete, correlated context of your environment rather than a narrow slice of it, its recommendations become explainable. You can trace the "why" behind every suggested action. The architecture question CISOs should be asking their teams right now is not "which AI tool should we buy next?" But rather "Can we actually explain, end to end, how our AI reached this conclusion?" If the answer is no, that's the gap to close before adding more automation. Building security operations that are ready for what's next The survey data is unambiguous: teams with mature AI adoption report significantly more value than teams still in the pilot stage 100% report moderate or significant value compared to just 60% at the limited-use stage . The argument is for building the foundation that makes AI adoption durable instead of a source of ongoing risk. A few starting points to accomplish this: - Make human approval the default, not the exception. The data shows this is already where most security teams land instinctively, but this needs to be formalized from the top down. - Build cost visibility into every AI deployment from day one. Don't let token spend and licensing creep become a surprise at renewal time. - Unify your data before you scale your automation. Explainability depends on context, and context depends on having your threat intelligence, alerts, and investigation history in one searchable place. - Check in with your practitioners directly. The gap between what leadership believes and what analysts experience is often the first sign that governance isn't keeping pace with adoption. - Treat every AI-assisted decision as something you may need to explain later. Build the audit trail now, not after an incident forces the question. The organizations that get this right won't be the ones with the most AI tools, they'll be the ones that can explain, clearly and confidently, exactly how every AI-assisted decision was made and why a human stood behind it. Curious where your team's AI maturity and oversight stand against industry benchmarks? Access the full AI Adoption in the SOC report https://www.elastic.co/resources/security/report/ai-adoption-soc to see how your SOC compares. Learn what Elastic Security's open, agentic security operations platform https://www.elastic.co/security can help your team accomplish. The release and timing of any features or functionality described in this post remain at Elastic's sole discretion. Any features or functionality not currently available may not be delivered on time or at all. In this blog post, we may have used or referred to third party generative AI tools, which are owned and operated by their respective owners. Elastic does not have any control over the third party tools and we have no responsibility or liability for their content, operation or use, nor for any loss or damage that may arise from your use of such tools. Please exercise caution when using AI tools with personal, sensitive or confidential information. Any data you submit may be used for AI training or other purposes. There is no guarantee that information you provide will be kept secure or confidential. You should familiarize yourself with the privacy practices and terms of use of any generative AI tools prior to use. Elastic, Elasticsearch, and associated marks are trademarks, logos or registered trademarks of elasticsearch B.V. in the United States and other countries. All other company and product names are trademarks, logos or registered trademarks of their respective owners.