Category: Security | Reading time: 5 min
The Report
Salt Security's 1H 2026 State of AI and API Security Report surveyed organizations running agentic AI in production environments.
The headline finding: 48.9 percent of enterprises cannot monitor non-human traffic at all. A near-identical 48.3 percent cannot differentiate a legitimate AI agent from a malicious bot.
Nearly half of the organizations that have deployed agents cannot see what those agents are doing on their networks.
The Speed Gap
The practical consequence of this visibility gap is a speed asymmetry that favors attackers.
AI agents operate at machine speed. They can make thousands of API calls, process millions of tokens, access dozens of systems, and complete irreversible actions in the time it takes a human analyst to open a dashboard.
SOC workflows, alert triage processes, and incident response playbooks are designed around human-speed threats. An agent-speed threat is invisible to those workflows until after significant damage is done.
API Growth Outpacing Security
47 percent of the organizations surveyed reported API growth of 51 to 100 percent in the past year, driven primarily by agentic AI integrations.
Every new API connection an agent makes is a new monitoring surface. The organizations that cannot monitor non-human traffic are watching their API surface expand rapidly while remaining blind to a growing portion of the traffic crossing it.
The security perimeter is not shrinking. It is expanding faster than the visibility layer can cover it.
Attribution Failure
The inability to differentiate legitimate agents from malicious bots is not just a detection problem. It is an attribution problem.
When an incident occurs, the first question any investigation asks is which system or entity caused it. If the organization cannot distinguish its own agents from external bots in its traffic logs, the attribution question has no clean answer.
Incident response becomes a process of elimination rather than direct identification, extending investigation timelines and widening the window of ongoing exposure during containment.
The Non-Human Identity Problem
The root cause of the monitoring gap is the absence of verifiable non-human identity in most agent deployments.
Agents that share credentials with other systems, operate under service accounts designed for human use, or authenticate with API keys that carry no agent-specific identity cannot be individually identified in traffic logs. They look identical to any other authenticated request.
Monitoring tools designed to track human user behavior have no mechanism to distinguish agent A from agent B when both authenticate with the same credential.
What Monitoring Requires
Effective monitoring of non-human traffic requires that each agent carry a unique, verifiable identity that travels with every request it makes.
Not a shared service account. Not a generic API key. A cryptographic identity that is specific to that agent, bound to its authorized scope, and verifiable by any monitoring system that receives its traffic.
With that foundation, the 48.9 percent blind spot becomes a solved problem. Without it, the visibility gap grows with every new agent deployed.
Source: Salt Security's 1H 2026 State of AI and API Security Report