Acceptance criteria
Show visibility in Chrome, Edge, Safari and Firefox where supported, including prompt context and account plan.
Why it matters
The browser is where most employee AI use happens, so it is the first place visibility has to work.
How to verify
Pilot users' AI use in each supported browser appears with prompt context and account plan.
OWASP adoption context
The listed contexts focus on browser access to personal-account AI and vendor assistants; the supported browser and capture path still determine visibility.
Framework mappings
Browser prompt and account-plan telemetry makes personnel use and AI runtime activity visible for operational monitoring. Coverage is limited to supported browsers, and visibility alone does not establish adverse-event analysis.
Point-of-use browser telemetry provides evidence for anomaly monitoring; the acceptance test does not require anomaly analysis or incident evaluation.
Browser-use observations, including the prompt and account fields actually captured, provide application-activity signals for security monitoring. Demonstrate browser coverage, telemetry completeness and delivery to security analysis; visibility alone does not detect anomalies or prevent disclosure.