> 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/configuration/coverage/detection-engineering-best-practices.md).

# Detection Engineering best practices

Detection Engineering lets you build, tune, and manage custom detections for your Vectra AI Platform (RUX) deployment.

Detection engineering is available for both cloud detections based on flow and DNS logs and for network detections based on packet level metadata gathered from network Sensors.

This feature is only available in Respond UX (RUX deployments). If you are unsure of your deployment type, please see [Analyst UX options (RUX vs QUX)](/deployment/getting-started/analyst-ux-options-rux-vs-qux.md).

Custom Models are also available for QUX deployments but the mechanism for creating them is different. Please see [Recall custom models - how to create detections (QUX)](/operations/analyst-guidance/recall-custom-models-how-to-create-detections-qux.md) for details.

{% hint style="info" %}
**Please Note:**

Detection Engineering is currently in Private Preview. If the feature is not available in your tenant and you wish to participate in the Private Preview, please reach out to your Vectra account team to discuss.
{% endhint %}

Please see either page below for details:

* [Detection Engineering Cloud](/configuration/coverage/detection-engineering-best-practices/detection-engineering-cloud.md)
  * Enable and edit available flow log-based detections.
* [Detection Engineering Network](/configuration/coverage/detection-engineering-best-practices/detection-engineering-network.md)
  * Create and manage network metadata-based detections.


---

# 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/configuration/coverage/detection-engineering-best-practices.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.