TL;DR: AI-driven security operations are moving into production faster than their governance models, according to Vectra AI. Identity and response programmes need tighter control over delegated access, cloud signals and automation as hybrid campaigns mix identity abuse with cloud compromise.
Editorial analysis by NHI Mgmt Group, based on content published by Vectra AI: “Cybersecurity Predictions 2026: AI, Agents, and SOC Defense”.
By the numbers:
- 46% of organisations plan to start using AI agents in security operations in 2026, according to Gartner’s 2025 Cybersecurity Innovations survey cited by Vectra AI.
- The article points to CVE-2025-14847 as the MongoBleed alert that kicked off security response over the 2026 holiday period.
Key questions
Q: Why do shadow AI tools create more identity risk than ordinary application sprawl?
A: Shadow AI often brings hidden identity relationships with it, such as OAuth grants, embedded secrets, and delegated API permissions.
Q: Should SOC teams use AI agents for investigation before response?
A: Yes, but only if investigation authority is tightly bounded and response authority remains separately controlled.
Q: What should security teams do when AI agents need access to tools and data?
A: Security teams should treat AI agents as runtime access actors and separate them from static machine identities.
Practitioner guidance
- Map AI agent permissions before production use Document every tool, dataset, and action path an agent can reach, then compare that scope with the business task it is meant to perform.
- Create an inventory of shadow AI and agentic workflows List approved and unapproved AI systems by owner, data access, and delegated action so hidden automation cannot bypass governance.
- Correlate identity telemetry across control planes Join identity, endpoint, cloud, and collaboration signals so abuse patterns can be reconstructed as one campaign instead of separate alerts.
Bottom line: AI-driven security operations are no longer hypothetical, but their governance model is still immature relative to the pace of deployment.
Glossary terms: Agentic IAM, Agentic Soc, Shadow AI, Delegated Authority Model
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
2026 will be defined by governance lag, not just attack innovation: the gap is no longer whether AI can participate in security operations, but whether programmes can define ownership, permission boundaries, and auditability fast enough for machines that act at runtime. That makes the control problem architectural rather than merely operational. The practical conclusion is that identity teams must govern agent behaviour as a first-class security domain.
A few things that frame the scale:
- 28% of secrets incidents now originate outside code repositories, in Slack, Jira, and Confluence, and are 13% more likely to be categorised as critical than code-based leaks, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: What does hybrid identity abuse mean for detection and response programmes?
A: It means defenders can no longer rely on separate views of cloud, endpoint, and identity activity. The response model has to correlate those signals into one attack narrative, or hybrid campaigns will keep slipping through the seams between teams and tools.
👉 Read our full editorial: AI SOC governance and agentic IAM define the next security risk