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

# messaging\_telegram

Explanation The messaging\_telegram event is a security event in the Netography Fusion Portal that evaluates for the presence of Telegram messaging application on the network. What to Look For To analy

**Explanation**

The messaging\_telegram event is a security event in the Netography Fusion Portal that evaluates for the presence of Telegram messaging application on the network.

**What to Look For**

To analyze the results of the messaging\_telegram event, look for network traffic associated with the Telegram application, including the server IP addresses and communication patterns. On the endpoint, check for the presence of the Telegram client application, including the installation path and file hashes. The messaging\_telegram event is critical for detecting potential security threats resulting from Telegram usage on the network, such as data exfiltration or malware distribution.


---

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