Discover · AI Discovery
Guided rollout· Browser and endpoint rollout is guidedBring shadow AI into view
Halo finds the AI your people use on supported browsers and devices, from chat sites and extensions to developer tools and local runtimes, and records findings with their source and confidence.
At a glance
- browsers supported
- 3
- endpoint operating systems
- 2
- inventory classifications
- 5
Why it matters
AI shows up before anyone approves it
People try new AI sites, browser extensions, and developer tools long before a security review happens. Without a record of what is in use, a policy has nothing to apply to.
- 01
A browser extension or chat site can send work content to a provider nobody on the security team has reviewed.
- 02
Developer laptops can run local model runtimes that produce no browser traffic and no purchase record.
- 03
A spreadsheet of approved tools goes stale as soon as someone installs something new.
Evidence first
Findings that show their work
Findings in the Halo inventory carry their source and confidence. Endpoint evidence adds file paths, hashes, and permissions, so a reviewer can verify a match and decide what to do without opening anyone's documents or prompts.
- Source and confidence recorded with findings
- Paths, hashes, and permissions as endpoint evidence
- Standard collection excludes prompts and documents
- Browser content inspection needs your approval
Capabilities
Find AI across browsers and endpoints
Halo combines browser and endpoint signals so reviewers see AI sites, extensions, applications, runtimes, and configuration in one place.
- AI sites in the browser
- Halo Browser recognizes use of supported AI websites in Chrome and Edge, plus Safari on macOS and reports it to Halo, so the inventory reflects what people actually open.
- AI browser extensions
- On Chrome and Edge, Halo inventories AI-related browser extensions, so reviewers can see which assistants and add-ons sit alongside the sites people use.
- Account posture signals
- Halo Browser records account posture signals on supported AI sites, such as whether a personal or a work account is in use.
- Applications and developer tools
- Halo Endpoint on macOS and Windows surveys AI applications, IDE plug-ins, and developer AI tools, and records paths, hashes, and permissions as evidence.
- Local runtimes and models
- Halo Endpoint also notes local AI runtimes, model artifact locations, startup items, and add-ins that browser monitoring cannot see.
- Source and confidence
- Findings record where they came from and how confident the match is, so reviewers can check the evidence before they classify anything.
How it works
From first signal to a classified inventory
A guided rollout keeps scope, privacy settings, and review ownership clear from the start.
- 1
Plan a guided rollout
Halo's team works with you on enrollment, packaging, and the first groups of browsers and devices, so discovery starts with a scope your team has agreed to.
- 2
Enroll browsers and devices
Halo Browser and Halo Endpoint enroll with an account-scoped token and begin reporting AI sites, extensions, applications, runtimes, and configuration signals.
- 3
Match and enrich
Halo matches signals to its AI catalog and attaches the source and a confidence level, so a finding shows why it was flagged.
- 4
Review and classify
Reviewers work through new findings in the AI inventory and mark each one sanctioned, monitored, blocked, shadow, or unknown.
FAQ
Questions, answered
Halo Browser discovers use of supported AI websites, AI browser extensions on Chrome and Edge, and account posture signals. Halo Endpoint surveys AI applications, IDE plug-ins, developer AI tools, local AI runtimes, model artifact locations, startup items, add-ins, and AI-related configuration files on macOS and Windows.
Standard collection is metadata first. Halo Endpoint records names, paths, hashes, and permissions, and standard collection does not include prompts, responses, documents, clipboard content, or credentials. Browser content inspection requires expanded permissions that your organization approves, and it is off in the standard configuration.
Halo reports what its sensors observe on enrolled, supported surfaces. Coverage depends on which browsers and devices are enrolled and on which sites, applications, and file locations Halo recognizes. The guided rollout includes a review of gaps, so your team knows where discovery does not reach.
Browser and endpoint rollout is guided. Halo's team helps you plan enrollment, package the extension and sensor for managed devices, and start with a scoped group before you expand. Agents you launch through Halo are known to Halo from the start, and their model and tool calls are recorded at the gateways.
Halo Browser supports Chrome and Edge, plus Safari on macOS. Halo Endpoint supports macOS and Windows. Other browsers and operating systems are not supported today, so devices and browsers outside that list do not report to Halo.
Put a halo around the AI your business runs.
See discovery, runtime policy, approvals, and evidence working together on your own use cases.