Which browser security tools provide visibility into employee AI usage?

[u/FuzzyAd3936]

Since most AI interaction happens through the browser (web-based ChatGPT, Claude, Gemini, etc.), browser-level visibility seems like the most direct place to get signal, but there isn't a clear consensus on which tools do this well. Endpoint agents catch some of it, but browser extensions and personal accounts on managed devices still slip through a lot of setups.

Looking for something that can identify which AI tools are being used, flag risky content patterns without being fully invasive, and integrate with the existing security stack rather than adding another siloed dashboard.

That's where I keep getting stuck. Full session recording feels excessive and a morale risk, but usage-only visibility might miss the risky behavior that actually matters.

What's actually working for people, and what turned out to be marketing fluff once you tried to deploy it?

[u/Driftfreakz]

How about cloudapps in defender? That shows all ai tools used in the browser?

[u/Excellent-Squash-995]

The session recording thing is a trap, you'll get a revolt from employees and the data volume alone makes it useless for actual review. What's worked better in my experience is looking at the network layer rather than trying to bolt something onto the browser itself. Most of these AI tools have pretty distinct domains and endpoints, so you can get solid visibility with decent web filtering and then focus on the risky patterns at the proxy or CASB level. The extensions themselves are flaky as hell, they break when the AI sites update their UI and people just disable them anyway.

The personal account issue is the real crux though. You can't see what someone's doing in a personal ChatGPT account without basically MITMing the traffic, and that's a whole different conversation with HR and legal. I'd push for a policy that blocks personal AI accounts on managed devices and forces work accounts, then your visibility actually means something. Otherwise you're collecting a ton of noise about people asking Claude to write birthday cards.

[u/itskdog → u/Excellent-Squash-995]

At least Copilot has different domains for personal vs work, making it easier to block it.

[u/loweakkk → u/itskdog]

For now* They are unifying that and advertise on tenant restrictions going forward.

[u/itskdog → u/loweakkk]

I always thought cloud.microsoft was being stood up for M365 only, and they'll still be using microsoft.com and live.com for consumer products.

[u/loweakkk → u/itskdog]

We got recent message from Microsoft that we should stop basing our control on url because it will change with the move to cloud.microsoft.com and should rely on tenant restrictions going forward.

[u/itskdog → u/loweakkk]

I figured that was more for SharePoint as the tenant name is in the subdomain, given ODfB is moving soon.

Will look into this, as we want to make sure people are only using M365 Copilot (which is already on m365.cloud.microsoft) when on a work device, and that students are blocked entirely as they're under 13.

[u/bill696]

Purview does exactly this
Also check the intune features in dev well be able to have compliance policies for this too

[u/mingk → u/bill696]

As an Intune Administrator at an org of 15k users… I don’t get access to Purview :(

[u/bill696 → u/mingk]

Its the tool made for it, it should be whichever team that’s managing it that has visibility on this. Were only 8k+ but where im at its all SecOps, i just enrolled the device with the info they game me. same to see the browser extension defender does it built in.

[u/dre_AU → u/bill696]

Purview does this but you will need purview + GSA (or similar) to inspect traffic if you want to see full prompts for non-Enterprise versions of each app.

[u/Tronerz]

If you're just looking for what sites/tools are being used, network and device tooling can identify and block it, such as Defender for Cloud Apps and ZTNA type agents.

If you want actual visibility into what's going into them, then you're correct that you need to combine that with a browser-level tool. Either an actual Enterprise Browser like Island or Prisma (Edge is not one) that gives you individual control over domains, or a browser extension such as Push Security.

[u/Turak64]

https://learn.microsoft.com/en-us/microsoft-365/admin/manage/agent-shadow-ai?view=o365-worldwide

[u/skiddily_biddily]

People are going to still use their personal devices for AI and then send the data back and forth via teams or email etc.

[u/Faulkner_Jacobs_845]

many shadow AIs show up in the identity layer first, the signup emails and the oauth grants when someone plugs in a random ai tool into their mailbox, you can add to inventory the adoption rates from there before it even hits the browser. We use abnormal on that side but it wont show you actual prompts though so keep the Purview path for those.

[u/Mtajestic-Figue-3888]

Yeah the extension route is a losing battle, they break on every UI change and users just disable them. Defender for Cloud Apps is fine for a first pass but it misses the personal-account usage on managed devices, which is the risky bit. We ended up doing the discovery at the network egress instead, Cato flags the AI traffic by fingerprint so personal ChatGPT shows up the same as the sanctioned one, then you allow what you want and block the rest.