> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/detection-strategy-guides/d-m/extrahop/extrahop-reveal-x-enterprise-detection-strategy.md).

# ExtraHop Reveal(x) Enterprise Detection Strategy

## Product Overview <a href="#h_01k0styvrhch08jt7a0pbdyyqg" id="h_01k0styvrhch08jt7a0pbdyyqg"></a>

ExtraHop Reveal(x) Enterprise is a network detection and response (NDR) platform that provides complete visibility, real-time detection, and intelligent response across hybrid and multi-cloud environments. By analyzing network traffic in real-time, Reveal(x) Enterprise decrypts and analyzes all network communications to identify suspicious behaviors and potential threats that other security tools may miss. The platform uses machine learning to baseline normal network activity and automatically detect anomalies, from initial intrusion attempts to lateral movement and data exfiltration. Reveal(x) Enterprise delivers high-fidelity insights and enables security teams to investigate incidents with full context and perform guided investigations, helping to accelerate threat resolution and reduce risk across the enterprise.

## Detection Strategy for Network Integrations <a href="#h_01jykxhz9hve4ay4cmf447f1wt" id="h_01jykxhz9hve4ay4cmf447f1wt"></a>

### Detection <a href="#h_01jykxhz9hr1rr5f4cvj1er5pg" id="h_01jykxhz9hr1rr5f4cvj1er5pg"></a>

Network traffic monitoring is a critical element of our detection strategy, offering insight into the activity of data as it moves across an organization's systems. The network traffic data source focuses on network connection creation (the initial construction of a network connection such as socket information, and src and dst IP and Ports ), network traffic content (logged network traffic data showing both protocol header and body values like PCAP), and network traffic flow (summarized network packet data, with metrics, such as protocol headers and volume like netflow or http logs).

We pull this information into our detection pipeline as events in the form of both security alerts and raw telemetry (depending on the integration). When a threat is detected, our automated response bot, Ruxie, takes action by enriching evidence fields with first- and third-party threat intelligence. Additional Ruxie actions query a wide span of technologies directly to arm analysts with key pieces of investigative information and related events.

### Response <a href="#h_01jykxhz9h7fgy8dscq2hh398z" id="h_01jykxhz9h7fgy8dscq2hh398z"></a>

Network technologies are utilized for support across many types of Expel Alerts such as endpoint and cloud. The main focus of the response strategy is on source IP, destination IP, and domain tracking to identify related connections, along with user activity summaries to give extra alert context.

To learn more about our overall approach to detection strategy, see [About Detection Strategy](/workbench-reference/detections/about-detection-strategy.md).

## What We Support for ExtraHop Reveal(x) Enterprise <a href="#h_01jz8v747tzqx1xgybg3d9hsh8" id="h_01jz8v747tzqx1xgybg3d9hsh8"></a>

To see a comprehensive list of the most up-to-date Expel detection rules, vendor detection rules, opt-in detections, and available DUETs (**d**id yo**u** **e**xpect **t**his) that we support for ExtraHop Reveal(x) Enterprise, you can visit the [Detections page](https://workbench.expel.io/tools/detections/all?filter=%7B%22supportedTech%22%3A%7B%22is%22%3A%5B%22extrahop%3A1.0.0%22%5D%7D%7D) in Workbench or ask your Sales or Support rep for the most recent download.

| **Supported versions**                                    | <ul><li> All versions</li></ul>                                         |
| --------------------------------------------------------- | ----------------------------------------------------------------------- |
| **Supported event log sources**                           | <ul><li>Alerts</li></ul>                                                |
| **ExtraHop Reveal(x) Enterprise detection rules support** | Yes.                                                                    |
| **Detection rules written by Expel**                      | Yes.                                                                    |
| **Auto remediations**                                     | No.                                                                     |
| **Investigative support through Workbench**               | No. We access the console directly with an "Investigator" role account. |
| **Hunting support**                                       | No. Hunting is not currently available for this integration.            |

## Additional Details and Common Questions <a href="#h_01jz8vcc9emyq2tekbvqfpcvtz" id="h_01jz8vcc9emyq2tekbvqfpcvtz"></a>

### Console Access <a href="#h_01jz8vchf4mkrs8mc1nypatgq2" id="h_01jz8vchf4mkrs8mc1nypatgq2"></a>

A vendor alert does not typically include all of the contextual timeline activity surrounding the event of interest. Because this integration does not allow us to get all necessary data via the API, we will ask you for a certain level of console access during onboarding.

The level of access that we require is meant to support essential triage and research activities, and to help us determine the vector and extent of attacker activity for an identified threat. At minimum, we will ask for visibility into alert data, timeline events recorded, and live response/real time response shell (if applicable).

### DUET <a href="#h_01jz8vcm88vz1vqncfjj81acz4" id="h_01jz8vcm88vz1vqncfjj81acz4"></a>

A DUET rule flags certain events as needing an immediate verification or notification, and bypasses the normal internal event triage process. The events subject to DUET rules contain behaviors that are not typically indicative of true security incidents, as they are related to policy violations or potential risk.

There are a number of workflows that a DUET may follow. When enabled, the activity will be flagged for investigation and will be routed to you (rather than to us) to take a specified first action. To see the specific DUET rules currently supported for this integration, visit the [Detections page](https://workbench.expel.io/tools/detections/all) in Workbench.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.expel.io/detection-strategy-guides/d-m/extrahop/extrahop-reveal-x-enterprise-detection-strategy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.