Skip to main content
Version: 11.5.0

See and Govern the AI Tools Already on Your Workstations

Who this is for: the Admin who brings the AI tools on your organization's workstations under governance, with your IT team deploying the desktop client.

Purpose​

This playbook gives the running order for bringing the AI tools already on your workstations under HYPR AgentPass™. First you see them, then you route them through the gateway, then you make sure they cannot go around it.

Each task is a summary. The detail, with screenshots, field values and caveats, is on the page the step links to.

When you finish:

  • Every workstation AI tool is visible, with its user and desktop.
  • Its traffic flows through the gateway, where policy applies.
  • Direct provider traffic from that tool is blocked.

Architecture​

Endpoint Guard on each workstation reports the tools it sees, then sends their traffic to the gateway. The gateway records and governs it. For the diagram and the request path, see Architecture: The Request Path.

Prerequisites​

  • Role: Admin. Desktops changes need Settings: Edit, and connectors need Connectors: Edit, which only Admin holds. Operator and Auditor can follow along read-only.
  • Endpoint Guard, deployable to your workstations
  • An account with the AI provider your tools use, Anthropic or OpenAI

For the full list, see Prerequisites.

Procedure​

Complete these tasks in order.

Enroll Your Workstations​

Open Desktops, and follow the Get started checklist. Create an enrollment token on Desktops → Installation, and deploy the desktop client with it. Watch desktops is on by default. One token per rollout keeps each deployment separate. Enrolled desktops are counted under their token, and start reporting.

See Getting Started with Desktops and Enrolling Desktops.

Read What Is Running​

Open Activity → Desktop activity. The By tool tab lists the AI tools your desktops report, and Via gateway lists tools that reach the gateway with no enrolled desktop behind them. Each is attributed to a person and desktop where possible. Note the tools, and the providers they call. The rest of this playbook works from that list.

See Desktop Activity.

Review Browser AI Tools (Optional)​

On Desktops → SaaS based AI, set rules for the AI apps your workforce reaches through the browser. Allow what your organization sanctions, Block… what it does not, and choose Don’t watch for what was never shadow AI. Their use is on Desktop activity. This is a separate signal, so the tasks that follow do not depend on it.

See SaaS Based AI.

Add the AI Provider Connector in Observe Mode​

Add a connector for each provider you noted, and set its Onboarding Mode to Observe only. The gateway records traffic from unmanaged clients without blocking or onboarding anything, so you can watch before you change behavior.

See Anthropic or OpenAI, and Onboarding Mode.

Configure and Route the Tools​

Open Desktops → Desktop configuration → Configuration, and turn on Configure agents from AgentPass. Turn on each tool to configure, keep Route model traffic through AgentPass ticked, and pick your connector. Enrolled desktops pick up the configuration on their next check.

See Agent Configuration and Routing and Observation.

Block the Bypass​

Tick Block direct traffic for each routed tool, and under For every agent, decide what a desktop does when AgentPass can't be reached. From this point, the tool's direct provider traffic is blocked on the device.

See Egress Enforcement.

Require Approval for New Agents​

Change the connector's Onboarding Mode from Observe only to Require Approval. A tool's next connection is held until its supervisor approves it, and the person at the workstation sees the onboarding prompt.

See Onboarding Mode. For what the person sees, see Onboarding Your Agent.

Validate​

Check the following:

  • On Activity → Desktop activity, the By desktop tab lists your desktops. Each desktop's Managed configuration shows routing and blocking as Applied.
  • On Activity → Request log, the tool's requests are attributed to the workstation user.
  • A direct call from the tool to the provider fails on the device.

See Managed Desktops.

Logs and Audit Trail​

Every governed request is in the Request Log. Desktop reports are on Activity → Desktop activity. What the gateway keeps of each request, and for how long, is set under Settings → Data management.

See Request Log and Data Management.