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

# messaging\_pushover

**Explanation**

The messaging\_pushover NDM is designed to detect the presence of the messaging platform Pushover on the network.

**What to Look For**

Customers should examine their network traffic for any indications of Pushover usage. This may include the use of specific ports or protocols associated with Pushover, or the presence of Pushover data patterns in network traffic. Endpoint devices should also be examined for the presence of Pushover applications or related software. To remediate the issue, any unauthorized Pushover usage or software should be removed from the network or endpoint devices.


---

# 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_pushover.md?ask=<question>&goal=<endgoal>
```

`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.
