> 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-xdr-5.x/detect-investigate-and-respond-to-threats/monitor-and-track-compliance-adherence/choose-compliance-standards-from-the-compliance-catalog/use-a-built-in-or-custom-standard.md).

# Use a built-in or custom standard

You can use a built-in industry standard or create a custom standard. A custom standard can be either a copy of a built-in standard or a custom standard created from scratch.

## Use a built-in standard

Cortex provides built-in industry approved regulatory compliance standards, for example **GDPR**. These standards cannot be edited or deleted, you can duplicate them to create a custom standard.

## Clone a built-in standard

To reuse and modify a built-in standard, clone the built-in industry standard:

1. In the **Standards** catalog, right-click on the custom standard you want to edit (or select <img src="/files/GWv0KyT4g3sfEmcLNNx3" alt="" data-size="line"> next to it) and then select **Save as new**.
2. Define compliance standard metadata, including:
   1. **Name**: By default, the original built-in standard name is used with “Copy of “ is prepended. You can update it if needed.
   2. **Description**: You can update the description if needed.
3. Click **Clone**.

You can edit categories and controls after cloning the standard.

## Create a custom standard

You can create a custom compliance standard that is tailored to your own business needs and organizational policies.

To organize controls within a custom compliance standard, you establish categories and optional sub-categories. Every control is defined as part of a specific standard and assigned to a single category within it. Sub-categories offer an additional layer of organizational structure.

1. In the **Standards** catalog, click **Create Standard**.
2. Define compliance standard metadata, including:
   1. **Name**
   2. **Description** (optional)
   3. **Labels** (optional)
3. Click **Next.**
4. Under **Categories & Controls**:
   1. Select **+Add Category** to create a new category. You must create at least one category. A category serves as a container for organizing controls within the specific standard.
   2. (Optional) Select **+Add Subcategory** to add a new sub-category using. A sub-category serves as an optional sub-container for organizing controls within the specific category.
   3. Select **+Add Control** to define controls within the category (and sub-category if selected). Next, enter **Control Name** and an optional **Description**. Repeat this step for each control. You can define up to 600 controls per standard.
   4. Add additional categories and sub-categories and then add controls to them. When done, click **Next**.
5. Review the summary of your changes.
6. Click **Create**.

## Edit a custom standard

You can edit an existing custom standard.

1. In the **Standards** catalog, right-click on the custom standard (or select <img src="/files/GWv0KyT4g3sfEmcLNNx3" alt="" data-size="line"> next to it) and then select **Edit**.
2. Define compliance standard metadata, including:
   1. **Name**
   2. **Description** (optional)
   3. **Labels** (optional)
3. Click **Next**.
4. Under **Categories & Controls**:
   1. Update or define new categories, sub-categories, and controls as needed.
   2. When done, click **Next**.
5. Review the summary of your changes and
6. Click **Save**.

## Delete a custom standard

To delete an existing custom standard and all the categories, subcategories, and controls associated with it, perform the following steps.

1. In the **Standards** catalog, right-click on the custom standard (or select <img src="/files/GWv0KyT4g3sfEmcLNNx3" alt="" data-size="line"> next to it ) and then select **Delete**.
2. Click **Delete**.


---

# 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-xdr-5.x/detect-investigate-and-respond-to-threats/monitor-and-track-compliance-adherence/choose-compliance-standards-from-the-compliance-catalog/use-a-built-in-or-custom-standard.md?ask=<question>&goal=<endgoal>
```

`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.