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

# Manage serverless function rules

Serverless function rules are designed to detect security threats within your serverless function environment that can potentially introduce vulnerabilities to its security. Serverless function rules identify and flag issues based on predefined criteria, ensuring that potential threats are proactively detected and addressed to enhance the overall security posture of your serverless functions. There are three categories or types of serverless function rules:

* **Attack Path**: These rules identify combined risks in your serverless function configurations, like overly permissive roles and network exposure, that could be exploited to breach your serverless applications
* **Config**: These rules detect security resource misconfigurations in your serverless function configurations and their related code and pipeline infrastructure
* **Network Exposure**: These rules detect internet-exposed serverless functions by leveraging network configurations monitored across your cloud environment

### **How to access serverless function rules**

To access serverless function rules:

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

   * **Azure Cloud Function**
   * **Google Cloud Function** (Gen 1 only)
   * **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 policies across your cloud providers.</p></div>

   A table of serverless function rules filtered by asset type is displayed. Serverless functions properties unique or important enough to mention to serverless functions include:

   * **Provider**: The cloud provider (such as WAS) associated with the serverless function
   * **Severity**: The severity level of findings associated with the rule
   * **Asset Types**: The type of serverless function. Options: Lambda Function, Google Cloud Function, Azure Cloud Function
   * **Type**: The type of serverless function rule. Options: Attack Path, Config, Network Exposure

### **Manage serverless function rules**

You can edit or clone serverless function rules.

* Edit a rule to fine-tune existing rules
* Clone a rule 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 Rules)**.
2. Filter for the list of serverless function rules. Refer to [How to access serverless function rules](#UUID-8868b0b1-16a6-1efb-207b-b8caeba7653f_section-idm234927012195576) above for more information.
3. Right-click on a rule.

   * To edit a rule, click **Edit**.

     You are redirected to the **Overview** step of the **Edit Rule** wizard.
   * To clone a rule, select **Save as new**.

     You are redirected to the **Overview** step of the new rules wizard.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>Refer to <a href="/pages/qXrctjqL5767fEBhwc3z">Create serverless function rules</a> for more information on how to define the steps of a rule 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-cloud-posture-management/serverless-function-posture-security/serverless-function-posture-rules/manage-serverless-function-rules.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.
