> 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-xsiam/cloud-security/rules-and-policies/cloud-security-rules-and-policies/create-and-manage-cloud-security-policies/use-an-existing-policy-to-create-a-new-one.md).

# Use an existing policy to create a new one

Clone an existing cloud security policy in Cortex XSIAM and tailor it to your needs.

You can use an existing custom or default cloud security policy to create a new one. To create a new cloud security policy using an existing policy:

1. Navigate to **Posture Management** → **Rules & Policies** → **Policies** → **Cloud Security**.
2. From the **Policies** page, there are two ways to access the option:
   * Right-click the entry and then select **Save as New.**
   * Click on the policy. Next, on the **Details** page, click the more options icon (⋮) and then select **Save as New.**
3. Modify the Policy Name, Description, and Labels fields as necessary.
4. Select the Rules that you would like to be alerted on:
   * All Matching Filter Criteria
   * Rules List
   * All Rules
5. Select the Scope that you would like to be alerted on:
   * Cloud Accounts
   * Asset Groups
   * All Cloud Assets
6. Click **Done** to save the new custom policy.


---

# 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-xsiam/cloud-security/rules-and-policies/cloud-security-rules-and-policies/create-and-manage-cloud-security-policies/use-an-existing-policy-to-create-a-new-one.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.