Topic starter
02/08/2026 12:11 pm
TL;DR: APIs, AI agents, and MCP servers converged in 2025 to create a broader attack surface, with visibility gaps, shadow APIs, and agent misuse driving new security priorities according to Salt Security. The governance problem is no longer model risk alone: security teams now have to control actions, access, and context across the API layer.
Editorial analysis by NHI Mgmt Group, based on content published by Salt: “The 12 Months of Innovation: How Salt Security Helped Rewrite API & AI Security in 2025”.
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 do unmanaged APIs create a bigger risk in large platform environments?
A: Because scale turns small visibility gaps into structural blind spots.
Q: How can security teams tell whether API risk controls are actually working?
A: Look for reduced abuse volume, fewer successful automated attacks, and clearer visibility into which non-human clients are making requests and why.
Practitioner guidance
- Map exposed API actions to business owners Create an owner-to-action inventory that ties each high-risk API and MCP workflow to a named system owner, approval path, and review cadence.
- Classify AI agents as governed non-human identities Assign each agent a scoped identity, explicit tool permissions, and an approval boundary for sensitive API actions rather than letting it inherit broad application trust.
- Discover and retire shadow API paths Continuously find unmanaged, zombie, and orphaned endpoints, then decommission or re-own anything that still accepts production traffic without current governance.
Bottom line: API security is becoming an identity and governance problem because the highest-risk events now happen at the point of action, not at login.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 1:15 pm
API action-layer governance is the missing control plane for agentic systems. The article correctly shifts attention away from model outputs and toward the actions that AI systems can trigger through APIs. That is where business risk becomes operational risk, because the system is no longer merely generating text, it is creating effects in production. For identity teams, the key question is whether each action path has explicit authorisation and ownership.
A few things that frame the scale:
- 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, the protocol's first year of widespread adoption, according to the State of Secrets Sprawl 2026.
- 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 is the difference between API authentication and API authorization?
A: API authentication verifies who or what is making the request. API authorization decides what that identity is allowed to access or do. Strong authentication does not prevent misuse if authorization is broken, and strong authorization cannot compensate for stolen or poorly validated credentials. Both controls must work together at object, property, and function level.
👉 Read our full editorial: API action layer security is becoming the new AI attack surface