Partnerships
Onyx Security and Glean Partner to Secure Enterprise AI Agents

Key PointsOnyx and Glean integrate discovery and runtime enforcement so agents are governed…
View more
- Onyx and Glean integrate discovery and runtime enforcement so agents are governed beyond simple data retrieval permissions.
- Glean's hooks give Onyx checkpoints to evaluate prompts and proposed tool executions before actions reach business systems.
- Agent governance must stay continuous because new connectors and capabilities can change an agent's risk profile after approval.
Onyx Security and Glean have announced a partnership to help enterprises secure and govern AI agents as they gain access to more company information and business tools. The integration connects Glean’s enterprise AI platform with Onyx’s secure AI control plane, bringing agent discovery, risk assessment, policy enforcement, and runtime protection into a shared governance approach.
The partnership addresses a practical challenge in enterprise AI: an agent may have permission to retrieve information while still needing additional controls over what it does with that information. A workflow that starts with gathering context can progress to sending a message, updating a record, or invoking another tool, making oversight of the proposed action increasingly important.
“As AI agents take on more complex work across the enterprise, they need access to the right context, with the right controls in place,” said Zubin Irani, VP of Partnerships at Glean.
Connecting enterprise context with security controls
Glean provides the platform for building, deploying, and operating enterprise agents. Its Enterprise Context layer connects business applications and indexes company information, while its Enterprise Graph maps relationships among people, content, and activity. Glean says its connector ecosystem spans more than 275 applications and data sources, including documents, tickets, chat, and code.
That context helps an agent connect information spread across business systems, such as a customer account, its support history, and the people responsible for the relationship. Permission-aware retrieval determines which information the user can access as the agent works.
Glean also brings its own security foundation. Glean Protect describes controls covering user and agent identity, source-system permissions, sensitive content, runtime threats, and action alignment, along with audit events that can feed security monitoring systems. The Onyx integration adds a separate enterprise-wide governance and risk layer around Glean agents and other supported AI environments.
How the integration works
According to Onyx’s technical description of the partnership, discovery uses the Glean API to read agent inventory and security posture. That gives security teams a way to review agents and their access without treating the discovery connection itself as a mechanism for executing agent actions.
Runtime enforcement uses a different path: Glean’s hooks provide supported checkpoints where Onyx can evaluate conversation content and proposed tool executions against enterprise policies. The controls assess prompts, responses, and agent actions, with the aim of blocking unsafe requests and steering unintended behavior back toward the authorized task.
For example, access to internal account information may be appropriate for preparing a customer meeting, while sending confidential pricing information outside the company may violate policy. An action checkpoint gives a security control an opportunity to assess the proposed disclosure before the tool executes it.
The distinction between retrieving data and authorizing its use is central to the partnership. It also connects to the broader challenge of securing agents against instructions embedded in external content, where a document or tool response can attempt to redirect an otherwise legitimate workflow.
Governance that follows agents as they change
The integration is intended to make agent governance an ongoing process. Security teams can discover Glean agents, understand their access and capabilities, establish ownership and business purpose, and assign risk classifications. Those records can then inform enterprise AI governance and compliance policies.
Ongoing assessment covers changes to permissions, tools, and data access. That matters because an agent approved for one workflow may later acquire a new connector or capability, changing its risk profile even if its name and owner remain the same. Centralized audit evidence provides a record that teams can use to investigate activity and review how policies were applied.
“As agents gain greater access and autonomy, security teams need visibility and control over what they can do,” said Gil Elbaz, Co-founder and Chief AI Officer at Onyx Security. “By combining Glean’s enterprise context with Onyx’s security control plane, customers can govern agent activity consistently and confidently across their AI environment.”
A broader control plane for enterprise AI
Onyx positions its secure AI control plane across SaaS applications, cloud services, endpoints, and custom code. Its platform combines agent observability, security posture management, governance, and runtime safeguards. The company describes session replay and audit trails for investigations, natural-language policy controls, and integrations with security information and event management and security orchestration systems.
Onyx also offers gateway capabilities for AI and Model Context Protocol traffic, alongside a supervisory Guardian Agent designed to identify risks and remediate issues across its platform. These broader capabilities explain the company’s role in the partnership: bringing Glean activity into a control framework that security teams can use across multiple AI systems.
The integration is listed in Glean’s connector catalog as beta. Its listed scope includes agent inventory, posture management, runtime visibility, and controls on prompts, model responses, and tool execution. Runtime enforcement depends on supported checkpoints, making the coverage of a particular workflow an important part of deployment planning.
For enterprises expanding agent use across departments, the partnership offers a way to connect useful business context with accountable operation. Its practical value will depend on keeping the agent inventory current, carrying ownership and risk decisions into runtime policies, and applying those policies at the points where agents can affect business systems.












