> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/admin-guide/33/web-application-and-api-security-waas/deploy-waas/deployment-serverless.md).

# Deploy WAAS for Serverless

## Create a WAAS rule for serverless

When Serverless Defender is embedded in a function, it offers built-in web application firewall (WAF) capabilities, including protection against:

* SQL injection (SQLi) attacks
* Cross-site scripting (XSS) attacks
* Command injection (CMDi) attacks
* Local file system inclusion (LFI) attacks
* Code injection attacks

Some [protections](https://docs.prismacloud.io/admin-guide/33/web-application-and-api-security-waas/waas-app-firewall.md) are not available for WAAS serverless deployment.

**Prerequisites:** You already [embedded Serverless Defender](https://github.com/PaloAltoNetworks/pc-docs-md/tree/main/compute-edition/33/admin-guide/install/deploy-defender/serverless/serverless.md) into your function.

1. Open Console and go to **Defend > WAAS > Serverless**.

   <figure><img src="https://2496555403-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbxtMJ4BKXGNuCZ9JYDpl%2Fuploads%2Fgit-blob-e54316d2d62baeaa36d8bb77624be073b61191f2%2Fwaas_deployment_types_serverless.png?alt=media" alt="waas deployment types serverless"><figcaption></figcaption></figure>
2. Click **Add rule**.
3. Enter a rule name.
4. Choose the rule **Scope** by specifying the resource collection(s) to which it applies.

   Collections define a combination of functions to which WAAS should attach itself to protect the web application:

   Use [pattern matching](https://docs.prismacloud.io/admin-guide/33/configure/rule-ordering-pattern-matching.md) to precisely target your rule.

   <figure><img src="https://2496555403-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbxtMJ4BKXGNuCZ9JYDpl%2Fuploads%2Fgit-blob-401c196cfd1e62671f77713df0edb2918387b6d3%2Fwaas_serverless_collections.png?alt=media" alt="waas serverless collections"><figcaption></figcaption></figure>
5. Select the protections to enable.

   <figure><img src="https://2496555403-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbxtMJ4BKXGNuCZ9JYDpl%2Fuploads%2Fgit-blob-f0b05531e0ec493cfe539fbc701a067b06d9db96%2Fwaas_serverless_protections_view.png?alt=media" alt="waas serverless protections view"><figcaption></figcaption></figure>
6. Select **Alert** or **Prevent**.
7. If necessary, adjust the **Proxy timeout**

   The maximum duration in seconds for reading the entire request, including the body. A 500 error response is returned if a request is not read within the timeout period. For applications dealing with large files, adjusting the proxy timeout is necessary.


---

# 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://docs.prismacloud.io/admin-guide/33/web-application-and-api-security-waas/deploy-waas/deployment-serverless.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.
