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

# Attack

Attack detections within Vectra Fusion's Vectra Detection Models (NDMs) are designed to identify and alert network administrators to attempts to break into their networks remotely. These detections l

Attack detections within Vectra Fusion's Vectra Detection Models (NDMs) are designed to identify and alert network administrators to attempts to break into their networks remotely. These detections look for suspicious patterns of network activity coming inbound from the Internet, including, in some cases, activity that is coming from IP addresses with bad reputations. Although scanning, brute force, and other malicious activity is quite common on the Internet, the NDMs in the attack category detect patterns of activity that may be of greater concern, such as interactive login sessions. By promptly identifying these indicators, the NDMs allow network administrators to take immediate action, mitigating further damage and initiating incident response procedures if necessary.


---

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