Topic starter
02/08/2026 11:39 am
TL;DR: Enterprise endpoint AI use grew 509% year over year, while coding assistants rose 357% and Claude 5,680%, according to Cyberhaven Labs data on hundreds of thousands of employees. The finding shows that adoption velocity, not tool popularity, is now the governance variable that determines exposure.
Editorial analysis by NHI Mgmt Group, based on content published by Cyberhaven: “The Fastest-Growing AI Categories in the Enterprise Are Also the Riskiest”.
By the numbers:
- Total enterprise use of endpoint-based AI native apps grew 509% in a single year, from February 2025 to February 2026.
- Enterprise adoption of coding assistants grew 357% year over year.
- Engineering accounts for 33% of all AI native app usage across the enterprises in the Cyberhaven dataset.
Key questions
Q: What breaks when coding assistants are allowed broad endpoint access?
A: Broad endpoint access breaks the assumption that AI tools are only reading prompts.
Q: Why do fast-growing endpoint AI tools create governance risk even when approved?
A: Approval does not solve governance if usage expands faster than policy coverage.
Q: What are the signs that AI governance is failing in a mixed Windows and Mac estate?
A: The clearest signs are uneven visibility, tool-specific blind spots, and policies that only cover one dominant platform.
Practitioner guidance
- Define endpoint AI inventory and ownership Map every AI native app and coding assistant in use across managed endpoints, including browser, desktop, and agentic variants.
- Constrain coding assistant access to minimum required scope Limit repository, file system, environment variable, and command execution access to the least amount needed for the developer task.
- Expand detection beyond sanctioned AI brands Build telemetry and DLP rules that detect AI usage patterns at the endpoint layer, not just approved vendor names.
Bottom line: The core problem is not AI popularity but the speed at which endpoint tools enter high-value workflows before governance catches up.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 12:51 pm
Adoption velocity is now the primary governance variable for enterprise AI risk. Security teams that still organise controls around the most popular model or the most visible SaaS app are managing the wrong denominator. The real exposure grows where endpoint AI tools spread fastest while control coverage lags behind. Practitioners should rebase governance on device-level usage, data sensitivity, and workflow access.
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 should security teams govern AI-assisted data movement across endpoints?
A: Security teams should govern AI-assisted data movement by starting at the endpoint, where content is opened, copied, transformed, and redistributed. They need lineage-aware policy that tracks how information moves across applications and identities, including non-human actors. Without that sequence, teams can neither distinguish normal use from risky propagation nor enforce controls before exposure spreads.
👉 Read our full editorial: Coding assistants are widening the enterprise AI governance gap