> 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/onboard-atlassian.md). # Onboard Atlassian Connect an Atlassian instance in Cortex XSIAM to detect posture and compliance risks. Connect an Atlassian instance to SaaS Security to detect posture and identity risks, and to enable third-party plugin scans for Jira and Confluence. For SaaS Security to detect posture risks in your Atlassian instance, you must onboard your Atlassian instance to Cortex. Through the onboarding process, SaaS Security connects to an Atlassian API and, through the API, scans the Atlassian Administration settings for your organization. If there are misconfigured settings, SaaS Security suggests a remediation action based on best practices. SaaS Security also runs identity scans for account risks. Note: Some of the Atlassian Administration settings that SaaS Security scans affect Jira and Confluence. These are high-level Atlassian Administration settings for your organization, and will differ depending on whether your organization has the free, Standard, or Premium versions of these products. To have SaaS Security scan settings at the Jira and Confluence level, you must onboard a Jira app and onboard a Confluence app. If users have extended the capabilities of Jira and Confluence by installing third-party plugins, SaaS Security also detect the third-party plugins and the access that the plugins were granted. This information helps you determine the risks posed by third-party plugins so you can take action as needed. It is not necessary to onboard Jira and Confluence to SaaS Security to enable these third-party plugin scans. To access your Atlassian instance, SaaS Security requires the following information, which you specify during the onboarding process. | API Token | A token, generated by an Atlassian Org Admin, that enables SaaS Security to authenticate to the administrator account. | | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | API Key | A key, generated by an Atlassian Org Admin, that enables SaaS Security to scan and update organization settings and user accounts. SaaS Security uses this key to identify and manage the third-party plugins that users have connected to Jira or Confluence. | | Admin Email | The login email address of the Atlassian Org Admin who created the API token and API key. | To onboard your Atlassian instance, complete the following actions. *** ### Step 1: Generate and Copy an Administrator API Token To authenticate to an administrator account using an Atlassian API, SaaS Security requires an administrator API token. 1. Log in to Atlassian using Org Admin credentials. 2. From the Atlassian account profile, navigate to the API tokens page. Select Security > Create and manage API tokens, or go directly to[ id.atlassian.com/manage-profile/security/api-tokens](https://id.atlassian.com/manage-profile/security/api-tokens). 3. Click Create API Token. A dialog prompts you to specify a label for the API token. 4. Specify a label and click Create. Atlassian generates and displays your new API token. 5. Copy the API token and paste it into a text file.\ Important: Do not continue to the next step unless you have copied the API token. You must provide this token to SaaS Security during the onboarding process. *** ### Step 2: Generate and Copy an API Key for Your Organization To identify and manage the third-party plugins that users have connected to Jira or Confluence, SaaS Security requires an API key generated from an administrator account. SaaS Security also requires this API key for identity scans. 1. Log in to the[ Atlassian Admin Portal](https://admin.atlassian.com/) using Org Admin credentials. 2. If you administer more than one Atlassian organization, select the organization you want SaaS Security to scan for third-party plugins. 3. From the left navigation, select Organization settings > API keys. 4. On the API keys page, click Create API key. 5. On the Before you begin page, select API key without scopes and click Next.\ Note: You must select the API key without the scopes option. SaaS Security does not support scoped API keys. 6. In the Create an API key dialog, specify a name and an expiration date for the key and click Create. Atlassian generates and displays a new API key. 7. Copy the API key and paste it into a text file.\ Important: Do not continue to the next step unless you have copied the API key. You must provide this key to SaaS Security during the onboarding process. *** ### Step 3: Connect SaaS Security to Your Atlassian Instance By adding an Atlassian app in Cortex, you enable SaaS Security to connect to your Atlassian instance for posture and identity scans. Connecting the Atlassian app also enables SaaS Security to scan for third-party plugins connected to Jira and Confluence. 1. Log in to Cortex. 2. Select **Settings > Data Sources and Integrations > Add New**. You can use the Search bar to find the app you want to connect to. 3. Click the Atlassian tile. 4. On the **Capabilities** page, Enter a Name for your application. 5. Select Security Posture under **Default Capabilities**. 6. Click **Next**. 7. On the **Connections** page, enter the login email address of the Atlassian administrator who created the API token, and the API key. 8. On the **Configurations** page, select a **Sync Interval**. Choose a meaningful **Tag** to distinguish between various applications in different environments. 9. Click **Next** to complete the onboarding validation process. --- # 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/cloud-security/cortex-cloud-saas-security/connect-a-saas-application/onboard-atlassian.md?ask=&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.