Mission

How to Audit and Control Shadow AI on Your Network

How to Audit and Control Shadow AI on Your Network

Know what attackers see before they do. See a live Radar report →

If you manage IT for a small business, you've probably heard some version of this from leadership: "Can you make sure employees aren't using unapproved AI tools?" And if you're honest, your answer is probably: you have no idea what AI tools your staff are already using.

That's the exact pain point driving discussions across IT and MSP forums right now, where admins are asking what actually works to restrict AI access for both on-prem and remote users. The honest answer is that blocking everything isn't realistic, and ignoring the problem isn't safe. You need a middle path: visibility first, policy second, enforcement last.

Why This Can't Wait

Two stories broke this month that should move AI governance up your priority list.

According to The Hacker News, malicious browser extensions can leverage Claude Dispatch to execute arbitrary code on an employee's machine. That means a tool your staff installed to "help with writing" or "summarize documents" could become a remote code execution vector — without the employee ever knowing.

At the same time, The Hacker News reported that researchers found a way to bypass ChatGPT's own Lockdown Mode and silently exfiltrate chat data without any user interaction. If you've been assuming the AI vendor's built-in security settings have you covered, this is proof that assumption is dangerous.

And zooming out, The Hacker News makes the broader case that the gap between AI capability and organizational readiness is accelerating faster than most IT teams can keep up with. Shadow AI isn't a future problem — it's already running on your network today.

Step 1: Find Out What's Actually Running

You can't govern what you can't see. Before writing a single policy, get a real inventory of AI usage across your network:

  • Pull DNS and proxy logs for known AI domains (chat.openai.com, claude.ai, gemini.google.com, perplexity.ai, and the dozens of smaller tools employees discover on their own)
  • Audit browser extensions across managed devices, since extensions are increasingly the delivery mechanism for AI-related exploits, as we covered in our browser extension security audit checklist
  • Review OAuth app permissions in Microsoft 365 or Google Workspace for any AI tool that's been granted access to email, files, or calendars
  • Ask department heads directly — shadow AI often starts as a sanctioned workaround to a slow approval process, similar to the patterns we outlined in our piece on shadow AI apps employees build on their own

Step 2: Tier Your AI Tools, Don't Blanket-Ban Them

A flat "no AI" policy usually fails because employees route around it, often through personal devices or personal accounts, which is worse for visibility than having them use an approved tool. Instead, create three tiers:

  • Approved — vetted tools with business accounts, data retention controls, and admin oversight (think enterprise ChatGPT or Copilot with proper settings configured)
  • Restricted — tools allowed for non-sensitive tasks only, with no company data permitted
  • Blocked — tools with no enterprise controls, unclear data handling, or a history of security issues

This tiering approach is the same logic we recommend in our broader AI governance and shadow AI data leakage guide — it keeps productivity intact while closing the biggest gaps.

Step 3: Enforce at the Network Layer, Not Just Policy Documents

A written policy without technical enforcement is a suggestion. Use your firewall, DNS filtering, or secure web gateway to:

  • Block known unapproved AI domains outright
  • Flag new AI tool traffic for review before it becomes normalized
  • Apply the same rules to remote and hybrid workers through endpoint-level DNS filtering, not just on-prem network rules

Step 4: Re-Audit on a Schedule

Shadow AI isn't a one-time cleanup. New tools launch weekly, and employees will keep finding workarounds. Set a recurring 30- or 60-day review of DNS logs, extension inventories, and OAuth grants so new risks don't sit unnoticed for months.

The Productivity Trap

The teams that struggle most with this are the ones that treat it as a security-versus-productivity tradeoff. It isn't. Giving staff one or two well-vetted, sanctioned AI tools with clear data rules almost always reduces shadow AI sprawl more effectively than a ban ever will. Employees want speed; give them an approved fast lane and they'll stop building their own.

Take Action

The exploits detailed above aren't hypothetical — they're active, documented, and targeting the exact kind of unmonitored AI usage happening on small business networks right now. Proactive scanning catches these exposures before an attacker does. Oscar Six Security's Radar gives you an affordable, fast way to check your network for unauthorized tools, risky extensions, and exposed access points for just $99 a scan. Check out our solutions and let's get ahead of it. Focus Forward. We've Got Your Six.

Frequently Asked Questions

How do I block AI tools on my company network?

Use DNS filtering or a secure web gateway to block known unapproved AI domains at the network and endpoint level, since blocking on-prem alone won't cover remote workers. Combine this with browser extension audits, since many AI-related exploits arrive through extensions rather than the AI website itself.

What is shadow AI and why is it a security risk?

Shadow AI refers to employees using AI tools that IT hasn't approved or vetted, often by pasting company data into personal AI accounts or installing unreviewed browser extensions. Recent research shows even mainstream tools like ChatGPT can be bypassed to leak data silently, making unmonitored shadow AI a real exposure point.

Should I ban AI tools completely at my small business?

A blanket ban usually backfires because employees route around it using personal devices, which reduces your visibility further. A tiered approach — approved, restricted, and blocked tools — tends to control risk without killing productivity.

How much does an AI security audit cost for a small business?

Costs vary widely depending on scope, but Oscar Six Security's Radar offers an affordable entry point at $99 per scan to identify unauthorized tools, risky browser extensions, and exposed access points on your network.

Can ChatGPT's security settings be bypassed?

Yes. Researchers recently demonstrated a method to bypass ChatGPT's Lockdown Mode and exfiltrate chat data without any user interaction, which means businesses should not rely solely on vendor-provided security controls and need their own network-level policies.

Step-by-Step Guide

  1. Inventory current AI usage

    Pull DNS/proxy logs, audit browser extensions, and review OAuth app permissions to see what AI tools are already running on your network.

  2. Tier AI tools by risk

    Classify tools as approved, restricted, or blocked based on data handling, admin controls, and business need rather than issuing a blanket ban.

  3. Enforce policy at the network layer

    Use firewall rules, DNS filtering, or a secure web gateway to block unapproved AI domains for both on-prem and remote/hybrid employees.

  4. Re-audit on a recurring schedule

    Repeat the inventory and policy review every 30-60 days since new AI tools and extensions launch constantly.

Find out what's exposed. Radar scans your external attack surface and shows you exactly what needs fixing. See a sample report →