> 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_meta-messaging.md).

# messaging\_meta-messaging

Explanation This NDM is designed to detect the presence of any "Meta" messaging applications on a network. What to Look For To examine the results of the messaging\_meta-messaging event, customers shou

**Explanation**

This NDM is designed to detect the presence of any "Meta" messaging applications on a network.

**What to Look For**

To examine the results of the messaging\_meta-messaging event, customers should look for patterns of messaging traffic on their networks. This might include traffic from popular messaging apps such as WhatsApp, Facebook Messenger, or Instagram. Customers should also examine endpoint devices for evidence of messaging applications installed or active. If messaging traffic is identified, customers should investigate the source and destination of the traffic to determine if it is legitimate or potentially malicious. Remediation may involve blocking or restricting certain messaging applications, or investigating further to identify potential security threats.


---

# 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_meta-messaging.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.
