> 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_threema.md). # messaging\_threema **Explanation** The messaging\_threema NDM is designed to detect the presence of Threema messaging application on the network. Threema is a secure messaging application that is commonly used by individuals and organizations to protect their communication from unauthorized access. **What to Look For** If this NDM is triggered, administrators should check if Threema is present on the network or any endpoints. They should examine the traffic and see whether it is originating from or directed towards Threema servers. This can help identify any potential security risks and vulnerabilities that need to be addressed. It is important to note that Threema traffic may appear as encrypted and this is normal for this application. Admins should also check their organization's security policies regarding the use of secure messaging applications and ensure that Threema usage is not violating those policies. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.fusion.vectra.ai/detection-models/library/operational-governance/messaging_threema.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.