> 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-xsoar-6-threat-intel-management-guides/6.15/configure-indicators/indicator-management/indicator-relationships.md).

# Indicator Relationships

Create and manage relationships between indicators in Cortex XSOAR 6.15.

Relationships are connections between different Cortex XSOAR objects. These relationships can be IP addresses related to one another, domains impersonating legitimate domains, and more. These relationships enable us to enhance investigations with information about indicators and how they might be connected to other incidents or indicators. Within an incident, the Canvas enables you to see if there are any relationships between indicators in the incident and other indicators in the system.

{% hint style="info" %}
This feature is available only for users with a TIM license.
{% endhint %}

For example, if we have a phishing incident with several indicators, one of those indicators might lead to another indicator, which is a malicious threat actor. Once we know who the threat actor is, we can further investigate to see the incidents it was involved in, its known TTPs, and other indicators that might be related to the threat actor. Our initial incident which started off as a phishing investigation immediately becomes a true positive and it is related to a specific malicious entity.

{% hint style="info" %}
To fully benefit from the Indicator Relationships feature, make sure that your **Common Types** content pack is updated for new fields and layouts to be added and populated.
{% endhint %}

Relationships are created from threat intel feeds and enrichment integrations that support automatic creation of relationships. Based on the information that exists in the integrations, the relationships are formed.

In addition, you can manually create and modify relationships. This is especially useful when a specific threat report comes out, for example, Unit 42’s SolarStorm report. These reports contain indicators and relationships that might not exist in your system, or you might not be aware of their connection to one another.

If a relationship is no longer relevant, you can revoke it. This might be relevant for example, if a known malicious domain is no longer associated with a specific IP address.

### Investigate indicator relationships

This example shows how relationships enrich a phishing investigation.

1. Open the incident.

   The incident has low severity and two indicators.

   ![relationships\_new-incident.png](https://content.gitbook.com/content/BpHpUTEMW1LJCAHPgrpq/blobs/KM0OthhKPiP0BzqsFmBP/f61ffcf0f00da1da110a1d077f28ac5ab15dbdea5ad773212fef86091451fb1d.png)
2. Select the file hash indicator.

   The **Info** and **Relationships** tabs contain no additional details. The file appears harmless.

   ![relationships\_harmless-file.png](https://content.gitbook.com/content/BpHpUTEMW1LJCAHPgrpq/blobs/sXFdPLW1SsYgnTo7wIFc/1b50a5b07f1d6c31a9c4f50091988d509360253f706a334b585e5a9502393533.png)
3. Select the IP address indicator.

   The **Info** tab shows that a threat intel feed ingested the indicator. Investigate the indicator further.

   ![relationships\_ipIndicator-info.png](https://content.gitbook.com/content/BpHpUTEMW1LJCAHPgrpq/blobs/340ld7xEcUQMgMU89I0Z/891009f7b8b078f688c80a34a6a2d5a00a584a4e1e76c96d28da5d51cf8e91c7.png)
4. Select the **Relationships** tab.

   The indicator is related to a campaign.

   ![relationships\_ipIndicator-relationships.png](https://content.gitbook.com/content/BpHpUTEMW1LJCAHPgrpq/blobs/dQAv1TpCDl6pHOOnryxr/711e467c3834505b9b66603434e49d8de5a661b2ea4c37926622f6cf32cf8e0a.png)

   The low-severity incident now requires further investigation.
5. Select the **Canvas** tab.
6. In the **Indicators** tab of the **Add entity to canvas** pane, drag the IP address indicator to the canvas.
7. From the IP address indicator menu, select **Expand**.

   ![relationships\_ipIndicator-menu.png](https://content.gitbook.com/content/BpHpUTEMW1LJCAHPgrpq/blobs/PxdkCX6ppoMQA3Up0Pki/426a6c7d6d5adfce3b8e2765cd30baa664841efcff7687fea17cc24e8dcf218f.png)

   The campaign indicator appears on the canvas.
8. From the campaign indicator menu, select **Expand**.

   The canvas displays all indicators related to the campaign.

   ![relationships\_harmless-campaign.png](https://content.gitbook.com/content/BpHpUTEMW1LJCAHPgrpq/blobs/FNab7IEK7cS8UEw7iso2/d243e56f46179d8a12f83d89e50a6fa6eb74d172f79b6c8ea1389c4d743c866a.png)

   Investigate the threat actor, its techniques, and potential targets.

   Relationships and the canvas provide a fuller view of the incident.


---

# 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-xsoar-6-threat-intel-management-guides/6.15/configure-indicators/indicator-management/indicator-relationships.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.