Group Purchasing
Group Purchasing

Assessing the Feasibility and Effectiveness of AI in CTI-Driven Threat Hunting

Assessing the Feasibility and Effectiveness of AI in CTI-Driven Threat Hunting (PDF, 0.37MB)Published: 17 Sep, 2026
Created by:

Security operations analysts spend significant time converting unstructured cyber threat intelligence (CTI) into actionable threat-hunting content, a manual process that is slow, inconsistent, and prone to error. While large language models (LLMs) appear well-suited to automate portions of this workflow, their ability to reliably operationalize CTI has not been rigorously evaluated.

This study evaluates three commercial LLMs, OpenAI GPT-4o, Google Gemini, and Microsoft Copilot, against ten recent CTI reports, measuring indicator extraction accuracy and validating generated Kusto Query Language (KQL) and CrowdStrike Query Language (CQL) hunting queries in Microsoft Sentinel and CrowdStrike NG-SIEM. Rather than relying on execution success alone, the evaluation applies a framework that separates indicator extraction from query generation, distinguishes instruction-following failures from analytical reasoning failures, and treats the completeness of the human analyst baseline as a measurable quantity rather than an assumption.

FAQ

An AI agent interrogator is a tool that probes an AI agent's natural language interface from the outside, with no access to its source code, to reconstruct the list of tools, functions, and capabilities it can invoke. Agent Interrogator, introduced in this SANS research, does this through a two-stage process: identifying high-level capabilities first, then enumerating the specific tools behind each one.

Yes. In testing, Agent Interrogator detected 100% of the tools made available through a Zapier MCP server connected to a test agent, even though the agent's hard-coded prompts gave the LLM no explicit documentation about those tools.

Across 20 repeated interrogation runs per test target, Agent Interrogator detected both functions on a baseline test agent in 95% of runs and reported zero hallucinated tools against a control agent configured with no tools at all.

Detection frequency dropped for tools discovered later in a session, from 100% down to as low as 45% for the last-discovered Gmail functions. The research attributes this to the framework's maximum iteration limit being too low to exhaustively work through a large tool set, not to a fundamental flaw in the interrogation approach.

Excessive agency describes an AI agent being granted capabilities, such as authentication functions, that should sit outside the agent's control with proper guardrails. The test agent used in this research includes a get_current_user function as a deliberate example of this vulnerability class.

Not fully yet. The current framework does not recursively interrogate a discovered tool if that tool is itself another AI agent with its own set of tools, which the research flags as a priority area for future work as agent-to-agent protocols like MCP and A2A become more common.