Topic starter
02/08/2026 11:54 am
TL;DR: 1,233% growth in Claude Desktop use and an 80% rise in GenAI SaaS data movement show how quickly professional services workflows are shifting, from Cyberhaven's survey and telemetry. Control over those workflows now depends on identity, session, and data handoff points, not policy on its own.
Editorial analysis by NHI Mgmt Group, based on content published by Cyberhaven: “Cyberhaven 2026 AI Adoption & Risk Report: Professional Services”.
Key questions
Q: Why does fragmented AI infrastructure create security risk?
A: Fragmented AI infrastructure creates risk because each provider handoff can split responsibility for credentials, permissions, and logging.
Q: How do security teams know if AI governance is working?
A: Look for evidence that access decisions are reviewable, permissions are revocable, and exceptions are not becoming permanent.
Q: What breaks when AI adoption outpaces governance?
A: What breaks first is attribution.
Practitioner guidance
- Map all AI usage paths Inventory sanctioned GenAI SaaS, endpoint AI applications, personal accounts and agent workflows so governance reflects real usage rather than approved-tool assumptions.
- Bind AI access to identity and lifecycle controls Define ownership, approval, privilege scope and offboarding for human users, service accounts and AI agents that touch sensitive work data.
- Control sensitive data at prompt and handoff points Apply data handling rules where content is entered into AI systems, transformed by them or passed into downstream tasks, not only where it is stored.
Bottom line: Professional services AI adoption is spreading across multiple tool types and access paths faster than governance can consistently track.
Glossary terms: AI Governance, Agentic AI, Control-plane sprawl, Sensitive Data Exposure
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 2 days ago by NHI Mgmt Group
02/08/2026 1:02 pm
AI adoption governance is now a control-plane problem, not a policy problem. Once employees distribute AI usage across SaaS apps, endpoint tools and unmanaged environments, the enterprise loses the ability to enforce a single governance model. That breaks the assumption that one approved catalog or one identity boundary can describe actual AI use. Practitioners should treat governance as an operating-state issue, not a document-review exercise.
A few things that frame the scale:
- Organisations that describe themselves as confident in their AI deployment actually experience a 72% security incident rate, compared to 33% for those who remain cautious, according to the 2026 Infrastructure Identity Survey.
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How should organizations approach the governance of AI agents?
A: Organizations should adopt a governance framework that incorporates continuous visibility, adaptive IAM practices, and stringent policy-based controls. This ensures that all agent actions are tracked, authorized appropriately, and assessed for compliance.
👉 Read our full editorial: AI adoption is outpacing governance in professional services
This post was modified 2 days ago by NHI Mgmt Group