> 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/compliance/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

Use built-in standards or create and edit custom standards for your organization.

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 built-in standard you want to edit or select <img src="https://1003524119-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxWuY3s7AUvWfzCV9p1A%2Fuploads%2FVyzJ8CuS4HnBpwZhnFU7%2Freusable-menu.png?alt=media&amp;token=b6814b36-7520-400d-a824-3654dbea7a58" alt="" data-size="line"> from the standard's side pane.
2. Select **Save as new**.
3. Define compliance standard metadata, including:
   1. **Name**: By default, the original built-in standard name is used with “\_copy“ is appended. You can update it if needed.
   2. **Description**: You can update the description if needed.
   3. **Select Controls**: You can select or deselect controls as needed.
4. Click **Create**.

## 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.<br>

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 **Select Controls**, you select the controls that you would like to add to the standard.
5. Click **Create**.

## Manage existing custom standards

Custom compliance standards can be managed from **Posture Management → Compliance → Standards Catalog.** Right click on a standard or select <img src="https://1003524119-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxWuY3s7AUvWfzCV9p1A%2Fuploads%2FVyzJ8CuS4HnBpwZhnFU7%2Freusable-menu.png?alt=media&amp;token=b6814b36-7520-400d-a824-3654dbea7a58" alt="" data-size="line"> from the standard's side pane to edit or delete it. You can edit all parameters of the standard and update the list of controls assigned to it.


---

# 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/compliance/monitor-and-track-compliance-adherence/choose-compliance-standards-from-the-compliance-catalog/use-a-built-in-or-custom-standard.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.