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

# Reconnaissance

Reconnaissance detections are an essential component of Vectra Fusion's Vectra Detection Models (NDMs) that are designed to identify and alert network administrators to activities associated with scan

Reconnaissance detections are an essential component of Vectra Fusion's Vectra Detection Models (NDMs) that are designed to identify and alert network administrators to activities associated with scanning and reconnaissance. These detections help identify potential attackers who are seeking information about the network and its infrastructure. For example, the system can detect Port Scanning and Service Enumeration attempts, which indicate an attacker is trying to identify open ports and the services running on them. The detection of OS Fingerprinting attempts can identify an attacker's attempt to learn more about the target operating system and any associated vulnerabilities. By identifying these reconnaissance activities, the system can alert network administrators to the presence of potential threats and enable them to take the necessary steps to mitigate these threats before they escalate into a full-blown attack.


---

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