Interactive · Shadow AI

Your staff already use AI. Shadow AI is the part you cannot see.

Contracts in a consumer chatbot. An AI sidebar reading your EHR. A note-taker recording client calls. Shadow AI moves regulated data outside your tenant in seconds, with no log and no way back. Estimate your exposure, then see how we shut it down without killing productivity.

NIST AI RMFMicrosoft PurviewBrowser controlDNS egressHIPAACMMC 2.0
Shadow AI estimator
30 seconds, no signup
critical risk
150
Most sensitive data your staff handle
AI usage policy today
17
Unsanctioned AI tools likely in use
63
Staff likely pasting company data
82
Shadow AI exposure score / 100
  • No technical control stops data leaving for a public model
    NIST AI RMF GOVERN 1.2 · CIS 3.3
  • No sanctioned AI tenant, so staff route around IT
    NIST AI RMF MAP 3.4 · CIS 2.1
  • AI browser extensions read every SaaS session your users open
    NIST CM-7 · CIS 4.8
Get the real number for your tenant

Directional estimate · real discovery runs against your tenant

[ 01 ]
4 in 10
Staff who paste work data into public AI
[ 02 ]
11 tools
Typical unsanctioned AI tools per 100 users
[ 03 ]
0 logs
Audit trail in a personal AI account
[ 04 ]
30-60 days
To sanctioned AI with enforcement live
The exposure

Six ways Shadow AI leaks data before anyone notices

None of these require a malicious insider. Every one of them is a well-meaning employee trying to move faster with a tool nobody told them not to use.

[ risk ]

Prompt-history data loss

Contracts, patient notes, CUI, payroll files, and source code pasted into consumer AI accounts. Retention is set by the vendor, not by you, and there is no e-discovery path.

[ risk ]

AI browser sidebars

Extensions that read every page a user opens, including your ERP, EHR, and finance systems, and forward that content to a third-party model.

[ risk ]

AI meeting note-takers

Bots joining calls with clients and staff, recording and transcribing conversations nobody consented to, and storing them outside your tenant.

[ risk ]

Silent SaaS AI features

AI toggles switched on inside apps you already pay for, sending your tenant data to a model provider under a sub-processor you never reviewed.

[ risk ]

Unreviewed AI-generated code

Generated snippets with vulnerable dependencies or hallucinated package names pushed into production by developers under deadline.

[ risk ]

Orphaned API keys

Personal model API keys embedded in scripts and automations. When the employee leaves, the integration keeps running and nobody owns it.

The control model

Discover, contain, allow, govern

Banning AI fails and ignoring it is worse. The programs that hold up under audit give staff one governed path and make every other path technically unavailable.

[ layer 01 ]

Discover

Named inventory of every AI tool, extension, OAuth grant, and AI endpoint in use, tied to the users and data categories touching them.

NIST AI RMF MAPCIS 2.1NIST CM-8
[ layer 02 ]

Contain

Block unsanctioned AI clients from executing, allowlist browser extensions, and stop sensitive paste and upload actions into public AI sites.

NIST CM-7CIS 4.8CMMC CM.L2-3.4.8
[ layer 03 ]

Allow

Stand up a sanctioned, licensed AI tenant with tenant-bound data, logged prompts, and role-scoped access so the approved path is the easy path.

NIST AC-6CIS 6.8SOC 2 CC6.1
[ layer 04 ]

Govern

AI acceptable-use policy, human-review requirements, vendor and sub-processor review, staff training, and monthly evidence for auditors.

NIST AI RMF GOVERNISO 42001HIPAA §164.308
Sanctioned vs shadow

Same prompt. Very different consequences.

The difference between a governed AI request and a shadow one is not the answer the model gives. It is everything that happens to your data around it.

[ shadow path ]

Personal account, personal device, no record

  • Data leaves your tenant the moment it is pasted
  • Retention and training terms set by the vendor
  • No DLP classification, no prompt log, no export
  • Access survives offboarding indefinitely
  • Unreviewable by an auditor or in litigation
  • Output re-enters your business with no provenance
[ governed path ]

Tenant-bound, logged, and revocable

  • Data stays inside your commercial tenant boundary
  • No training on your content, contractually confirmed
  • Sensitivity labels and DLP applied before submission
  • Every prompt and response retained for review
  • Access follows identity and dies at offboarding
  • Evidence pack ready for HIPAA, CMMC, and SOC 2
How it works

From unknown usage to a governed AI program

A repeatable rollout that gets you a named inventory fast, then enforcement, then a program that stays current as new AI features ship every month.

01

Discover

Identity, endpoint, browser, and egress telemetry combine into a named Shadow AI inventory: which tools, which people, which data.

02

Triage

Every tool is classified as sanction, replace, or block based on data sensitivity, vendor terms, and the business need behind the usage.

03

Enforce

Sanctioned AI goes live with guardrails while unsanctioned clients, extensions, and endpoints are blocked at the device, browser, and DNS layers.

04

Govern

Policy, training, and monthly reporting keep the program current as new models and features appear, with mapped evidence for audits.

[ start here ]

Get a named Shadow AI inventory in two weeks

We will show you the exact AI tools in use, who is using them, and what data categories are moving. No agents to buy first, no commitment to a platform before you see the findings.

FAQ

Shadow AI questions we hear a lot

Get started

Ready to make IT a strategic advantage?

Get a 30-minute call with our sales or support team. No pitch. Just a real assessment of where your IT and security stand today.