> 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/getting-started/monitor-events/event-advisor.md).

# Event Advisor

### Overview

The **Event Adviser** helps you get detailed insight into CloudGuard WAF Security Events and is divided into three easy-to-read sections:

* What Happened?
* Why Was It Blocked?
* What Should You Do?

{% hint style="danger" %}
**Tech Preview Feature**\
This feature is currently is only visible with **Tech Preview** enabled. Functionality behavior could change in future releases. 
{% endhint %}

### How to Enable

* Navigate to "Monitor" Section and Enable Tech Preview on the Left Bottom side of the Menu Pane

<div align="left"><figure><img src="https://2760087783-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEWA4nfgNrSRL8dA6Kap7%2Fuploads%2FRVxdBcw4kZ4tOj9THI8m%2Fimage.png?alt=media&amp;token=76501e26-f412-435e-b813-b66fd79f23ba" alt=""><figcaption></figcaption></figure></div>

* Navigate to your CloudGuard WAF Security Logs.
* Right-click on any individual log entry.
* Select “Event Adviser” from the context menu.
* A panel opens on the right-hand side of the screen, showing the event analysis.

<figure><img src="https://2760087783-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEWA4nfgNrSRL8dA6Kap7%2Fuploads%2F4AWPK7h9Uhldfba5olZ0%2Fimage.png?alt=media&amp;token=5304bdd1-5064-4ac3-8cf2-f500773306a6" alt=""><figcaption></figcaption></figure>

### The Adviser Output

<figure><img src="https://2760087783-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEWA4nfgNrSRL8dA6Kap7%2Fuploads%2FsqC2VYKLunydJ72VGIWd%2Fimage.png?alt=media&amp;token=bf642b15-2d6a-4c74-ad21-4a4cf1e71199" alt=""><figcaption></figcaption></figure>

#### What Happened?

This section gives a short, clear summary of the event.

* It shows the request method (GET, POST, etc.), the source IP, the destination host/path, and whether the request was blocked or detected.
* Example: “*A POST request from 192.168.0.1 to the root path of "example.com" was blocked due to missing authentication token*.”

#### Why Was It Blocked?

This section explains why CloudGuard WAF took action.

* It describes what was missing, suspicious, or malicious in the request.
* Example: “*The request contained patterns matching Java JNDI injection attempts in the URL path. The presence of 'jndi:' in the URI is a strong indicator of an attempt to exploit Log4j vulnerabilities (Log4Shell) or similar Java deserialization attacks. The request also matched XPath injection patterns. These attacks could allow remote code execution or unauthorized data access on the target system*.*”*

#### What Should You Do?

This section provides recommended next steps.

The guidance here always starts with the verdict sentence, then adds 2–3 hardening steps relevant to the detected attack type(s):

* **If malicious (blocked/detected):** No action is required.&#x20;
* **If likely a false positive (blocked/detected but looks legitimate)**:  create a narrow Custom Rule/Exception for the specific URL and parameter or click ‘Report misclassification’

#### Reporting Misclassification

If you believe the log classification is incorrect (for example, a false positive), you can click Report misclassification.&#x20;


---

# 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://waf-doc.inext.checkpoint.com/getting-started/monitor-events/event-advisor.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.