> For the complete documentation index, see [llms.txt](https://docs.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.vectra.ai/reference/about-reference.md).

# About Reference

Overview of Vectra AI reference articles on detections, scoring, appliances, metadata, security, and supported browsers.

Reference articles are standalone explanations and lookup material. They are grouped below by topic.

## Detections, scoring, and hosts

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>AI and ML terminology</strong></td><td>Definitions for common AI/ML terms used in Vectra docs.</td><td><a href="https://docs.vectra.ai/reference/ai-and-ml-terminology.md">AI and ML terminology</a></td></tr><tr><td><strong>Vectra AI prioritization and scoring factors</strong></td><td>FAQ for AI-driven Prioritization (Urgency scoring) in Respond UX.</td><td><a href="https://docs.vectra.ai/reference/ai-driven-priortization-faq.md">Vectra AI prioritization and scoring factors</a></td></tr><tr><td><strong>How detection PCAPs are generated</strong></td><td>How Detection PCAPs are created as part of Detect for NDR.</td><td><a href="https://docs.vectra.ai/reference/how-detection-pcaps-are-generated.md">How detection PCAPs are generated</a></td></tr><tr><td><strong>Host ID best practices and functionality</strong></td><td>Understand Vectra Host ID, host naming behavior, and best practices for configuration and traffic engineering.</td><td><a href="https://docs.vectra.ai/reference/understanding-vectra-host-naming.md">Host ID best practices and functionality</a></td></tr><tr><td><strong>Vectra's coverage of MITRE ATT&#x26;CK and D3FEND</strong></td><td>See how Vectra maps detections to MITRE ATT&#x26;CK v18 and supports MITRE D3FEND countermeasures, with navigator layers and export files.</td><td><a href="https://docs.vectra.ai/reference/vectra-coverage-of-mitre-attandck-and-d3fend.md">Vectra's coverage of MITRE ATT&amp;CK and D3FEND</a></td></tr></tbody></table>

## Appliances and network traffic

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Appliance support and EOS / EOL policy</strong></td><td>Appliance support policies, End-of-Sale (EOS) announcements, and End-of-Sale/End-of-Life (EOL) dates for Vectra appliances.</td><td><a href="https://docs.vectra.ai/reference/appliance-eos-eol-policy.md">Appliance support and EOS / EOL policy</a></td></tr><tr><td><strong>Bandwidth used between Sensor and Brain</strong></td><td>Expected bandwidth from Sensor to Brain and how to interpret low-bandwidth alerts.</td><td><a href="https://docs.vectra.ai/reference/bandwidth-used-between-sensor-and-brain.md">Bandwidth used between Sensor and Brain</a></td></tr><tr><td><strong>RSPAN and ERSPAN support</strong></td><td>RSPAN and ERSPAN compatibility for Vectra Sensors, including VLAN tag limits.</td><td><a href="https://docs.vectra.ai/reference/rspan-and-erspan-support.md">RSPAN and ERSPAN support</a></td></tr></tbody></table>

## Metadata and data sharing

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Metadata attributes</strong></td><td>Reference PDFs for Vectra network and cloud metadata fields.</td><td><a href="https://docs.vectra.ai/reference/metadata-attributes.md">Metadata attributes</a></td></tr><tr><td><strong>Why is metadata sharing important</strong></td><td>How metadata sharing works, what data is shared, and why it matters.</td><td><a href="https://docs.vectra.ai/reference/why-is-metadata-sharing-important.md">Why is metadata sharing important</a></td></tr></tbody></table>

## Security, support, and the Vectra UI

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Product Security</strong></td><td>Product security statements and hardening guidance.</td><td><a href="https://docs.vectra.ai/reference/product-security.md">Product Security</a></td></tr><tr><td><strong>In-App support</strong></td><td>Enable and manage in-app support, including telemetry fields and outbound endpoints.</td><td><a href="https://docs.vectra.ai/reference/in-app-support.md">In-App support</a></td></tr><tr><td><strong>Vectra UI supported browsers</strong></td><td>Supported browsers and version support policy for the Vectra UI.</td><td><a href="https://docs.vectra.ai/reference/vectra-ui-supported-browsers.md">Vectra UI supported browsers</a></td></tr></tbody></table>


---

# 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.vectra.ai/reference/about-reference.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.
