> 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-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/celonis.md).

# Celonis

Use Celonis data with Cortex Cloud.

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

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

* SaaS Posture Configuration Monitoring: Detect, monitor and alert on settings of your SaaS application.
  * saas-posture-config-remediation: Help remediate the misconfigured security settings of your SaaS application.

### How to configure the Celonis connector

Cortex Cloud supports Celonis Platform teams with Administrator privileges. The connection will fail for any other role.

Celonis uses a server-to-server OAuth Client. No redirect URI is required and there is no browser consent screen. Cortex Cloud exchanges the Client ID and Client Secret for short-lived access tokens (valid for 15 minutes) directly and refreshes them automatically.

> **Important:** The Team Name and Realm cannot be changed after the instance is created. If you enter the wrong values, you must delete the instance and create a new one.

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

* **Team Name:** The subdomain segment of your Celonis URL that identifies your team. For example, in `https://acme-corp.eu-1.celonis.cloud`, the Team Name is `acme-corp`.
* **Realm:** The cluster segment of your Celonis URL that identifies your data center. For example, in `https://acme-corp.eu-1.celonis.cloud`, the Realm is `eu-1`. Common values include `eu-1`, `us-1`, `us-2`, `ap-1`, and `ca-1`.
* **Client ID:** The unique identifier for your Celonis OAuth client application, generated in Admin & Settings → Applications.
* **Client Secret:** The secret key for your Celonis OAuth client application. Cortex Cloud uses the Client ID and Client Secret to obtain access tokens from the Celonis authorization server.

> **Important:** The Client Secret is displayed only once, at the time the OAuth client is created. If you navigate away without copying it, you must regenerate the secret and update the Cortex Cloud instance.

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

#### Task 1: Identify Your Team Name and Realm

1. Log in to your Celonis Platform team and look at your browser's address bar.
2. Your Celonis URL follows this pattern: `https://[team_name].[realm].celonis.cloud`

   For example, if your URL is `https://acme-corp.eu-1.celonis.cloud`:

   | Field     | Value       |
   | --------- | ----------- |
   | Team Name | `acme-corp` |
   | Realm     | `eu-1`      |
3. Copy both values and store them in a text file.

   > Do not continue to the next step unless you have recorded both values. You must provide them to Cortex Cloud during the onboarding process.

#### Task 2: Create an OAuth Client in Celonis

1. Log in to your Celonis Platform team as an Administrator.
2. Navigate to **Admin & Settings** → **Applications** from the left sidebar.
3. Click **Add New Application** (top-right) and select **OAuth Client**.
4. Complete the client configuration fields:

   | Field                 | Value                                                                  |
   | --------------------- | ---------------------------------------------------------------------- |
   | Name                  | `Cortex_SSPM_Auditor` (or any descriptive name)                        |
   | Description           | `Read-only OAuth 2.0 client for Cortex SSPM security posture scanning` |
   | Grant Type            | `Client Credentials`                                                   |
   | Authentication Method | `Client secret post`                                                   |
5. Click **Define Scopes** and select all four required scopes:

   | Scope                            | Purpose                     |
   | -------------------------------- | --------------------------- |
   | `audit.log:read`                 | Administrative Audit Trail  |
   | `authorization.permissions:read` | Permissions Export API      |
   | `team.user-group-info:read`      | Members and User Groups API |
   | `team.login-history:read`        | Login History API           |
6. Click **Create**. Immediately copy the **Client ID** and **Client Secret** and store them securely.

   > The Client Secret is shown only once. You cannot retrieve it after you navigate away from this page. You must provide both values to Cortex XSIAM during the onboarding process.

#### Task 3: Assign Admin Permissions to the OAuth Client

> This step is mandatory. Without platform permissions, all API calls return `403 Forbidden` even if the scopes are correctly configured. Celonis uses a two-layer model: scopes define what the token can request; platform permissions define what the application is allowed to access.

1. Open the OAuth client you created in Task 2.
2. In the **Add new** section, click **Admin & Settings**.
3. Toggle the following four services to **Use API**:

   | Service             | Permission |
   | ------------------- | ---------- |
   | Audit logs          | Use API    |
   | Service permissions | Use API    |
   | Users               | Use API    |
   | Login history       | Use API    |
4. Click **Save**.

#### Task 4: Connect Celonis to Cortex Cloud

1. In Cortex Cloud, navigate to **Settings** → **Data Sources & Integrations**.
2. Click **+ Add new**.
3. In the **Add Data Source** page, search for Celonis.
4. Under **Recommended**, hover over the new Celonis integration and click **Add Instance** to launch the configuration wizard.
5. Under the **Capabilities** tab, enter a name for your application.
6. Select **Security Posture** under **Default Capabilities**. Click **Next**.
7. Under the **Connection** tab, enter the **Team Name**, **Realm**, **Client ID**, and **Client Secret** 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 Celonis 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-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/celonis.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.
