> 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/logz.io-detection-strategy.md).

# Logz.io Detection Strategy

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

Logz.io is a cloud-native observability platform that helps businesses monitor and secure their applications and infrastructure. It combines open-source tools like the ELK Stack (Elastic Security, Logstash, and Kibana) and Grafana to provide a unified platform for log management, metrics monitoring, tracing, and security analytics.

## Detection Strategy for SIEM Integrations <a href="#h_01jz10bx2t3gxg7q73c4web8m7" id="h_01jz10bx2t3gxg7q73c4web8m7"></a>

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

SIEM technology provides us with a helpful detection "backstop" for event telemetry. The detections are not authored by us, so how we ingest and action on the SIEM's alerts depends on the SIEM's category.

This SIEM integration is categorized as **investigative-only**. This means no alerts from the SIEM are ingested, but the SIEM can still be used by us for investigation telemetry. Therefore we strongly recommend you set up this integration in Workbench to increase the available investigative support.

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

SIEM telemetry provides additional information that can be useful for us to disposition alerts. With the exception of investigative-only SIEMs, we will follow our normal event triage process and create an Expel Alert that is sent to our SOC analysts for analysis. We may also run queries against your SIEM logs to search for additional types of data, which we use to enrich our alerts with additional context.

## What We Support for Logz.io <a href="#h_01jz10bx2t7t0s54hwjfewqm48" id="h_01jz10bx2t7t0s54hwjfewqm48"></a>

To see a comprehensive list of the most up-to-date SIEM rules and available DUETs that we support for Logz.io, ask your Sales or Support rep for the most recent download (not all SIEM rules are visible on the [Detections page](https://workbench.expel.io/tools/detections/all) in Workbench).

| **Logz.io detection rules support**         | No, this SIEM integration is categorized as investigative-only.     |
| ------------------------------------------- | ------------------------------------------------------------------- |
| **Detection rules written by Expel**        | No. Expel does not write any detection rules for SIEM integrations. |
| **Investigative support through Workbench** | Yes.                                                                |
| **Hunting support**                         | No. Hunting is not currently available for this integration.        |

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

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

A SIEM 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. Granting it is optional, but is strongly recommended.

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).

### Historic Volume <a href="#h_01jz10bx2tv652j3sg0besjakx" id="h_01jz10bx2tv652j3sg0besjakx"></a>

We use historic volume to determine projected SIEM alert volume, which helps us decide whether or not a particular detection is appropriate to send to our SOC. We target 30 days as the ideal period of time to check on volume, and two weeks as the minimum. This gives us the confidence we need to properly evaluate incoming SIEM alerts in a way that does not flood the SOC with benign activity.

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

A DUET (**d**id yo**u** **e**xpect **t**his) rule flags certain SIEM alerts as needing an immediate verification or notification, and bypasses the normal internal event triage process. The alerts 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.&#x20;

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/logz.io-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.