TL;DR: Employees are using AI tools and agents without formal approval, with Lumia Security noting shadow AI now reaches sanctioned tools, embedded features, and autonomous agents. Discovery and traceability need to cover prompts, data, identities, and downstream actions before policy can be enforced.
Editorial analysis by NHI Mgmt Group, based on content published by Lumia Security: “6 Shadow AI Risks that Can Disrupt Enterprise AI Usage”.
By the numbers:
- 63% of organisations lacked AI governance policies to manage AI or prevent the proliferation of shadow AI, according to IBM's 2025 Cost of a Data Breach Report cited by Lumia Security.
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: How can security teams tell whether AI lifecycle controls are working?
A: They should look for evidence that access requests, policy enforcement, and usage visibility are centrally recorded and current.
Q: What is the first control teams should put in place for shadow AI?
A: Start with discovery. Security teams cannot govern what they cannot see, so the first control is a live inventory of AI tools, embedded features, and agents in use. That inventory should include who is using them, what data they touch, and which identities or tokens they rely on. Without that baseline, every later policy, review, or restriction is partly guesswork.
Practitioner guidance
- Build a continuous inventory of AI usage Discover standalone chatbots, coding assistants, browser extensions, embedded AI features, and autonomous agents across the business, then refresh the inventory continuously as tools and workflows change.
- Classify AI use by data sensitivity and business impact Score each use case by the type of data involved, the user role, the trustworthiness of the tool, and the possible operational impact so controls match actual risk.
- Define policy by use case, not by broad tool category Write separate rules for summarisation, coding, forecasting, customer communications, and agent actions so the policy reflects what the AI is doing rather than just which brand it belongs to.
Bottom line: Shadow AI is not a narrow chatbot problem. It is a governance gap that spans sanctioned tools, embedded features, and autonomous agents.
Glossary terms: Shadow AI, Interaction-level monitoring, Agentic AI, AI usage control
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Shadow AI is fundamentally an access governance problem, not just a content or productivity problem. Once AI tools can ingest data, generate outputs, and act through agents, the security question becomes who or what is allowed to do those things. That shifts the control point from simple tool approval to identity, permission, and usage governance. Practitioners should treat unmanaged AI as a governed access surface, not a side channel.
A few things that frame the scale:
- One in five organisations reported a breach due to shadow AI, and 97% of those breached through an AI model or application lacked proper AI access controls, according to IBM's 2025 Cost of a Data Breach Report.
A question worth separating out:
Q: When should organisations require human approval for an AI agent action?
A: Require human approval when the action could change infrastructure, expose sensitive data, move laterally across systems, or trigger a business-critical workflow that is hard to reverse. Approval is also warranted when the agent’s decision depends on ambiguous input or external data that cannot be trusted at face value. High-consequence actions need a human stop point.
👉 Read our full editorial: Shadow AI risks grow when enterprises lack usage visibility