> 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/post-compromise/external_nonhttp_beacon.md).

# external\_nonhttp\_beacon

Explanation Malware often engages in repeated communications with command and control systems, to check for instructions or updates. The external\_nonhttp\_beacon NDM detects network communications over

**Explanation**

Malware often engages in repeated communications with command and control systems, to check for instructions or updates. The external\_nonhttp\_beacon NDM detects network communications over non-http ports (ports other than 80 and 443) that have a repeating pattern, similar to the sort of communications associated with malware beaconing.

**What to Look For**

This NDM is opt-in, and may require some tuning to be effective on noisy networks. Many legitimate software applications engage in beaconing behavior, to check for software updates, or updates to information such as social media posts or the weather. Internet IP addresses that are identified by this NDM should be checked for IP Reputation, Reverse DNS, and Whois information to determine whether they are benign or suspicious. Configuring discards for IP ranges or AS organizations can help reduce false positives.

**Related MITRE ATT\&CK Categories**

[Command and Control: Application Layer Protocol, Technique T1071 - Enterprise](https://attack.mitre.org/techniques/T1071)


---

# 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/post-compromise/external_nonhttp_beacon.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.
