> For the complete documentation index, see [llms.txt](https://waf-doc.inext.checkpoint.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://waf-doc.inext.checkpoint.com/how-to/how-to-enable-websocket-scanning.md).

# How to Enable WebSocket Scanning

You can enable scanning of WebSocket traffic for a Web Application profile by adding a WebSocket URL alongside your regular application URLs.

### Steps

1. Go to the profile's **Web Application** configuration screen or use the **Onboarding Wizard**
2. Under **Users will access the application / API at these URLs**, click **+** and add your WebSocket URL (e.g., `ws://websocketexample`).

<figure><img src="/files/crXYBcTuxUXiXr7Ih3MF" alt=""><figcaption></figcaption></figure>

### GenAI Security Settings (optional)

If the WebSocket traffic carries GenAI/LLM prompts, you can also configure:

* **Request URI** — the request path to inspect (e.g., `/api/chat`).
* **Prompt Location** — where in the request body the prompt is located (e.g., `body.prompt`).

Additional GenAI options are available under [**GenAI Advanced**](/additional-security-engines/genai-security.md)

{% hint style="info" %}

### EA Requirement

For Early Availability (EA), WebSocket scanning also requires enabling the following key under the profile's **Advanced Settings**:

{% code overflow="wrap" %}

```
agent.webSocketStream.nginxModule: true
```

{% endcode %}

Without this key, WebSocket traffic will not be streamed to the scanning module even if a WebSocket URL is defined.
{% 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 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://waf-doc.inext.checkpoint.com/how-to/how-to-enable-websocket-scanning.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.