> 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/create-a-cloud-security-policy.md).

# Create a cloud security policy

Create a cloud security policy in Cortex XSIAM that applies security rules to selected cloud assets.

To create a cloud security policy:

1. Navigate to **Posture Management** → **Rules & Policies** → **Policies** → **Cloud Security**.
2. Click **Create Policy**.
3. On the **Details** page, provide **Policy Name**, **Description**, and **Labels** (optional).
4. Click **Next**.
5. On the **Rules** page, select which rules to be alerted on by using the available filters. You have three options:
   1. **All Matching Filter Criteria** - Include rules that match specific attributes (e.g., all critical severity rules).
   2. **From Rules List** - Manually select specific rules from the available inventory.
   3. **All Rules** - Include all available rules.
6. Click **Next**.
7. On the **Scope** page, select which scope to be alerted on:
   1. From Cloud Accounts - Select the specific cloud provider account to which the asset belongs.
   2. From Asset Groups - Select the specific logical groupings of assets (e.g., "Production" or "PCI Environment"). An asset group can have assets across different accounts, as the filter logic for the group can be generic (e.g., provider = AWS).
   3. All Cloud Assets - Apply to the entire tenant.
8. Click **Done** to save the 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/create-a-cloud-security-policy.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.