> 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/cloud-security/cortex-cloud-saas-security/connect-a-saas-application.md). # Connect a SaaS application To detect posture risks, applications must first be connected to Cortex SaaS Security and have the necessary permissions to scan SaaS application settings. During data connection, Cortex SaaS Security prompts you for the configuration information required to establish a connection with the SaaS app. The configuration information that SaaS Security requires differs from app to app, and you might need to collect configuration information prior to onboarding. When you connect an application you may also be prompted to provide required for application connection, such as administrator credentials for a service account. The required information varies, and in many cases you must first take some actions on the SaaS app, such as creating an API key. The following table provides links to detailed connection instructions for most applications. Where detailed instructions are not available for a particular SaaS application, the table includes the relevant onboarding steps. | **SaaS app connection steps** | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [Aha.io](/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/aha/aha.md) | | [Asana](/cortex-xsiam/cloud-security/cortex-cloud-saas-security/connect-a-saas-application/onboard-asana.md) | | [Atlassian](/cortex-xsiam/cloud-security/cortex-cloud-saas-security/connect-a-saas-application/onboard-atlassian.md) | | [Automox](/cortex-xsiam/cloud-security/cortex-cloud-saas-security/connect-a-saas-application/onboard-automox.md) | | [BusinessMap](/cortex-xsiam/cloud-security/cortex-cloud-saas-security/connect-a-saas-application/onboard-businessmap.md) | | [Celonis](/cortex-xsiam/cloud-security/cortex-cloud-saas-security/connect-a-saas-application/onboard-celonis.md) | | [Cisco Duo](/cortex-xsiam/cloud-security/cortex-cloud-saas-security/connect-a-saas-application/onboard-cisco-duo.md) | | [Cisco Meraki](/cortex-xsiam/cloud-security/cortex-cloud-saas-security/connect-a-saas-application/onboard-cisco-meraki.md) | | [Clickup](/cortex-xsiam/cloud-security/cortex-cloud-saas-security/connect-a-saas-application/onboard-clickup.md) | | [Contentful](/cortex-xsiam/cloud-security/cortex-cloud-saas-security/connect-a-saas-application/onboard-contentful.md) | | [Couchbase](/cortex-xsiam/cloud-security/cortex-cloud-saas-security/connect-a-saas-application/onboard-couchbase.md) | | [Coveo](/cortex-xsiam/cloud-security/cortex-cloud-saas-security/connect-a-saas-application/onboard-coveo.md) | | [Databricks](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/XS0S7JoLUifZC5D1tNjh) | | [DataDog](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/qwK9HOtK4c1roLQP2En2) | | [Gainsight](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/V8BHFmau7XAfswLb4uhu) | | [Grammarly](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/YujZOBkTG6uE0Ty0UTqB) | | [Harness](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/0HUUohyappwI96dtIseT) | | [Intercom](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/S579x9jfdjT6r6Qth32j) | | [Jamf Pro](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/Ueapw1T0b95O6X86p3PZ) | | [Jumpcloud](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/hcIdnIvH9yEagQSaUaHS) | | [Kustomer](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/KMPW2rJZqTmV4a6S3Mj6) | | [Microsoft Entra](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/ZxzogzRakmegK49mbn2f) | | [Monday](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/iUdvZin5zkDJ5SJWCGNW) | | [MongoDB](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/hiPb6tWDlFuuDoVEeHsF) | | [Mulesoft](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/8tBw1ifJJhiQ7X9SSvwp) | | [Mural](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/mM0rViZV1sCINLQWwbjA) | |

Nintex Workflow Cloud

Complete the following steps to connect to a Nintex Workflow Cloud API:

  1. Log in to a Nintex Workflow Cloud account that is assigned to the Global administrator role.
  2. From the Apps and Tokens page in your Nintex Workflow Cloud settings, add an app.
  3. Copy the Client ID and the Client Secret that is associated with your app.
  4. During onboarding, provide the Client ID and the Client Secret that is associated with your app.
