> 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_zalo.md).

# messaging\_zalo

Explanation The messaging\_zalo NDM is a network security event designed to detect the use of messaging applications on the network, with a particular focus on the Zalo messaging platform. What to Look

**Explanation**

The messaging\_zalo NDM is a network security event designed to detect the use of messaging applications on the network, with a particular focus on the Zalo messaging platform.

**What to Look For**

To examine the results of the messaging\_zalo event, network administrators should look for traffic patterns associated with Zalo messaging. This may include an increase in traffic volume or the use of specific ports or protocols that are associated with the Zalo platform. Endpoint forensic analysis may also be necessary to identify individual users or devices that are using the Zalo messaging app on the network. Remediation may involve blocking Zalo messaging traffic or implementing stricter access controls to prevent unauthorized use of the application.


---

# 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_zalo.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.
