Find out where AI is used in my org COMING SOON
Surfaces used: Shadow AI Scout Modes supported: Hosted Tiers: Teams Status: COMING SOON
This use case is not deliverable today. Scout has no installer, and the Shadow AI dashboard routes are redirected in every environment. Everything below describes intended behaviour so you can plan for it.
What you'll do
When Scout ships you will get a map of every AI tool your workforce is actually using -- including the ones IT does not know about. Scout will ingest endpoint telemetry, classify each tool by vendor and risk, and show you a ranked list of what to govern first.
Why this is the right path for you
- If your first question is "where is AI being used here?" and you need evidence before you can propose controls, start here.
- Scout is a discovery tool. It does not block anything on its own. Once you know where AI is happening, pair Scout with the right enforcement surface:
- Browser-based AI -> browser extension
- API traffic from apps -> gateway
- Coding assistants on dev laptops -> coding hooks
When NOT to use this approach
If you already know what you want to govern (e.g., "we use Claude Code and I need guardrails"), skip Scout and go straight to the relevant surface. Scout pays off when you do not have the map yet.
Planned setup
These are the three ingestion paths Scout is being built to. Commands are omitted deliberately rather than shown in a form that would fail, or leak an API key, if you pasted it.
Endpoint agent (most detail)
An agent installed on each laptop, enrolled against your org, watching for known AI processes and browser tabs and reporting on an interval. This is the path that will give the most detail, because it sees the process, not just the hostname.
Network / proxy log ingest
For orgs already running a forward proxy (Zscaler, Netskope, a corporate Squid), an HTTP ingest that accepts the proxy's access logs. No endpoint agent to deploy, less detail per event.
DNS log ingest
The same shape as proxy ingest, fed from DNS query logs. The broadest reach and the least detail: it tells you a host was resolved, not who did it or what was sent.
What you will be able to verify
When Scout ships, these are the checks that will tell you it is working:
- Dashboard -> Shadow AI shows hostnames (e.g.,
api.anthropic.com,claude.ai,chatgpt.com,copilot.github.com) with request counts and first-seen / last-seen timestamps. - The top of the page ranks tools by estimated risk and volume.
- Clicking any tool shows which endpoints / users / accounts are hitting it, exportable to CSV for your report.
Common follow-ups
- "Now I want to block claude.ai leaks" -> Browser extension
- "Now I want to govern OpenAI API calls from our apps" -> Gateway
- "Now I want to govern devs using Claude Code" -> Coding hooks
- "I need a compliance report on this discovery" -> Compliance reports
Reference
- Surface page: Shadow AI Scout
- Concepts: Feature availability
- API: API reference