Vendor comparison
Halo vs OneTrust
OneTrust extends its privacy, risk, and third-party platform to AI. Halo is built for AI from the ground up, with discovery on browsers and endpoints and enforcement at model and tool gateways and in a sandboxed agent runtime, available today.
The short version
- OneTrust’s public materials connect AI governance to its privacy, risk, and third-party programs, with cloud discovery, a policy engine, the AI Guard classification service, and an MCP Gateway announced as a private preview.
- Halo’s model gateway and MCP and tool gateway enforce policy on live agent traffic today, and Halo Browser and Halo Endpoint find the AI people use outside your cloud accounts.
- An AI system registry with owners, risk tiers, and intake is coming soon, so the governance record and the controls that enforce it live in one platform.
How OneTrust describes its AI governance
OneTrust positions AI governance as part of a platform that also covers privacy, consent, technology risk, and third-party management. Public materials describe a record of what AI is running, who owns it, and what data it can reach, with intake, risk scoring, and approval workflows.
Runtime controls use a policy-as-code engine, cloud discovery across AWS, Azure, and GCP, and an AI Guard service that classifies text locally. A September platform announcement describes an AI Control Plane and an MCP Gateway, and labels the MCP Gateway as a private preview. This summary reflects public materials reviewed in October 2026.
How Halo approaches AI governance
Halo discovers the AI in use through Halo Browser (Chrome and Edge, plus Safari on macOS) and Halo Endpoint (macOS and Windows, with Linux coming soon), then classifies each item as sanctioned, monitored, blocked, shadow, or unknown.
Policy applies through model, MCP and tool, and API gateways, the Halo AI Gateway for desktop AI apps and coding agents, and a secure agent runtime that sets execution boundaries. Halo records evidence that supports governance programs, and framework packs that map it to the EU AI Act and NIST AI RMF are coming soon.
Side by side
How Halo and OneTrust compare
| Dimension | Halo | OneTrust |
|---|---|---|
| Starting point | Halo Available nowThe AI in use on browsers, endpoints, gateways, and agent runtimes, governed with policy, evidence, and cost controls. | OneTrust Public materials place AI governance on a platform that also covers privacy, consent, technology risk, and third-party management. |
| Discovery | Halo Guided rolloutHalo Browser and Halo Endpoint discover AI sites, extensions, apps, IDE plug-ins, and local runtimes, with metadata-first collection. On the roadmap Read-only connectors for AWS, Azure, and Google Cloud AI services, SaaS AI, and code repositories. | OneTrust Public materials describe least-privileged discovery across AWS, Azure, and GCP, with relationships mapped across models, agents, datasets, and use cases. |
| Policy engine | Halo Available nowVersioned policy bundles in schema or YAML with audit and enforce modes, simulation with a decision trace, tool-level checks, and decision explanations. Coming soon Immutable policy versions with history, diff, and restore, plus exceptions and reviewer approval before publishing. | OneTrust Public materials describe a policy-as-code engine that turns written policy into machine-readable rules applied to live telemetry. |
| Runtime actions | Halo Available nowAllow, deny, and alert outcomes, human approval gates, and masking in supported gateway paths. | OneTrust Public materials list actions such as blocking or restricting access, redacting through the AI Guard SDK, escalating, and routing to owners. |
| Data handling for classification | Halo Available nowRuntime classifiers cover selected PII, secrets, prompt injection, moderation, and language checks, and standard discovery leaves prompts, responses, documents, and credentials out of collection. | OneTrust AI Guard documentation describes a local service where prompts and responses stay in your environment and only aggregate metrics go to OneTrust. |
| Agents and MCP | Halo Available nowThe MCP and tool gateway applies identity, tool-level policy, approvals, and brokered credentials to each tool call today, and agent identity stays separate from user identity. | OneTrust A September announcement describes an AI Control Plane for agent actions and an MCP Gateway labeled private preview. |
| Governance record | Halo Available nowAn AI inventory with classifications, source, and confidence, plus AI BOM export in CycloneDX, JSON, and CSV. Coming soon An AI system registry with owners, purpose, risk tiers, and intake, linked to the agents and apps Halo already sees. | OneTrust Public materials describe a record of what AI is running, who owns it, and what data it can reach. |
| Evidence and context | Halo Available nowAudit logs and gateway decisions export as CSV and JSON, and dashboards show decision timeseries and cost analytics. Coming soon Tamper-evident decision and audit records with retention and legal hold. | OneTrust Public materials describe a trust graph and an evidence ledger that record which policy applied and what action was taken. |
Why Halo
Why choose Halo over OneTrust
Simple, secure, and efficient AI, governed where it runs.
Discovery outside your cloud accounts
Halo Browser and Halo Endpoint find AI websites, browser extensions, desktop apps, IDE plug-ins, and local runtimes, with paths, hashes, and permissions as evidence.
Enforcement on devices and in browsers
Halo Endpoint can audit or block unapproved AI apps on macOS and Windows, and Halo Browser can audit, warn, or block on supported AI sites.
MCP and tool enforcement today
The MCP and tool gateway applies identity, policy, approvals, and budgets to agent tool calls, and provider and app credentials stay bound at the gateway.
The AI apps your people already use
The Halo AI Gateway connects Claude Desktop, Claude Code, ChatGPT Desktop, and Codex CLI to models and tools that Halo authorizes, meters, and records.
Budgets that act
Account, agent, and per-user budgets can notify owners, pause new operations, or stop active deployments, and cost analytics show spend by agent and model.
A sandbox for every agent
Agents run as non-root workloads with default-deny network egress and signed configuration, and operators can quarantine and release them at any time.
Roadmap
What Halo is building next
Each of these extends the controls Halo runs today.
Capabilities marked coming soon or on the roadmap reflect current plans and may change.
- Coming soon
AI system registry and intake
Register each AI system with an owner, purpose, and risk tier, linked to the agents, apps, and AI Gateway clients Halo already sees.
- Coming soon
Framework packs
EU AI Act and NIST AI RMF controls mapped to Halo checks and runtime policies, with an exportable evidence pack.
- Coming soon
Tamper-evident evidence
Hash-chained decision and audit records with retention, legal hold, and a verifier your auditors can run.
- On the roadmap
Cloud, SaaS, and code discovery
Read-only connectors for cloud AI services, SaaS AI, and code repositories add to the inventory Halo builds from browsers and endpoints.
Buyer checklist
Questions to ask in your evaluation
Bring these to each vendor you evaluate. Here is how Halo answers them.
Does the platform enforce policy on each surface, or only report what it finds?
How Halo answers
Halo enforces on each surface it covers. It blocks unapproved AI apps on devices, audits, warns, or blocks on supported AI sites, and allows, denies, or holds agent calls at the gateway.
How does the platform find AI that nobody registered, including AI outside your cloud accounts?
How Halo answers
Halo Browser and Halo Endpoint find AI sites, extensions, apps, IDE tools, and local runtimes as they appear, with the source and confidence of each finding.
Which capabilities are generally available today, and which are preview or planned?
How Halo answers
Halo labels each capability as available, guided rollout, preview, coming soon, or on the roadmap, on this page and across our site.
Which evidence can reviewers export, and in what formats?
How Halo answers
Audit logs and gateway decisions export as CSV and JSON, and each decision records the policy, the outcome, and the reason.
Where do provider keys and app credentials live, and can an agent ever read them?
How Halo answers
Credentials stay bound at the Halo gateway. Agents receive scoped capabilities and never see raw keys.
Sources and review
Last reviewed October 19, 2026. Information about OneTrust comes from public materials and may change. Product names belong to their owners. Capabilities marked coming soon or on the roadmap reflect current plans and may change. If you spot something out of date, please let us know.
Put a halo around the AI your business runs.
See discovery, runtime policy, approvals, and evidence working together on your own use cases.