Skip to main content
Book a demo

Connect Jamf to Glean

Give Glean governed access to Jamf’s 6 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Glean setup guide

Set up

Add Jamf to Glean in four steps

Admins approve the server once. Everyone in Glean then gets it through the same governed connection.

  1. 1

    Approve Jamf in Runlayer

    Add Jamf from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Glean to Runlayer

    Users add the Runlayer Plugin to Glean by following Runlayer’s setup guide. Glean reaches Jamf’s 6 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Glean setup guide
  3. 3

    Sign in to Jamf

    Sign in the way Jamf requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Jamf from Glean

    Jamf’s approved tools appear in Glean. Every call is checked against policy and recorded.

Tools

6 Jamf tools in Glean

Runlayer policy decides which of these Glean users can call.

  • Execute request

    Executes an API request with a given HAR request object.

  • Get endpoint

    Gets detailed information about a specific API endpoint, including security schemes and servers

  • Get server variables

    Gets the server variables for each server within a specific OpenAPI spec.

  • List endpoints

    Lists all API paths and their HTTP methods with summaries, organized by path.

  • List specs

    Lists all available OpenAPI specs.

  • Search endpoints

    Performs a deep search through paths, operations, and parameters to discover relevant API endpoints.

Control

What Runlayer can see and stop in Glean

Some controls apply to every client at the gateway. Others depend on what Glean exposes to Runlayer.

  • Gateway policy (available)

    Every Jamf call from Glean passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Glean as the client, the tool, and the policy and scanner decisions.

  • OTLP telemetry (available)

    Glean can send supported OpenTelemetry events to Runlayer for observe-only session visibility.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for Glean yet, so control happens at the gateway.

In Glean

  • Runlayer sees Glean activity through OpenTelemetry traces for monitoring only; enforcement happens at the gateway.

Frequently asked questions

Connect more

Find another combination