> 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/serverless-function-posture-security/serverless-function-posture-policies/manage-serverless-function-policies.md).

# Manage serverless function policies

Serverless function policies define how a system should respond to serverless function threats. They include conditions that trigger the policy, the scope of its application, and the actions to be taken when these conditions are met. When policies detect a threat, they generate issues for remediation.

### How to access serverless function policies

1. Under **Posture Management**, select **Rules & Policies** → **Cloud Security (under Policies)**.
2. Select the **Show filter panel** icon.
3. Filter the table by the **Asset Types** category and select your cloud provider serverless function type from the **Select values** menu. Options:

   * **Azure Cloud Function**
   * **Google Cloud Functions:** 1st gen and 2nd gen (Cloud Functions API and Cloud Run Admin API)
   * **Lambda Function (AWS)**

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>You can select multiple types to view all your serverless function rules across your cloud providers.</p></div>

   A list of serverless function rules filtered by asset type is displayed.

### Manage serverless function policies

You can delete, edit or clone serverless function policies.

* Delete a policy when no longer relevant, to avoid overhead
* Edit a policy to fine-tune existing policies
* Clone a policy to saves time by reusing settings and applying policies uniformly across similar assets, ensuring standardized policies and predictable behavior

1. Under **Posture Management**, select **Rules & Policies** → **Cloud Security (under Policies)**.
2. Filter for the list of serverless function policies. Refer to [How to access serverless function policies](#how-to-access-serverless-function-policies) above for more information.
3. Right-click on a policy.

   * To delete a policy, click **Delete**, and confirm the deletion in the popup
   * To edit a policy, click **Edit**.

     You are redirected to the **Details** step of the **Edit Policy** wizard.
   * To clone a policy, select **Save as new**.

     You are redirected to the **Details** step of the new policy wizard.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>Refer to <a href="/spaces/AEIjuYE3RXcIfmuQnBbm/pages/JCPEZXLzl6RrjupW4VAj">Create serverless function policies</a> for more information on how to define the steps of a policy in the wizard.</p></div>


---

# 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-xsiam/cloud-security/serverless-function-posture-security/serverless-function-posture-policies/manage-serverless-function-policies.md?ask=<question>&goal=<endgoal>
```

`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.
