> 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/splunk/splunk.md).

# Splunk

Use Splunk data in Cortex XSIAM.

{% hint style="info" %}
The capabilities and sub-capabilities listed for this connector are available with any active Cortex XSIAM or Cortex Cloud Posture Security license.
{% endhint %}

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

* Security Posture: 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 Splunk connector

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

* **Okta subdomain**: Your Okta subdomain.
* **Username**: The username of the Splunk administrator account.
* **Password**: The password of the Splunk administrator account.
* **MFA secret key**: The MFA secret key generated for the administrator account.
* **Splunk domain**: Your Splunk Cloud app domain.

{% hint style="info" %}
**Prerequisites:** Your organization must use Okta as an identity provider. MFA using one-time passcodes must be configured.
{% endhint %}

#### Task 1: Connect to the Splunk API

1. Identify the Splunk administrator whose credentials you will supply to Cortex XSIAM.
2. Identify your **Okta subdomain**.
3. Generate and copy an **MFA secret key**.
4. Identify your **Splunk app domain**, which is a subdomain included in the Splunk Cloud URL. The URL format is `<app_domain>.cloud.splunk.com` or `<app_domain>.splunkcloud.com`.

#### Task 2: Connect Splunk to Cortex XSIAM

1. In Cortex XSIAM, navigate to **Settings** > **Data Sources & Integrations**.
2. Click **+ Add new**.
3. On the **Add Data Sources or Integrations** page, search for **Splunk**.
4. Under **Recommended**, hover over the Splunk 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 **Connection**, provide the following:
   * Okta subdomain
   * Administrator credentials
   * MFA secret key
   * Splunk domain
8. Click **Next**.
9. Under the **Configuration** tab, select a **Sync Interval**. Choose a meaningful **Tag** to distinguish between various applications in different environments. Click **Next**.
10. A confirmation message indicates that Splunk 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/splunk/splunk.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.