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

# YouTrack

Use YouTrack data for Cortex XSIAM.

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

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 YouTrack connector <a href="#how-to-configure-the-aha-connector" id="how-to-configure-the-aha-connector"></a>

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

* **Instance name**: The unique subdomain that identifies your organization's YouTrack instance, as shown in your YouTrack URL: .youtrack.cloud.
* **Permanent token**: A token generated from a YouTrack administrator account assigned to the System Admin role. The token must be scoped to YouTrack and YouTrack Administration.

#### **Task 1: Gather YouTrack account information**

1. Open a browser and go to your YouTrack login page. Your instance name is the subdomain shown in the URL: \<instance-name>.youtrack.cloud. Record your instance name before proceeding. You must provide it during the data connection process.
2. Log in to YouTrack as an administrator assigned to the System Admin role.
3. Click your account avatar in the upper-right corner and select **\<your-avatar> > Profile**.
4. On your profile page, go to Account Security.
5. In the Tokens section, click **New token**.
6. In the New Permanent Token dialog:
   * Enter a name for the token.
   * Select the following scopes:
   * YouTrack
   * YouTrack Administration
7. Click **Create**. YouTrack displays the new permanent token.
8. Click **Copy token** and save it to a text file. Do not proceed until you have copied the token. You must provide it during data connection.

#### **Task 2: Connect** YouTrack **to Cortex XSIAM**

1. In Cortex XSIAM, navigate to **Settings** → **Data Sources & Integrations**.
2. Click **+ Add new**.
3. In the **Add Data Sources or Integrations** page, search for YouTrack.
4. Under **Recommended**, hover over the new YouTrack 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**.
7. Click **Next**.
8. Under **Connection**, enter your **Instance Name** and **Permanent Token**.
9. Under **Configuration** tab, select a **Sync Interval**. Choose a meaningful **Tag** to distinguish between various applications in different environments.
10. A confirmation message indicates that YouTrack 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/youtrack/youtrack.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.