How to Detect Shadow AI in a Small Business
QUICK ANSWER
To detect Shadow AI (AI tools employees use without approval) in a small business, combine six signals: ask staff, review app sign-ins and OAuth grants, check browser activity, review DNS or firewall logs, audit AI features inside the software you already pay for, and check expense reports. No single signal sees everything, so use at least three and repeat the check monthly.
WHY SHADOW AI IS HARD TO SEE
Shadow AI rarely needs an install. Most AI tools run in a browser tab on a personal account, so traditional software inventories miss them. AI is also increasingly built into tools you already approved, such as email, document editors and CRMs, where it can be switched on without IT knowing. Detection is about combining signals, not finding one perfect report.
SIX WAYS TO DETECT SHADOW AI
| Method | What it finds | Effort | What it misses |
|---|---|---|---|
| 1. Staff survey | Tools people admit to using, and why | Low | Anything people forget or hide |
| 2. Sign-ins and OAuth grants | AI apps connected to company accounts | Low | Personal accounts |
| 3. Browser activity | AI sites and extensions used on company devices | Medium | Personal devices |
| 4. DNS or firewall logs | Traffic to known AI domains | Medium | Off-network use, encrypted detail |
| 5. Built-in AI features audit | AI switched on inside approved software | Low | New features added later |
| 6. Expense and card review | Paid AI subscriptions | Low | Free tools |
1. Ask your staff
Send a short, non-punitive survey with two questions: "Which AI tools have you used for work in the last month?" and "What did you use them for?" Make clear the goal is to approve useful tools, not to punish anyone. People share more when they expect a yes.
2. Review sign-ins and OAuth grants
In Microsoft 365 or Google Workspace, review which third-party apps employees have connected with "Sign in with Microsoft" or "Sign in with Google," and which permissions those apps hold. AI note-takers, writing assistants and meeting bots often show up here with access to mail, calendars or files.
3. Check browser activity
Browser history and installed extensions on company devices show which AI sites people visit and which AI extensions they added. A managed browser extension can do this continuously instead of by hand.
4. Review DNS or firewall logs
If your firewall or DNS filter keeps logs, search them for traffic to well-known AI services. This catches use from any device on your network, but not from home or mobile data.
5. Audit AI features in software you already use
List your top ten business applications and check each one's settings for AI features: assistants, summaries, auto-drafting, transcription. Note which are on, who turned them on, and what data they can read.
6. Review expenses
Search card statements and expense reports for AI subscriptions. Paid tools are often the ones handling the most business data.
WHAT TO DO WHEN YOU FIND IT
- Sort, don't ban: Group findings into approve, approve with limits, and stop. Blanket bans push use further out of sight.
- Write the rules down: Turn your decisions into an approved-tools list and data rules. Our free AI Acceptable Use Policy template gives you a starting point.
- Offer a safe alternative: If staff use a personal chatbot, give them an approved company account.
- Check again monthly: New tools appear constantly. A one-time check goes stale within weeks.
A SIMPLE MONTHLY CHECKLIST
- Survey: Re-ask the two questions each quarter, and to every new hire.
- Connected apps: Review new OAuth grants for AI apps.
- Browser and network: Compare AI sites and extensions seen this month with your approved list.
- Built-in features: Check release notes of your main apps for new AI features.
- Expenses: Flag new AI subscriptions.
- Policy: Update the approved list and tell staff what changed.
FOR MSPS: RUN THIS AS A SERVICE
Managed service providers can turn this checklist into a recurring Shadow AI review for every client, paired with a white-labeled acceptable use policy. See the MSP White-Label AI Governance Playbook and RAIC for MSPs.
HOW RAIC AUTOMATES DETECTION
Doing this by hand works, but it takes hours each month. RAIC replaces the manual steps:
- Continuous detection: RAIC continuously detects supported AI services and model activity using browser and Microsoft 365 signals, with detections matched against its curated AI catalog.
- Approved-list comparison: see which detected tools are approved, pending or not yet reviewed.
- Approvals with evidence: route new-tool requests to the right approver, with a record of who approved what and when.
- Reports: export your AI inventory for leadership, clients and insurers.
A policy is one part of a wider AI governance program. For the bigger picture, read Shadow AI: The SMB Guide or see the Shadow AI page.
NEXT STEPS
- Start a free trial: raic.rhindoncyber.com/pricing
- Book a demo: raic.rhindoncyber.com/demo
- Partner and MSP inquiries: [email protected]
Rhindon AI Risk & Integrity Cloud | raic.rhindoncyber.com | © 2026 Rhindon Cyber
FAQ
How do you detect Shadow AI?
Combine several signals: ask staff, review app sign-ins and OAuth grants, check browser activity, review DNS or firewall logs, audit AI features in software you already use, and check expenses. Repeat the check monthly.
Can a small business detect Shadow AI without special tools?
Yes. A staff survey, a review of connected apps in Microsoft 365 or Google Workspace, and an expense review cost nothing. Dedicated tools make detection continuous and save time.
Why is Shadow AI hard to detect?
Most AI tools run in a browser on personal accounts with nothing installed, and AI features are increasingly built into software that was already approved.
What should I do after finding Shadow AI?
Sort tools into approve, approve with limits, and stop; write the decisions into an AI acceptable use policy; give staff approved alternatives; and check again monthly.
Bring AI governance into one platform
Start a free trial of RAIC and operationalize the practices in this article.
Start trial