# A Primer to Detection Engineering Dimensions in a SOC Universe

## Introduction

During my three years in cybersecurity, I have been lucky enough, as an analyst, to work on several vectors inside the SOC pipelines, from alert triage and DFIR engagement to SIEM engineering and detection development which allowed me to experience first hand different challenges that we face on a daily basis.

Detection engineering is now considered one of the most important operations inside a SOC, MSSP or an MDR. In this article I will try to present detection engineering dimensions from my personal point of view of a SOC analyst. 

## TL;DR

Here is a Mind Map where I tried to group the main ideas of these blog posts. For further details, please follow along.

* [**Dimension 1** : Operationalization](https://www.unh4ck.com/detection-engineering-dimensions/operationalization)
* [**Dimension 2** : Execution](https://www.unh4ck.com/detection-engineering-dimensions/execution)
* [**Dimension 3** : Analytics](https://www.unh4ck.com/detection-engineering-dimensions/logic)

![Detection Engineering Dimensions](/files/-Ml1JqerZWrtL1706GQE)


---

# Agent Instructions: 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:

```
GET https://www.unh4ck.com/detection-engineering-dimensions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.