How Do You Detect Unauthorized AI Tool Usage?

Organizations that cannot detect unauthorized AI usage cannot enforce AI policy, quantify data risk, or pass compliance audits. Detection is the foundation of AI governance. Here is how each method works, what it catches, what it misses, and why you need all three for complete coverage.

Three Methods Compared

Each detection method operates at a different layer of the technology stack, giving it unique strengths and blind spots.

Browser Extension Monitoring

Browser monitoring provides the richest data about AI tool usage. A managed browser extension observes navigation events and reports visits to known AI domains.

What it catches:

• Visits to AI tool websites (ChatGPT, Claude, Gemini, Perplexity, etc.) with exact timestamps
• User identity tied to every visit through browser profile or device enrollment
• Time spent on AI tools, distinguishing between brief visits and extended sessions
• Navigation patterns that indicate data input (visiting an AI tool immediately after viewing sensitive internal documents)
• New AI tools as they emerge, if the extension maintains an updated domain list

What it misses:

• AI tools used on personal devices or unmanaged browsers
• Desktop AI applications (Cursor, local LLMs) that run outside the browser
• Mobile AI app usage on personal phones
• AI features embedded within approved applications (Notion AI, Canva AI) that share a domain with the non-AI product
• Usage on incognito or guest browser profiles if the extension is not force-installed

Browser monitoring is the highest-value starting point because it provides user-level attribution. Knowing that a specific person visited a specific AI tool at a specific time is the foundation of enforcement.

OAuth Integration Monitoring

OAuth monitoring detects AI applications that employees have connected to their corporate Google Workspace or Microsoft 365 accounts.

What it catches:

• AI tools that employees authorized to access corporate email, documents, or calendar data
• The specific permissions each AI app was granted (read email, access Drive, manage calendar)
• When the authorization occurred and who granted it
• Third-party AI apps in the Google Workspace Marketplace or Microsoft AppSource that employees installed

What it misses:

• AI tools used via direct web access without SSO integration
• Personal account usage (employee logs into ChatGPT with a personal email, not corporate SSO)
• AI tools that do not use OAuth (most AI tools used via web browser do not request OAuth permissions)
• Usage volume or frequency (OAuth shows the connection exists, not how often it is used)

OAuth monitoring is low-effort and high-impact for a specific threat: AI applications that have been granted access to corporate data through identity provider integrations. A single unauthorized OAuth grant can give an AI tool persistent access to corporate email or documents.

DNS Monitoring

DNS monitoring captures all network-level connections to AI service domains, regardless of how the connection is made.

What it catches:

• Every device on the corporate network or VPN connecting to AI services
• API-level AI usage (scripts, automations, and backend services calling AI APIs)
• AI tool usage from any application type: browser, desktop app, mobile app, command-line tool
• Volume of requests to each AI domain, indicating intensity of usage

What it misses:

• Which specific user made the request (DNS resolves at the device or network level, not user level)
• What data was sent or received (DNS only shows the domain, not the payload)
• AI usage on personal devices using cellular data or personal Wi-Fi
• AI services accessed through VPN endpoints that bypass corporate DNS

DNS monitoring is the broadest detection method. It catches AI usage that browser monitoring and OAuth monitoring miss, including desktop applications, command-line tools, and automated scripts. The tradeoff is low data richness: you know something connected to an AI service, but not who or why.

Why You Need All Three

Each method covers the gaps left by the others. The coverage matrix shows why a single method is insufficient.

Browser monitoring provides identity and context. OAuth monitoring catches persistent data access grants. DNS monitoring provides breadth. Together, they create a detection net that catches the vast majority of unauthorized AI usage within your environment. For understanding the risks that unauthorized usage creates, see our shadow AI risk analysis. For building the governance program that acts on detection findings, read our AI policy and governance guide.

Frequently Asked Questions

Which detection method should we implement first?

Browser extension monitoring. It provides the highest data richness (user identity, tool, timestamp, duration) with the lowest setup complexity. You can deploy a browser extension to managed Chrome or Edge browsers in hours through your endpoint management platform.

Can employees bypass AI detection?

Individual methods can be bypassed. Employees can use personal devices to avoid browser monitoring, use personal email accounts to avoid OAuth detection, or use cellular data to avoid DNS monitoring. The three-method approach makes comprehensive evasion difficult, requiring an employee to avoid all corporate infrastructure simultaneously.

Does DNS monitoring require a proxy or firewall?

No. DNS monitoring operates at the DNS resolver level. By routing corporate DNS through a resolver that logs AI-related domains, you capture connection data without deploying a proxy or modifying firewall rules. Most organizations can implement this by updating their DNS resolver configuration or using a cloud DNS service with logging capabilities.

How do you handle false positives in AI detection?

Maintain a curated allowlist of approved AI tools and domains. Flag only connections to unapproved AI services. Review flagged events weekly to identify false positives (for example, a marketing site that shares infrastructure with an AI service) and update the allowlist. Automated classification reduces false positives over time.

Is employee consent required for AI usage monitoring?

On company-owned devices and networks, most jurisdictions allow monitoring with disclosure. Include AI monitoring in your acceptable use policy and employee handbook. In the EU, GDPR requires a legitimate interest assessment and employee notification. In some US states, specific consent requirements apply. Consult your legal team for jurisdiction-specific requirements before deploying monitoring tools.