Topic starter
11/11/2026 5:59 pm
TL;DR: AI agents in security produce incomplete investigations when fragmented telemetry and inconsistent schemas limit what they can reason over, according to Query. The data layer, not the model, determines whether analysts get usable evidence or faster noise.
Editorial analysis by NHI Mgmt Group, based on content published by Query: “The AI Agent Stack Is Upside Down”.
By the numbers:
- Only 8.5% of public MCP servers implement OAuth, according to Software Analyst Cyber Research cited by Query.
- Tool poisoning attacks succeed at a 72.8% rate, according to Software Analyst Cyber Research cited by Query.
Key questions
Q: Why do AI agents produce incomplete investigations when telemetry is fragmented?
A: AI agents produce incomplete investigations when telemetry is fragmented because logs, alerts and traces lack shared identifiers, time alignment and context needed for correlation.
Q: How does semantic context improve security data correlation?
A: Semantic context improves security data correlation by adding meaning to raw events, such as asset identity, user identity, process lineage, timestamps and attack stage.
Q: How should security teams govern AI agents that can act across multiple business systems?
A: Treat the agent as a governed digital actor with its own identity, delegated authority, and revocation path.
Practitioner guidance
- Implement cross-source data normalization Map identity, endpoint and cloud fields to shared semantics before letting agents consume them, so the same user, host or alert means the same thing everywhere.
- Preserve source-level evidence trails Require every automated investigation to retain queries run, systems checked and correlation steps used, so reviewers can validate the conclusion without re-running the case.
- Define environment-specific severity semantics Document what high severity, resolved, new and anomalous mean in your own environment, then apply those definitions consistently across tools and agents.
Bottom line: AI security agents are limited less by model capability than by fragmented, inconsistent telemetry that prevents complete investigations.
Glossary terms: Model Context Protocol, Security Information and Event Management (SIEM), Semantic Context, Autonomous Investigation
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/11/2026 6:07 pm
The deciding control is not model quality, but evidence quality. Security teams keep framing AI agents as a reasoning problem, when the harder problem is whether the environment exposes a coherent evidentiary surface. If the agent can only see part of the picture, the output becomes a polished summary of missing context. The practical conclusion is that AI in security rises or falls on the integrity of the data layer underneath it.
A few things that frame the scale:
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, according to the 2026 Infrastructure Identity Survey.
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What should teams do first when an AI SOC agent is missing evidence?
A: Teams should first verify which source systems are missing, then check ingestion, parsing and normalisation before asking the AI SOC agent to infer anything. If evidence is absent, the agent can only guess. Restoring feeds, fixing field mapping and confirming asset and identity context usually resolves the gap faster than tuning detection logic.
👉 Read our full editorial: Why security AI agents need clean telemetry to investigate well