> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/glean.md).

# Glean

Use Glean data with Cortex XSIAM.

The capabilities and sub-capabilities listed for this connector are available with any active Cortex Cloud Posture Security license.

This connector includes the following capabilities and sub-capabilities (if applicable):

* Agent Security Scanning

### How to configure the Glean connector

To access Glean, Cortex XSIAM requires the following information, which you will specify during the connection process.

* **Instance URL:** The complete backend URL for your Glean organization, typically in the format `https://<tenant-name>-be.glean.com`.
* **Glean API Token:** An API token generated from the Glean Admin Console. Cortex XSIAM uses this token to authenticate to the Glean API.

Perform the following procedures in the order that they appear below.

#### Task 1: Identify Your Instance URL

1. Log in to your Glean web app at <https://app.glean.com>.
2. Navigate to the Glean About page at <https://app.glean.com/admin/about-glean>.
3. Under **Server instance**, copy your organization's complete backend URL (for example, `https://yourcompany-be.glean.com`) and store it in a text file.

#### Task 2: Generate a Glean API Token

1. Log in to your Glean workspace as an administrator.
2. Navigate to the **Admin Console**.
3. Go to the **API tokens** page.
4. Click **Add token** in the top-right corner.
5. Enter a name for the token, configure the expiration date, and select the required scope permissions.
6. Copy the generated token and store it securely.

   > Do not continue to the next step unless you have copied the token. You must provide this value to Cortex XSIAM during the onboarding process.

#### Task 3: Connect Glean to Cortex XSIAM

1. In Cortex XSIAM, navigate to **Settings** → **Data Sources & Integrations**.
2. Click **+ Add new**.
3. In the **Add Data Source** page, search for Glean.
4. Under **Recommended**, hover over the new Glean integration and click **Add Instance** to launch the configuration wizard.
5. Under the **Capabilities** tab, enter a name for your application.
6. Select **Glean Agents** under **Capabilities**. Click **Next**.
7. Under the **Connection** tab, enter the **Instance URL** and **Glean API Token** details.
8. Under the **Configuration** tab, select a **Sync Interval**. Choose a meaningful **Tag** to distinguish between various applications in different environments.
9. A confirmation message shows that Glean is successfully connected. Confirm the **Summary** details and click **Save instance**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/glean.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
