Topic starter
02/08/2026 11:48 am
TL;DR: Security leaders report that 48.9% of organisations are blind to machine-to-machine traffic, 48.3% cannot distinguish legitimate AI agents from malicious bots, and 78.6% face heightened executive scrutiny while only 23.5% rate existing tools as very effective, according to Salt Security's 1H 2026 State of AI and API Security Report. The operational problem is no longer prompt control alone, but governance over the APIs, identities, and MCP-connected workflows that autonomous agents actually use.
Editorial analysis by NHI Mgmt Group, based on content published by Salt: “The Era of Agentic Security is Here: Key Findings from the 1H 2026 State of AI and API Security Report”.
By the numbers:
- 48.9% of organisations are entirely blind to machine-to-machine traffic.
- 48.3% of organisations cannot distinguish legitimate AI agents from malicious bots.
- 78.6% of security leaders report increased executive scrutiny of AI security risks.
Key questions
Q: What breaks when AI agents can reach exposed internal APIs?
A: The break point is governance, not just security tooling.
Q: Why does the agentic action layer create more risk than prompt security alone?
A: The agentic action layer creates more risk because the damage happens where the agent executes actions, not where it generates text.
Q: What are the signs that AI agent observability is failing?
A: The main signs are missing tool metadata, disconnected traces between agent hops, unexplained retries, and an inability to reconcile a successful call with the actual state change it caused.
Practitioner guidance
- Map agent-to-API dependencies Build an inventory of every AI agent, MCP server, and downstream API it can invoke, then record the business purpose and owner for each path.
- Bind each agent to a unique identity Assign non-shared credentials or workload identities so every agent action can be traced, scoped, and revoked without affecting other systems.
- Monitor machine-to-machine traffic for drift Baseline normal agent behaviour and alert on unusual call sequences, bulk pulls, new endpoints, or tool use outside approved workflows.
Bottom line: AI agents are pushing security teams to govern the execution layer, where APIs, MCP servers, and delegated access create the real exposure.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 12:58 pm
Agentic action layer visibility is now the governance problem, not a side issue: once AI agents operate through APIs, MCP servers, and internal services, security controls must follow the action path rather than the model prompt. The real exposure is in the execution layer where non-human actors can reach sensitive systems without human-style sessions. Practitioners should treat agent traffic as governed production behaviour, not experimental AI usage.
A few things that frame the scale:
- Systems with least-privileged AI access had a 17% incident rate vs 76% for over-privileged systems. Organisations failing to scope AI access properly are 4.5x more likely to experience a security incident, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How should teams govern AI agents that can reach APIs, events, and memory?
A: Teams should govern those agents as runtime identities, not as isolated integrations. That means enforcing policy at execution time, logging every tool and data access, and binding actions back to a clear initiating workflow or identity. If the control plane cannot show who acted, what they reached, and why, the programme does not have usable governance.
👉 Read our full editorial: AI agent visibility gaps are exposing the agentic action layer