TL;DR: Shadow AI use spans browser sessions, endpoint agents, code repositories and sanctioned SaaS, according to Repello AI. Discovery has to cover those layers or the inventory will miss the most hidden AI paths.
Editorial analysis by NHI Mgmt Group, based on content published by Repello AI: “Shadow AI Detection: The 2026 Enterprise Playbook”.
Key questions
Q: Why do sanctioned credentials make embedded LLM calls hard to detect?
A: Because the call can look like normal application traffic.
Q: How do security teams decide which AI coding tools and models should be approved or blocked?
A: Security teams should evaluate AI coding tools using policy, reputation, access scope, and compliance fit.
Q: What breaks when shadow AI discovery only covers one layer?
A: A one-layer program misses entire categories of AI use because browser sessions, endpoint agents, code-level integrations, and SaaS features expose different signals.
Practitioner guidance
- Build a five-layer discovery workflow Scan network, browser, endpoint, code, and SaaS layers together so each category of AI use is visible in the same inventory.
- Classify every discovered AI use case Tag each item by data sensitivity, capability scope, ownership, and prevalence before deciding whether it should be sanctioned, permitted, or blocked.
- Add code-repository scanning to your AI audit Search repositories for SDK imports, direct provider calls, embedded prompts, and vector database usage so production code is not the blind spot.
Bottom line: Shadow AI is a governance and discovery problem that spans browser sessions, endpoint agents, code repositories, and sanctioned SaaS, so no single control layer is enough.
Glossary terms: Shadow AI, Embedded LLM API Call, MCP Server, AI Posture Management
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Shadow AI is now an access-governance problem, not just an acceptable-use problem. The article shows that the highest-risk AI usage often hides inside sanctioned credentials, local runtimes, and production code paths. That means the control failure is not simply user behaviour, but the absence of a complete discovery model across browser, endpoint, code, and SaaS layers. Practitioners should treat AI inventory as an identity and access question, not only a tooling question.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
- Organisations with high levels of shadow AI faced an average of $670,000 in additional breach costs compared with those with little or none, according to IBM's 2025 Cost of a Data Breach Report.
A question worth separating out:
Q: What should organisations do first when shadow AI appears in the environment?
A: Organisations should treat the tool as an unmanaged identity, then decide whether it is allowed to handle business data at all. The first 24 to 72 hours should focus on discovery, containment, and policy enforcement at the access boundary. If the tool cannot be governed inline, it should be denied by default.
👉 Read our full editorial: Shadow AI discovery fails when teams miss embedded LLM code paths