> 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-cloud-runtime-security/cortex-cloud-data-classification/how-to-use-information-protection-labels-in-cortex-data-security.md).

# How to use information protection labels

How to use information protection labels in Cortex Cloud Runtime Security

Information protection labels are digital tags that help your organization classify and secure sensitive data. They identify how sensitive a piece of information is, whether it's a document or an email. Once applied, these labels can automatically trigger protective measures like encryption to control who can access the file, or restrictions on who can edit or share it.

Ultimately, these labels are vital for enforcing your data policies and significantly cutting down the risk of data breaches. They ensure sensitive information is managed correctly throughout its entire journey, from when it's created to when it's no longer needed.

Each sensitivity label within your organization is assigned a unique GUID. This ensures consistent policy enforcement regardless of where the data resides or moves.

Once you have integrated Microsoft 365 with Cortex and after scanning, you can:

* View all the information protection labels available from your connected integrations.
* Create labeling policies that automatically apply an information protection label to files that match a specific data profile.
* Identify the files that have information protection labels, and view the specific GUIDs for each one.

For information about integrating Microsoft 365, see [How to onboard Microsoft 365](https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/microsoft/microsoft-365-posture/how-to-onboard-microsoft-365.md).

### How Cortex locates information protection labels

The Cortex scanner runs on your files and extracts the information protection labels from them during the classification process. This extraction is supported across all platforms and asset types, both file-based and unstructured.

#### Label translation

To enable the translation of Microsoft IDs to label names, connect to the Microsoft 365 integration.

**Example**

| GUID                                 | Translated Label   |
| ------------------------------------ | ------------------ |
| 6b29fc40-ca47-1067-b31d-00dd010662da | Sensitive-Internal |

### The IP Labels page

The IP Labels page is where you view the information protection labels available to Cortex and set up labeling policies that apply these labels to your files automatically.

To open the IP Labels page, go to **Settings → Configurations → Data Classification → IP Labels**.

#### Labels tab

The **Labels** tab lists all the information protection labels synced from your connected Microsoft 365 integrations. Use this tab to see which labels are available to you before you create labeling policies.

For each label, you can see its name, its ID, the integration it comes from, and its priority.

#### Policies tab

The **Policies** tab lists all your labeling policies and lets you create new policies and manage existing ones. For each policy, you can see its status, its sensitivity (the associated data profile), the label it applies and that label's priority, when and by whom it was last updated, and whether it overrides existing labels.

A labeling policy links a data profile to an information protection label. When Cortex finds files that match the data profile, it applies the selected label to them.

{% hint style="info" %}
**Note:** Cortex doesn't create new labels. You can only select from your organization's existing labels.
{% endhint %}

**How labeling policies work**

When files match an enabled policy's data profile, Cortex applies the policy's label to them through your Microsoft 365 integration, depending on the policy's override setting and the priority of any existing label.

Each policy has an **Override lower priority labels** option:

* **Off:** Files that already have a label are not changed.
* **On:** An existing label is replaced only if the policy's label has a higher priority than the existing label. Existing labels with an equal or higher priority are not replaced.

If more than one policy uses the same data profile, only the enabled policy with the highest priority is applied. The other policies have the **Blocked** status.

**Manage labeling policies**

From a policy's row actions, you can edit, enable, disable, copy, or delete the policy.

To create a labeling policy, click **Add new policy**, fill in the required fields, and save the policy.

{% hint style="info" %}
**Note:** If you disable a data profile that is used by a labeling policy, the policies attached to that data profile are also disabled.
{% endhint %}

### Find files that have information protection labels

1. In the navigation pane on the left, click **Modules → Data Security**.
2. Under **Objects Inventory**, click **Files**.
3. On the **Files Inventory** screen, click **Show filter panel** to open the filter panel and then do the following:
   1. In the **Select field** list, select **Has Information Protection Labels**.
   2. In the next list to the right, select the equals sign **(=)**.
   3. In the next field to the right, select **Yes**.
   4. Click anywhere in the screen outside the filter panel area.

      Now only files with information protection labels are displayed. In the **Information Protection Labels** column, the IDs for these labels appear.

{% hint style="info" %}
**Note:** The information protection labels appear only if you have connected a Microsoft 365 instance to Cortex Data Security. See [How to onboard Microsoft 365](https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/microsoft/microsoft-365-posture/how-to-onboard-microsoft-365.md).
{% endhint %}


---

# 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-cloud-runtime-security/cortex-cloud-data-classification/how-to-use-information-protection-labels-in-cortex-data-security.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.
