When an employee installs an AI writing assistant, connects a coding copilot to their IDE, or starts summarizing meetings with a new browser tool, they are doing exactly what a productive employee should do: finding faster ways to work.
Across most organizations today, employees are running three to five AI tools on any given day. Most were never reviewed by IT. A significant portion connect to corporate data through OAuth tokens or browser sessions, giving them access to shared drives, emails, and internal documents the employee never specifically intended to expose. Security teams often have no visibility into any of it.
This is the shadow AI gap, and it is widening fast. Most security tools were built to monitor email and network traffic flowing through the corporate network. A browser-based AI tool that connects to company data through a quick login approval bypasses those controls entirely, because it never passes through the corporate network at all.
According to Adaptive Security research, 80% of employees currently use unapproved generative AI applications at work, and only 12% of companies have a formal AI governance policy in place. The result is a growing disconnect between how employees work and what security teams can see.
A program that channels AI adoption into a safe, visible, approved path gives security teams the visibility they need and employees the tools they want. The five steps below show exactly how to build one.
Step 1: Build a Full Picture of What’s Running
A security program can only manage what it can see. The first step is discovering which AI tools are in use across the organization, and most security teams will find the answer surprising.
Three areas account for the majority of shadow AI activity.
-
OAuth connections. Most AI tools request access to Google Workspace or Microsoft 365 through OAuth, which grants them read or write permissions to corporate data. A quarterly audit of connected third-party apps, sorted by permission scope, usually surfaces dozens of tools the security team never reviewed.
-
Browser extensions. Many AI tools run as browser extensions and never touch the operating system, so traditional endpoint management tools miss them entirely. A browser management solution or a lightweight agent installed on employee devices can scan for and identify which extensions are active across the organization.
-
AI features bundled inside already-approved tools. Microsoft Copilot, Google Gemini, and Salesforce Einstein are examples of AI capabilities that may have been introduced after the original vendor review, often without a separate security evaluation.
A simple employee survey is also worth running. A survey framed around helping employees work more safely tends to get candid responses. Many shadow tools surface through surveys that automated discovery misses entirely.
The goal of this step is a current, accurate inventory: every AI tool in use, who is using it, and what data it has access to.
AI-powered social engineering has moved beyond email –– into voice, SMS, and deepfake video.
Adaptive Security protects teams by simulating attacks, measuring risk, and closing the gaps legacy SAT misses. CISO-grade defense for a new threat model.
Step 2: Write a Policy That Works With Employees
Most AI acceptable use policies stall for the same reason: they give employees a list of prohibited tools with no guidance on what the approved path looks like. A policy designed as a practical guide, one that identifies approved tools and provides a clear process for requesting new ones, is the foundation employees need to make good decisions.
An effective AI governance policy covers five things.
-
Clear data classification rules specifying which categories of data, including customer records, source code, and financial information, should never be entered into any AI tool.
-
A verified data training opt-out status for each approved tool. Many AI tools use company inputs to improve their models by default unless enterprise settings are explicitly configured otherwise. Approval should require confirmed opt-out for any tool that handles sensitive data.
-
A defined process for requesting new tools, with a target turnaround time.
-
A plain-language explanation of why the guidelines exist.
That last element matters more than it might seem. Employees who understand why OAuth connections carry data exposure risk apply that reasoning to every tool decision they make. Policy becomes a form of education when the reasoning is included.
Step 3: Create a Fast Lane for New Tool Requests
Shadow AI grows fastest in organizations where the official approval process cannot keep pace with the rate of AI product releases. An employee who needs a tool today and faces a six-week security review will find a workaround within days. The goal of this step is to remove that friction.
-
Most AI tool requests do not warrant a full procurement review. A structured intake form with defined evaluation criteria is enough for the majority of lower-risk tools.
-
A structured intake form and a defined set of evaluation criteria make faster decisions possible. For tools with limited data access, many organizations find a shorter turnaround feasible once evaluation criteria are documented and consistently applied.
-
The evaluation criteria should cover data access scope, vendor security practices, data training opt-out status, compliance certifications, and whether the tool already has a functional equivalent on the approved list.
Security teams that publish their approved tool list openly and keep it current typically see a meaningful reduction in shadow AI usage. When employees know where to find the right tools, they use them.
Step 4: Use Monitoring as a Shared Safety Layer
Continuous visibility into AI tool usage across an organization serves two groups simultaneously.
-
Security teams get the real-time picture they need to identify and address exposure before it becomes an incident.
-
Employees get a form of protection they often do not have on their own: a signal when a tool they are using may be putting their credentials or company data at risk.
A browser-native monitoring approach gives security teams visibility into AI activity without rerouting employee web traffic or adding friction to daily work. The signals it captures feed into each employee’s broader risk profile, sitting alongside their phishing simulation results and training completion data in one place.
That combined view matters because risky behaviors compound. An employee who clicks phishing links, skips training, and runs unapproved AI tools with access to sensitive data presents a much higher risk than any single behavior would indicate. Seeing the full picture in one place helps security teams focus on the employees who need attention most.
Step 5: Make Good Security Behavior Easy
Security programs that make the secure choice the easiest choice are the ones employees follow. In the context of AI governance, two things drive that: just-in-time coaching and training that explains the reasoning behind the rules.
Just-in-time coaching delivers a brief, contextual prompt at the moment an employee attempts to use an unsanctioned tool. This is more effective than quarterly training modules, because the intervention happens at the point of decision. A well-designed prompt tells the employee what the concern is, directs them to an approved alternative, and takes less than thirty seconds to read.
Training that explains the reasoning behind AI governance policies builds the kind of judgment employees can apply across any situation they encounter, including tools and threats that emerge long after the training itself. The AI tool landscape is changing fast enough that no training program can anticipate every specific case.
An employee who understands that OAuth connections to corporate Google Workspace can expose the entire shared drive to a third-party vendor will apply that understanding to tools that did not exist six months ago.
Building a Security Program Based on How Teams Work
AI adoption is a signal of productive teams doing their jobs well. Companies that build practical programs around that momentum, with clear paths to approved tools and real-time visibility for security teams, tend to handle it best.
Security teams that close that gap find that shadow AI usage declines organically over time. Browser-native visibility, clear paths to approved tools, and just-in-time coaching at the moment of risk are what make that possible.
When employees have access to effective, approved tools and a fast, transparent path to get new ones reviewed, the incentive to work around the system largely disappears.
Adaptive Security’s AI Governance product gives security teams real-time visibility into every AI tool and shadow app running across their organization, with automated policies and just-in-time employee coaching built in.
Learn more at adaptivesecurity.com.
Sponsored and written by Adaptive Security.