| | [Office365](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/YyKcBu75bHUt9tkBXMVY) | | [Okta](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/yMOZ9bwhYFDhc3kM0gZW) | | [Pagerduty](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/lgjrfzz4u2jzUVaVEgT5) | |

Ping Identity

Complete the following steps to enable to connect a Ping Identity API:

  1. Log in to Ping Identity as an administrator assigned to either the Organization Admin or Environment Admin role.
  2. Create a Ping Identity worker application, which will inherit your role assignments and enable access to the API. Copy the application's Client ID and Client Secret.
  3. Copy your Environment ID and Region, which are shown on your environment page in Ping Identity.

  4. During onboarding, provide the following information:

| |

Pipedrive

Complete the following steps to connect to a Pipedrive API:

  1. Log in to Pipedrive as an administrator and copy the administrator's personal API token.
  2. During onboarding , provide the API token.
| |

Qualtrics

Complete the following steps to enable configuration information access through an administrator account. Your organization must be using Okta as an identity provider. MFA using one-time passcodes must be configured.

  1. Identify the Qualtrics XM administrator whose credentials you will supply to SSPM. The account must have Brand Administrator authority.

  2. To enable SSPM to access the account using Okta credentials:

    1. Identify your Okta subdomain.
    2. Generate and copy an MFA secret key.
  3. Identify your Organization ID. After you log in to Qualtrics XM, your organization ID is included in the Qualtrics XM URL. The URL format is \.qualtrics.com.
  4. Identify your SSO display name. To get the display name, go to AdminOrganization> SettingsSSO and open the Edit page for the SSO connection.
  5. During onboarding, provide the information above.
| | [Redis Labs](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/WCSSdrmhCQsH9jNNKpo8) | | [Salesforce](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/QK8JbDj0lTTaLtB02eWZ) | | [SAP Ariba](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/1rbCk7qLRgCJB4YBZNmP) | | [Sentryio](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/Vs8VKTrifsm3hWyLLBtg) | | [ServiceNow](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/aTQ116uYWVFfJJYRTM86) | | [Shopify](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/0RiUN8WRIH5OSgJYXrjh) | | [Slack](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/wTEhOsmFLM2bltJRpQjE) | |

Splunk

Complete the following steps to enable access to configuration information through an administrator account. Your organization must be using Okta as an identity provider. MFA using one-time passcodes must be configured.

  1. Identify the Splunk administrator whose credentials you will supply to SSPM.

  2. To enable SSPM to access the account using Okta credentials:

    1. Identify your Okta subdomain
    2. Generate and copy an MFA secret key
  3. Identify your Splunk app domain, which is a subdomain included in the Splunk Cloud URL. The URL format is \.cloud.splunk.com or \.splunkcloud.com.
  4. During onboarding, provide your organization's Okta domain, the administrator credentials, the MFA secret key, and the Splunk app domain.
| | [sumologic](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/lKntcZTtFaYqG16DMlil) | |

VMware

Complete the following steps to to connect to a VMWare API.

  1. Log in to VMWare Cloud Services using an account that is assigned to the Organization Owner role.

  2. Generate and copy an API token for the organization. Configure the API key to these specifications:

  3. Copy your Organization ID, which you can access from your profile.
  4. (Optional) Activate MFA for tokens that are associated with the account, and copy the MFA secret key for the account.
  5. During onboarding, provide the API token and your organization ID. If you configured MFA for tokens, also provide your MFA secret key.
| | [Workday](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/oVUfw3KSiu7F5LfM7pPJ) | | [Wrike](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/eGKq3RwXdXPTy8SebPoL) | | [Youtrack](broken://spaces/AEIjuYE3RXcIfmuQnBbm/pages/btHK19uwAjOVqqEce82e) | --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam/cloud-security/cortex-cloud-saas-security/connect-a-saas-application.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.