> 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-control.md).
# Use a built-in or custom control
Add built-in controls or create and manage custom controls for custom standards.
When using custom standards, you can use built-in controls or create custom controls and then associate them with detection rules.
## Add a built-in control to a custom standard
Cortex Cloud provides built-in controls that cannot be edited or deleted. When you edit or create a custom standard you can add the built-in controls.
## Create a custom control to use in a custom standard
You can create a new control that is tailored to your own business needs, standards, and organizational policies to use in a custom standard.
1. In the **Controls** catalog, click **+ Create Control**.
2. Define control metadata, including:
* A single category
* A single sub category (optional)
* Control name
* Description (optional)
* One or more custom standards to associate the control with
3. Click **Create**.
4. Assign a custom detection rule to the control. See [Associate a custom control to a detection rule](#associate-a-custom-control-to-a-detection-rule).
## Associate a custom control to a detection rule
You can associate custom compliance controls with workload security and cloud security rules. This tailors compliance checks to your organization's needs. You can associate controls during rule creation or editing.
{% hint style="info" %}
**NOTE**
Custom rules can only be associated with custom compliance controls.
{% endhint %}
The following table shows which rule types support custom compliance controls:
| Rule type | Out-of-the-box rules | Custom rules |
| ------------------------ | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| **Cloud workload rules** | Not applicable. | Associate custom compliance controls when creating or editing custom cloud workload rules. |
| **Cloud security rules** | Associate custom compliance controls when editing existing rules. | Associate custom compliance controls when creating or editing custom cloud security rules. |
You can only associate custom compliance controls with ConfigIdentityAI cloud security rules.
To associate a custom compliance control:
1. Navigate to **Posture Management → Rules & Policies → Rules → Cloud Workload** or **Cloud Security**.
2. Create a policy, or edit an existing rule.
3. In **Overview → Compliance Controls**, click **Add**.
4. Select one or more custom compliance controls, then click **Assign**.
5. Save your changes.
## Manage existing controls
Existing compliance controls can be managed from **Posture Management → Compliance → Controls Catalog.**
### Edit or delete a custom control
Custom controls can be edited or deleted. Right click on a control or select 
from the control's side pane to access the **Edit** and **Delete** options. When editing a control, you can update all its parameters.
### Clone a control
All controls can be cloned using the **Save as new** option. Right click on a control or select from the control's side pane to access the option to **Save as new**. When cloning a control, you can update all its parameters. By default the original built-in control name is used with “\_copy“ appended.
---
# 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-cloud-runtime-security/compliance/monitor-and-track-compliance-adherence/choose-compliance-standards-from-the-compliance-catalog/use-a-built-in-or-custom-control.md?ask=&goal=
```
`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.