> 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/protect-your-endpoints/endpoint-security/install-and-manage-endpoints/manage-endpoint-protection/create-a-new-prevention-policy-rule-for-serverless-function.md).

# Create a new prevention policy rule for serverless function

Create Cortex XSIAM prevention policy rules for serverless functions.

{% stepper %}
{% step %}
From **Inventory → Endpoints → Policy Management → Prevention → Profiles**, right-click the profile and select **Create a new policy rule using this profile**.

Cortex XSIAM automatically populates the Platform selection based on your profile configuration as well as the Restricitons selection with the selected profile.
{% endstep %}

{% step %}
For **Policy Name**, enter a meaningful name, and optionally, add a description for the policy rule, and then click **Next**.
{% endstep %}

{% step %}
Use the filters to define criteria for the policy rule to apply, and then click **Next**.

#### Select from the following function parameters:

* Cloud provider
* Region
* Runtime
* Function version
* Endpoint name
  {% endstep %}

{% step %}
Review the policy rule summary, and then click **Done**.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
The filter is stored within the policy definition and assessed during runtime to extract the functions that match the filter criteria.
{% endhint %}


---

# 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/protect-your-endpoints/endpoint-security/install-and-manage-endpoints/manage-endpoint-protection/create-a-new-prevention-policy-rule-for-serverless-function.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.