> For the complete documentation index, see [llms.txt](https://docs.fusion.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fusion.vectra.ai/detection-models/library/operational-governance/messaging_whatsapp.md).

# messaging\_whatsapp

Explanation The messaging\_whatsapp NDM detects the presence of messaging applications on the network, with a specific focus on WhatsApp. This NDM works by analyzing network traffic to determine the pr

**Explanation**

The messaging\_whatsapp NDM detects the presence of messaging applications on the network, with a specific focus on WhatsApp. This NDM works by analyzing network traffic to determine the presence of any WhatsApp connections.

**What to Look For**

Customers should look for any traffic associated with WhatsApp on their networks, especially during times when such traffic is unexpected or out of the ordinary. They should also examine the endpoints on their network for any instances of WhatsApp being installed or used. This information will help security professionals to identify any potential risks associated with the use of WhatsApp on their network and take appropriate action to minimize those risks.


---

# 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.fusion.vectra.ai/detection-models/library/operational-governance/messaging_whatsapp.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.
