TL;DR: Employees are pasting sensitive business data into public AI systems, and traditional discovery controls often miss prompt-level exposure and model-governance risk, according to Protecto. Visibility now has to reach the point where data is entered into AI tools, not just where apps are installed.
Editorial analysis by NHI Mgmt Group, based on content published by Protecto: “Shadow AI vs Shadow IT: How to Detect and Govern Both”.
By the numbers:
- 75% of knowledge workers use AI at work, according to Microsoft’s 2024 Work Trend Index cited by Protecto.
Key questions
Q: What breaks when shadow AI is treated as ordinary SaaS sprawl?
A: Teams miss the real control problem, which is not the app itself but the data it can access and the identities it uses.
Q: How can organisations tell whether AI governance is actually working?
A: Organisations can tell AI governance is working when they can inventory every agent, explain its purpose, show who owns it, and prove that permissions are tightly scoped.
Q: How should organisations govern AI usage when employees use unapproved tools?
A: Organisations should start with visibility, not enforcement.
Practitioner guidance
- Define a separate shadow AI control set Create governance criteria that distinguish AI tools, AI-enabled applications, and generic shadow IT so teams do not apply the wrong detection and approval model.
- Add prompt and content monitoring Extend monitoring to prompt submissions, AI traffic patterns, and embedded AI features so sensitive data use can be detected before it leaves approved boundaries.
- Protect data before AI submission Use tokenisation, masking, or controlled de-tokenisation for sensitive fields that are likely to enter public or unmanaged AI systems.
Bottom line: Shadow AI is a distinct governance problem because the material risk often sits in the prompt and model interaction, not only in the application being used.
Glossary terms: Shadow AI, Shadow IT, Prompt Analysis, Context-based access control
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Shadow AI creates a governance gap that shadow IT controls do not close. Visibility into applications is necessary but no longer sufficient when the risk is the prompt, the model interaction, and the downstream reuse of output. That means the control plane has to expand from asset discovery to data-aware governance across AI workflows. Practitioners should treat this as a distinct control domain, not a subcategory of software sprawl.
A few things that frame the scale:
- 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 is the difference between governance visibility and data loss prevention for AI?
A: Governance visibility shows what already happened, while data loss prevention stops or shapes the action before it happens. For AI tools, that difference matters because the dangerous moment is often the paste or upload itself. Teams need both, but only one of them reduces immediate exposure.
👉 Read our full editorial: Shadow AI and shadow IT need different governance controls