From 1faf27a4a07cd6ab0277418a7909474f31afa79a Mon Sep 17 00:00:00 2001 From: Mindy Moreland Date: Thu, 15 Jan 2026 10:20:58 -0800 Subject: [PATCH 1/5] reformatting experiment --- baton/palo-alto-cortex.md | 193 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 193 insertions(+) create mode 100644 baton/palo-alto-cortex.md diff --git a/baton/palo-alto-cortex.md b/baton/palo-alto-cortex.md new file mode 100644 index 0000000..3ede220 --- /dev/null +++ b/baton/palo-alto-cortex.md @@ -0,0 +1,193 @@ +--- +title: Set up a Palo Alto Networks Cortex XDR connector +seo_title: Set up a Palo Alto Networks Cortex XDR connector - ConductorOne docs +seo_description: Integrate your Cortex XDR instance with ConductorOne to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +intro: ConductorOne provides identity governance and just-in-time provisioning for Cortex XDR. Integrate your Cortex XDR instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests. +--- + +## Capabilities + +| Resource | Sync | Provision | +| ------------ | ---- | --------- | +| Accounts | ✅ | | +| Roles | ✅ | ✅* | +| Groups | ✅ | | + +*Due to a limitation of the underlying API, the Cortex XDR **Account Admin** role cannot be granted or revoked by this connector. + +## Gather Cortex XDR credentials + +Each setup method requires you to pass in credentials generated in Cortex XDR. Gather these credentials before you move on. + +{{% hint style="warning" %}} +A an **Instance Administrator** in Cortex XDR must perform this task. +{{% /hint %}} + +### Generate an API key + +1. In Cortex XDR, navigate to **Settings > Configurations > Integrations > API Keys**. + +1. Click **+ New Key**. + +1. Choose the type of API Key you want to generate based on your desired security level: Advanced or Standard. + +1. **Optional.** If desired, set an expiration date and time for the API key and add a comment describing its use. + +1. Give the key the **Instance Administrator** role. + +1. Click **Generate**, then carefully copy and save the new API key. + +### Look up the API key ID + +1. In the API keys table, locate the key you just created. + +1. Find and copy the key's **ID**. + +**That's it!** Next, move on to the connector configuration instructions. + +## Configure the Cortex XDR connector + +{{% hint style="warning" %}} +To complete this task, you'll need: + +- The **Connector Administrator** or **Super Administrator** role in ConductorOne +- Access to the set of Cortex XDR credentials generated by following the instructions above +{{% /hint %}} + +{{< tab-group >}} +{{< tab label="Cloud-hosted" >}} +{{< markdown >}} +**Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.** + +1. In ConductorOne, navigate to **Admin** > **Connectors** and click **Add connector**. + +1. Search for **Cortex XDR** and click **Add**. + +1. Choose how to set up the new Cortex XDR connector: + + * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with ConductorOne) + + * Add the connector to a managed app (select from the list of existing managed apps) + + * Create a new managed app + +1. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed. + + If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process. + +1. Click **Next**. + +1. Find the **Settings** area of the page and click **Edit**. + +1. Enter the Cortex XDR credentials into the relevant fields. + +1. Click **Save**. + +1. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. + +**That's it!** Your Cortex XDR connector is now pulling access data into ConductorOne. +{{< /markdown >}} +{{< /tab >}} + +{{< tab label="Self-hosted" >}} +{{< markdown >}} +**Follow these instructions to use the [Cortex XDR](https://github.com/ConductorOne/baton-pandadoc) connector, hosted and run in your own environment.** + +When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests. + +### Step 1: Configure the Cortex XDR connector + +1. In ConductorOne, navigate to **Connectors** > **Add connector**. + +2. Search for **Baton** and click **Add**. + +3. Choose how to set up the new Cortex XDR connector: + + * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with ConductorOne) + + * Add the connector to a managed app (select from the list of existing managed apps) + + * Create a new managed app + +1. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed. + + If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process. + +1. Click **Next**. + +1. In the **Settings** area of the page, click **Edit**. + +1. Click **Rotate** to generate a new Client ID and Secret. + + Carefully copy and save these credentials. We'll use them in Step 2. + +### Step 2: Create Kubernetes configuration files + +Create two Kubernetes manifest files for your Cortex XDR connector deployment: + +#### Secrets configuration + +```yaml +# baton-palo-alto-cortex-secrets.yaml +apiVersion: v1 +kind: Secret +metadata: + name: baton-palo-alto-cortex-secrets +type: Opaque +stringData: + # ConductorOne credentials + BATON_CLIENT_ID: + BATON_CLIENT_SECRET: + + # Cortex XDR credentials + BATON_CORTEX_API_KEY: + BATON_CORTEX_API_KEY_ID: + BATON_CORTEX_BASE_URL: + + # Optional: Include if you want ConductorOne to provision access using this connector + BATON_PROVISIONING: true +``` + +See the connector's README or run `--help` to see all available configuration flags and environment variables. + +#### Deployment configuration + +```yaml +# baton-palo-alto-cortex.yaml +apiVersion: apps/v1 +kind: Deployment +metadata: + name: baton-palo-alto-cortex + labels: + app: baton-palo-alto-cortex +spec: + selector: + matchLabels: + app: baton-palo-alto-cortex + template: + metadata: + labels: + app: baton-palo-alto-cortex + baton: true + baton-app: palo-alto-cortex + spec: + containers: + - name: baton-palo-alto-cortex + image: ghcr.io/conductorone/baton-palo-alto-cortex:latest + imagePullPolicy: IfNotPresent + envFrom: + - secretRef: + name: baton-palo-alto-cortex-secrets +``` + +### Step 3: Deploy the connector + +1. Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files. + +1. Check that the connector data uploaded correctly. In ConductorOne, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Cortex XDR connector to. Cortex XDR data should be found on the **Entitlements** and **Accounts** tabs. + +**That's it!** Your Cortex XDR connector is now pulling access data into ConductorOne. +{{< /markdown >}} +{{< /tab >}} +{{< /tab-group >}} + From d7ef2970a673bf610a09df9b2839baef5a2bc7f2 Mon Sep 17 00:00:00 2001 From: Mindy Moreland Date: Thu, 15 Jan 2026 11:31:29 -0800 Subject: [PATCH 2/5] reformatted doc --- baton/palo-alto-cortex.mdx | 238 +++++++++++++++++++++++++++++++++++++ 1 file changed, 238 insertions(+) create mode 100644 baton/palo-alto-cortex.mdx diff --git a/baton/palo-alto-cortex.mdx b/baton/palo-alto-cortex.mdx new file mode 100644 index 0000000..9b369f0 --- /dev/null +++ b/baton/palo-alto-cortex.mdx @@ -0,0 +1,238 @@ +--- +title: Set up a Palo Alto Networks Cortex XDR connector +og:title: Set up a Palo Alto Networks Cortex XDR connector - ConductorOne docs +og:description: Integrate your Cortex XDR instance with ConductorOne to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: ConductorOne provides identity governance and just-in-time provisioning for Cortex XDR. Integrate your Cortex XDR instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests. +sidebarTitle: "Palo Alto Networks Cortex XDR" +--- + +## Capabilities + +| Resource | Sync | Provision | +| :--- | :--- | :--- | +| Accounts | | | +| Roles | | | +| Groups | | | + + +*Due to a limitation of the underlying API, the Cortex XDR **Account Admin** role cannot be granted or revoked by this connector. + + +## Gather Cortex XDR credentials + +Each setup method requires you to pass in credentials generated in Cortex XDR. Gather these credentials before you move on. + + +A an **Instance Administrator** in Cortex XDR must perform this task. + + +### Generate an API key + + + +In Cortex XDR, navigate to **Settings > Configurations > Integrations > API Keys**. + + +Click **+ New Key**. + + +Choose the type of API Key you want to generate based on your desired security level: Advanced or Standard. + + +**Optional.** If desired, set an expiration date and time for the API key and add a comment describing its use. + + +Give the key the **Instance Administrator** role. + + +Click **Generate**, then carefully copy and save the new API key. + + + +### Look up the API key ID + + + +In the API keys table, locate the key you just created. + + +Find and copy the key's **ID**. + + + +**That's it!** Next, move on to the connector configuration instructions. + +## Configure the Cortex XDR connector + + +To complete this task, you'll need: + +- The **Connector Administrator** or **Super Administrator** role in ConductorOne +- Access to the set of Cortex XDR credentials generated by following the instructions above + + + + + +**Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.** + + + +In ConductorOne, navigate to **Admin** > **Connectors** and click **Add connector**. + + +Search for **Cortex XDR** and click **Add**. + + +Choose how to set up the new Cortex XDR connector: + + * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with ConductorOne) + + * Add the connector to a managed app (select from the list of existing managed apps) + + * Create a new managed app + + +Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed. + + If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process. + + +Click **Next**. + + +Find the **Settings** area of the page and click **Edit**. + + +Enter the Cortex XDR credentials into the relevant fields. + + +Click **Save**. + + +The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. + + +**That's it!** Your Cortex XDR connector is now pulling access data into ConductorOne. + + + + +**Follow these instructions to use the [Cortex XDR](https://github.com/ConductorOne/baton-palo-alto-cortex) connector, hosted and run in your own environment.** + +When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests. + +### Step 1: Configure the Cortex XDR connector + + + +In ConductorOne, navigate to **Connectors** > **Add connector**. + + +Search for **Baton** and click **Add**. + + +Choose how to set up the new Cortex XDR connector: + + * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with ConductorOne) + + * Add the connector to a managed app (select from the list of existing managed apps) + + * Create a new managed app + + +Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed. + + If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process. + + +Click **Next**. + + +In the **Settings** area of the page, click **Edit**. + + +Click **Rotate** to generate a new Client ID and Secret. + + Carefully copy and save these credentials. We'll use them in Step 2. + + + +### Step 2: Create Kubernetes configuration files + +Create two Kubernetes manifest files for your Cortex XDR connector deployment: + +#### Secrets configuration + +```yaml expandable +# baton-palo-alto-cortex-secrets.yaml +apiVersion: v1 +kind: Secret +metadata: + name: baton-palo-alto-cortex-secrets +type: Opaque +stringData: + # ConductorOne credentials + BATON_CLIENT_ID: + BATON_CLIENT_SECRET: + + # Cortex XDR credentials + BATON_CORTEX_API_KEY: + BATON_CORTEX_API_KEY_ID: + BATON_CORTEX_BASE_URL: + + # Optional: Include if you want ConductorOne to provision access using this connector + BATON_PROVISIONING: true +``` + + +See the connector's README or run `--help` to see all available configuration flags and environment variables. + + +#### Deployment configuration + +```yaml expandable +# baton-palo-alto-cortex.yaml +apiVersion: apps/v1 +kind: Deployment +metadata: + name: baton-palo-alto-cortex + labels: + app: baton-palo-alto-cortex +spec: + selector: + matchLabels: + app: baton-palo-alto-cortex + template: + metadata: + labels: + app: baton-palo-alto-cortex + baton: true + baton-app: palo-alto-cortex + spec: + containers: + - name: baton-palo-alto-cortex + image: ghcr.io/conductorone/baton-palo-alto-cortex:latest + imagePullPolicy: IfNotPresent + env: + - name: BATON_HOST_ID + value: baton-palo-alto-cortex + envFrom: + - secretRef: + name: baton-palo-alto-cortex-secrets +``` + +### Step 3: Deploy the connector + + + +Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files. + + +Check that the connector data uploaded correctly. In ConductorOne, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Cortex XDR connector to. Cortex XDR data should be found on the **Entitlements** and **Accounts** tabs. + + + +**That's it!** Your Cortex XDR connector is now pulling access data into ConductorOne. + + From 386056e779a39cad15c41867464dcb85470e7aef Mon Sep 17 00:00:00 2001 From: Mindy Moreland Date: Thu, 15 Jan 2026 11:31:44 -0800 Subject: [PATCH 3/5] index entries --- baton/capabilities.mdx | 3 ++- baton/intro.mdx | 7 +++++-- docs.json | 3 ++- 3 files changed, 9 insertions(+), 4 deletions(-) diff --git a/baton/capabilities.mdx b/baton/capabilities.mdx index 3808853..9c76324 100644 --- a/baton/capabilities.mdx +++ b/baton/capabilities.mdx @@ -165,6 +165,8 @@ og:description: "A quick reference for how each connector can be set up and what | [Oracle Identity Cloud Service](/baton/oracle-idcs) | | | | | [Outreach](/baton/outreach) | | | | | [PagerDuty](/baton/pagerduty) | | | | +| [Palo Alto Networks Cortex XDR](/docs/baton/palo-alto-cortex) | | | | +| [Palo Alto Networks Cortex XSOAR](/docs/baton/xsoar) | | | | | [PandaDoc](/baton/panda-doc) | | | | | [Panther](/baton/panther) | | | | | [Paylocity](/baton/paylocity) | | | | @@ -229,7 +231,6 @@ og:description: "A quick reference for how each connector can be set up and what | [Workday Account](/baton/workday-wql) | | | | | [Workday](/baton/workday) | | | | | [Xero](/baton/xero) | | | | -| [XSOAR](/baton/xsoar) | | | | | [YouTrack](/baton/youtrack) | | | | | [Zendesk v1](/baton/v1/zendesk) | | | | | [Zendesk v2](/baton/zendesk-v2) | | | | diff --git a/baton/intro.mdx b/baton/intro.mdx index c8e6793..1d140f7 100644 --- a/baton/intro.mdx +++ b/baton/intro.mdx @@ -199,6 +199,8 @@ You can build it yourself, or we can build it for you. Whether it’s API-based, - [Oracle Utilities Work and Asset Cloud Service](/baton/oracle-idcs) - [Outreach](/baton/outreach) - [PagerDuty](/baton/pagerduty) + - [Palo Alto Networks Cortex XDR](/docs/baton/palo-alto-cortex) + - [Palo Alto Networks Cortex XSOAR](/docs/baton/xsoar) - [PandaDoc](/baton/panda-doc) - [Panther](/baton/panther) - [Paylocity](/baton/paylocity) @@ -257,7 +259,6 @@ You can build it yourself, or we can build it for you. Whether it’s API-based, - [Workday](/baton/workday) - [Workday Account](/baton/workday-wql) - [Xero](/baton/xero) - - [XSOAR](/baton/xsoar) - [YouTrack](/baton/youtrack) - [Zendesk](/baton/zendesk-v2) - [ZipHQ](/baton/ziphq) @@ -270,6 +271,7 @@ You can build it yourself, or we can build it for you. Whether it’s API-based, +- [Palo Alto Networks Cortex XDR](/docs/baton/palo-alto-cortex) - [OpenAI](/baton/openai) - [Valimail](/baton/valimail) - [ZipHQ](/baton/ziphq) @@ -492,11 +494,12 @@ You can build it yourself, or we can build it for you. Whether it’s API-based, - [CloudAMQP](/baton/cloudamqp) - [Cloudflare](/baton/cloudflare-v2) - [Cloudflare Zero Trust](/baton/cloudflare-zero-trust) -- [Cortex XSOAR](/baton/xsoar) - [CrowdStrike](/baton/crowdstrike) - [DigiCert CertCentral](/baton/digicert-certcentral) - [Fastly](/baton/fastly) - [Jamf](/baton/jamf) +- [Palo Alto Networks Cortex XDR](/docs/baton/palo-alto-cortex) +- [Palo Alto Networks Cortex XSOAR](/docs/baton/xsoar) - [Panther](/baton/panther) - [PrivX](/baton/privx) - [Rapid7](/baton/rapid7) diff --git a/docs.json b/docs.json index 3933f21..8a91a13 100644 --- a/docs.json +++ b/docs.json @@ -370,6 +370,8 @@ "baton/oracle-idcs", "baton/outreach", "baton/pagerduty", + "baton/palo-alto-cortex", + "baton/xsoar", "baton/panda-doc", "baton/panther", "baton/paylocity", @@ -427,7 +429,6 @@ "baton/workday", "baton/workday-wql", "baton/xero", - "baton/xsoar", "baton/youtrack", "baton/zendesk-v2", "baton/ziphq", From 805a53ff62175161ca20704c00c5869cf1851262 Mon Sep 17 00:00:00 2001 From: Mindy Moreland Date: Thu, 15 Jan 2026 11:31:58 -0800 Subject: [PATCH 4/5] cleanup and standardization --- baton/_release-notes.mdx | 2 +- baton/xsoar.mdx | 7 ++++--- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/baton/_release-notes.mdx b/baton/_release-notes.mdx index 8fd2587..f51af5c 100644 --- a/baton/_release-notes.mdx +++ b/baton/_release-notes.mdx @@ -3,7 +3,7 @@ title: "Connector release notes" sidebarTitle: "Release notes" description: "Here you'll find the latest on new connectors, connector updates, and other connector news from C1." --- -{/* OpenAI */} +{/* Cortex XDR */} {/* No connector release notes for week of January 9, 2026 */} diff --git a/baton/xsoar.mdx b/baton/xsoar.mdx index 4b2a68c..4808410 100644 --- a/baton/xsoar.mdx +++ b/baton/xsoar.mdx @@ -1,9 +1,9 @@ --- -title: Set up a Cortex XSOAR connector -og:title: Set up a Cortex XSOAR connector - ConductorOne docs +title: Set up a Palo Alto Networks Cortex XSOAR connector +og:title: Set up a Palo Alto Networks Cortex XSOAR connector - ConductorOne docs og:description: Integrate your XSOAR instance with ConductorOne to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. description: ConductorOne provides identity governance and just-in-time provisioning for Cortex XSOAR. Integrate your XSOAR instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests. -sidebarTitle: "XSOAR" +sidebarTitle: "Palo Alto Networks Cortex XSOAR" --- ## Capabilities @@ -46,6 +46,7 @@ Click **Save** to generate the new API key. Carefully copy and save the API key. + ## Find your API URL From 4d5be29764837fbaf329458ded32b979554dad8b Mon Sep 17 00:00:00 2001 From: Mindy Moreland Date: Thu, 15 Jan 2026 12:14:37 -0800 Subject: [PATCH 5/5] remove markdown file --- baton/palo-alto-cortex.md | 193 -------------------------------------- 1 file changed, 193 deletions(-) delete mode 100644 baton/palo-alto-cortex.md diff --git a/baton/palo-alto-cortex.md b/baton/palo-alto-cortex.md deleted file mode 100644 index 3ede220..0000000 --- a/baton/palo-alto-cortex.md +++ /dev/null @@ -1,193 +0,0 @@ ---- -title: Set up a Palo Alto Networks Cortex XDR connector -seo_title: Set up a Palo Alto Networks Cortex XDR connector - ConductorOne docs -seo_description: Integrate your Cortex XDR instance with ConductorOne to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. -intro: ConductorOne provides identity governance and just-in-time provisioning for Cortex XDR. Integrate your Cortex XDR instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests. ---- - -## Capabilities - -| Resource | Sync | Provision | -| ------------ | ---- | --------- | -| Accounts | ✅ | | -| Roles | ✅ | ✅* | -| Groups | ✅ | | - -*Due to a limitation of the underlying API, the Cortex XDR **Account Admin** role cannot be granted or revoked by this connector. - -## Gather Cortex XDR credentials - -Each setup method requires you to pass in credentials generated in Cortex XDR. Gather these credentials before you move on. - -{{% hint style="warning" %}} -A an **Instance Administrator** in Cortex XDR must perform this task. -{{% /hint %}} - -### Generate an API key - -1. In Cortex XDR, navigate to **Settings > Configurations > Integrations > API Keys**. - -1. Click **+ New Key**. - -1. Choose the type of API Key you want to generate based on your desired security level: Advanced or Standard. - -1. **Optional.** If desired, set an expiration date and time for the API key and add a comment describing its use. - -1. Give the key the **Instance Administrator** role. - -1. Click **Generate**, then carefully copy and save the new API key. - -### Look up the API key ID - -1. In the API keys table, locate the key you just created. - -1. Find and copy the key's **ID**. - -**That's it!** Next, move on to the connector configuration instructions. - -## Configure the Cortex XDR connector - -{{% hint style="warning" %}} -To complete this task, you'll need: - -- The **Connector Administrator** or **Super Administrator** role in ConductorOne -- Access to the set of Cortex XDR credentials generated by following the instructions above -{{% /hint %}} - -{{< tab-group >}} -{{< tab label="Cloud-hosted" >}} -{{< markdown >}} -**Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.** - -1. In ConductorOne, navigate to **Admin** > **Connectors** and click **Add connector**. - -1. Search for **Cortex XDR** and click **Add**. - -1. Choose how to set up the new Cortex XDR connector: - - * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with ConductorOne) - - * Add the connector to a managed app (select from the list of existing managed apps) - - * Create a new managed app - -1. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed. - - If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process. - -1. Click **Next**. - -1. Find the **Settings** area of the page and click **Edit**. - -1. Enter the Cortex XDR credentials into the relevant fields. - -1. Click **Save**. - -1. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. - -**That's it!** Your Cortex XDR connector is now pulling access data into ConductorOne. -{{< /markdown >}} -{{< /tab >}} - -{{< tab label="Self-hosted" >}} -{{< markdown >}} -**Follow these instructions to use the [Cortex XDR](https://github.com/ConductorOne/baton-pandadoc) connector, hosted and run in your own environment.** - -When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests. - -### Step 1: Configure the Cortex XDR connector - -1. In ConductorOne, navigate to **Connectors** > **Add connector**. - -2. Search for **Baton** and click **Add**. - -3. Choose how to set up the new Cortex XDR connector: - - * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with ConductorOne) - - * Add the connector to a managed app (select from the list of existing managed apps) - - * Create a new managed app - -1. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed. - - If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process. - -1. Click **Next**. - -1. In the **Settings** area of the page, click **Edit**. - -1. Click **Rotate** to generate a new Client ID and Secret. - - Carefully copy and save these credentials. We'll use them in Step 2. - -### Step 2: Create Kubernetes configuration files - -Create two Kubernetes manifest files for your Cortex XDR connector deployment: - -#### Secrets configuration - -```yaml -# baton-palo-alto-cortex-secrets.yaml -apiVersion: v1 -kind: Secret -metadata: - name: baton-palo-alto-cortex-secrets -type: Opaque -stringData: - # ConductorOne credentials - BATON_CLIENT_ID: - BATON_CLIENT_SECRET: - - # Cortex XDR credentials - BATON_CORTEX_API_KEY: - BATON_CORTEX_API_KEY_ID: - BATON_CORTEX_BASE_URL: - - # Optional: Include if you want ConductorOne to provision access using this connector - BATON_PROVISIONING: true -``` - -See the connector's README or run `--help` to see all available configuration flags and environment variables. - -#### Deployment configuration - -```yaml -# baton-palo-alto-cortex.yaml -apiVersion: apps/v1 -kind: Deployment -metadata: - name: baton-palo-alto-cortex - labels: - app: baton-palo-alto-cortex -spec: - selector: - matchLabels: - app: baton-palo-alto-cortex - template: - metadata: - labels: - app: baton-palo-alto-cortex - baton: true - baton-app: palo-alto-cortex - spec: - containers: - - name: baton-palo-alto-cortex - image: ghcr.io/conductorone/baton-palo-alto-cortex:latest - imagePullPolicy: IfNotPresent - envFrom: - - secretRef: - name: baton-palo-alto-cortex-secrets -``` - -### Step 3: Deploy the connector - -1. Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files. - -1. Check that the connector data uploaded correctly. In ConductorOne, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Cortex XDR connector to. Cortex XDR data should be found on the **Entitlements** and **Accounts** tabs. - -**That's it!** Your Cortex XDR connector is now pulling access data into ConductorOne. -{{< /markdown >}} -{{< /tab >}} -{{< /tab-group >}} -