Topic starter
02/08/2026 11:54 am
TL;DR: AI usage is spreading across GenAI SaaS apps, endpoint AI applications, and AI agents while governance and visibility lag, with employees also using personal and unmanaged environments, according to Cyberhaven’s manufacturing-focused 2026 AI Adoption & Risk Report. The result is a fragmented control surface where data exposure rises faster than security teams can see or govern it.
Editorial analysis by NHI Mgmt Group, based on content published by Cyberhaven: “Cyberhaven 2026 AI Adoption & Risk Report: Manufacturing Industry”.
Key questions
Q: What breaks when AI governance is not aligned to how employees actually use AI?
A: AI governance breaks when policy is built around approved tools instead of real usage paths.
Q: Why do unmanaged AI accounts increase data exposure risk?
A: Unmanaged AI accounts remove policy continuity between the user, the device, and the destination service.
Q: How should security teams govern AI agents that can access enterprise systems?
A: Security teams should govern AI agents as non-human identities with explicit ownership, scoped privileges, and continuous monitoring.
Practitioner guidance
- Map every AI access path Inventory GenAI SaaS apps, endpoint AI applications, personal accounts, and AI agents that can reach company data.
- Apply policy to unmanaged AI use Define which data types may never be pasted into personal or unmanaged environments and enforce that boundary with DLP, browser, and endpoint controls where possible.
- Treat AI agents as runtime identities Assign owners, scopes, and revocation criteria to AI agents before they are allowed to act on behalf of users or teams.
Bottom line: AI adoption in manufacturing is widening the gap between where work happens and where governance can actually see it.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 1:02 pm
AI adoption in manufacturing is now an identity-governance problem, not just an enablement problem. Once employees can shift between GenAI SaaS apps, endpoint AI tools, personal accounts, and AI agents, the security boundary follows the user instead of the platform. That breaks the assumption that a single IAM policy set can describe who may touch what. Practitioners should treat AI adoption as a control-surface expansion that demands identity-aware governance.
A few things that frame the scale:
- 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: When should organisations unify IAM, AI governance, and data security controls?
A: Organisations should unify those controls as soon as AI use spans multiple accounts, unmanaged environments, or agentic workflows. At that point, separate policy teams cannot reliably answer basic questions about access, data handling, and accountability. A shared governance model is the only way to keep control boundaries intelligible.
👉 Read our full editorial: AI adoption is outpacing governance in manufacturing enterprises