> 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-posture-management/rules-and-policies/cloud-security-rules-and-policies/create-and-manage-cloud-security-rules/edit-a-cloud-security-rule.md).

# Edit a cloud security rule

Edit cloud security rules in Cortex Cloud Posture Management and review their effect on related issues.

You can edit custom cloud security rules and modify their parameters as needed.

In some cases, you can also edit and modify parameters of out-of-the-box rules:

* You can add labels to out-of-the-box attack path, config, and network exposure rules.
* You can associate AI, config, and identity rules with custom compliance controls.

To edit a rule:

1. Navigate to **Posture Management** → **Rules & Policies** → **Rules** → **Cloud Security**.
2. From the **Rules** page, there are two ways to access the option:
   1. Right-click the entry and then select **Edit.**
   2. Click on the rule. Next, on the **Details** page, click the more options icon (⋮) and then select **Edit.**
3. Make the necessary changes.
4. Click **Done** to save your changes.

Note that the following may happen as a result of editing a rule:

* When rule logic is modified, if the assets which were violating the rule earlier are not violating it anymore, the corresponding issues are closed.
* When certain rule attributes such as severity or labels are modified, if these attributes matched earlier but do not match after the edit, the rule may be excluded from the policy and the corresponding issues closed.


---

# 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-posture-management/rules-and-policies/cloud-security-rules-and-policies/create-and-manage-cloud-security-rules/edit-a-cloud-security-rule.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.