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

# Informational

Informational detections are a category within Vectra Fusion's Vectra Detection Models (NDMs) that provide valuable insights about unusual but not necessarily malicious network behavior. These detect

Informational detections are a category within Vectra Fusion's Vectra Detection Models (NDMs) that provide valuable insights about unusual but not necessarily malicious network behavior. These detections are designed to inform and alert network administrators about irregularities that could impact network functionality or indicate potential vulnerabilities. For example, the 6in4tunnel detection flags IPv6 traffic tunneled over IPv4, which, while not inherently harmful, could be exploited for covert communication. The alltcpflags detection alerts when all TCP flags are set, an unusual condition often associated with network scanning or evasion techniques. While these detections may not always signify an imminent attack, they serve as critical informational tools for maintaining network hygiene and preemptively addressing potential security risks.


---

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