> 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/outbound_teredo_spike.md).

# outbound\_teredo\_spike

Explanation The outbound\_teredo\_spike NDM is designed to detect high volumes of Teredo packets leaving the customer network. Teredo is a protocol for encapsulating IPv6 packets in IPv4 UDP packets. Te

**Explanation**

The outbound\_teredo\_spike NDM is designed to detect high volumes of Teredo packets leaving the customer network. Teredo is a protocol for encapsulating IPv6 packets in IPv4 UDP packets. Teredo can be used for legitimate communication between IPv6-enabled networks or devices over an IPv4 infrastructure. However, it can also be exploited by attackers to bypass security measures, and can allow bidirectional access behind a firewall over IPv6.

**What to Look For**

Teredo is often enabled by default on Windows machines and some communication with the Internet may be expected. However, high volumes of communication could suggest that Teredo is in use and not idle. If Teredo traffic is not expected or authorized in the environment, investigate the sources and destinations of the traffic to determine if there are any signs of malicious activity. Many organizations chose to block outbound Teredo traffic at their firewalls.

**Related MITRE ATT\&CK Categories**

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


---

# 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/outbound_teredo_spike.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.
