Topic starter
01/08/2026 8:58 pm
TL;DR: Agentic AI is shifting work into machine-speed workflows, and Cyberhaven says endpoint agentic AI adoption doubled year over year to 60% of enterprises in May 2026. The security gap is that traditional point tools still lose context once data moves, so governance has to follow the workflow, not the checkpoint.
Editorial analysis by NHI Mgmt Group, based on content published by Cyberhaven: “Securing the Agentic Enterprise”.
By the numbers:
- endpoint agentic AI adoption doubled year over year, reaching 60% of enterprises in May 2026.
Key questions
Q: How should security teams govern agentic workflows that are built from real user activity?
A: Security teams should govern them as delegated identities with explicit ownership, approval, scope, and revocation.
Q: Why do role-based controls struggle with agentic AI?
A: Role-based controls struggle because agents do not behave like stable process actors.
Q: What breaks when teams treat autonomous agents like service accounts?
A: Teams lose visibility into dynamic decision-making, tool choice, and action timing.
Practitioner guidance
- Map your highest-value workflows Identify the cross-functional workflows that move proprietary or regulated data across multiple systems, teams, and identities.
- Bind policy to data lineage Require controls to retain provenance, destination, and identity context as data moves from source systems into prompts, browsers, and downstream applications.
- Classify agent actions separately from human actions Track whether a request was made by a person, a workload, or an autonomous agent, then scope permissions and logging accordingly.
Bottom line: Agentic enterprise security fails when controls stop at a checkpoint and cannot follow data across the workflow.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
01/08/2026 9:05 pm
Workflow-aware governance is becoming the defining control plane for agentic enterprises. Security teams can no longer rely on repository-centric or checkpoint-centric controls when work is assembled across many systems and identities. The relevant governance unit is the workflow, because that is where intent, lineage, and business context are created and lost. Practitioners should treat workflow visibility as a core governance requirement, not an optimisation.
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: How do organisations know if identity-driven workflow security is working?
A: They should look for fewer password resets, fewer access exceptions, faster detection of anomalous access, and fewer cases where users need to bypass controls to get work done. If security improves while operational friction falls, the identity model is supporting the workflow instead of fighting it.
👉 Read our full editorial: Agentic enterprise security depends on workflow-aware data controls