> For the complete documentation index, see [llms.txt](https://darkcybe.gitbook.io/holocron/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://darkcybe.gitbook.io/holocron/detect/detect.md). # Detection Engineering & Hunting Detection engineering and hunting with explicit telemetry, hypotheses and test boundaries. `DETECT // DEFINE THE SIGNAL` A detection article should explain the behaviour it is looking for, the data it needs and how its result was assessed. This section covers detection logic, telemetry design and threat hunting with those questions kept together. ## Write the hypothesis first Describe the behaviour in plain language before choosing a query language. Then name the event sources, fields and collection assumptions required to observe it. Keep the analytical idea separate from the syntax used by a particular platform. A useful review asks: * What should match, and what similar legitimate activity should not? * Which missing fields, collection gaps or environment differences would change the result? * What evidence supports the claimed coverage, and what remains untested? * What should an analyst examine after a match? Hunts belong here when they have a question, a search method and an account of the result, including inconclusive results. A quiet query is not a complete investigation narrative. ## Connect the signal to a decision [Investigate](/holocron/investigate/investigate.md) provides the evidence context behind a hypothesis. [Build](/holocron/build/build.md) covers the lab and instrumentation needed to exercise it. Durable field and query explanations belong in [Reference](/holocron/reference/reference.md). --- # 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://darkcybe.gitbook.io/holocron/detect/detect.md?ask=&goal= ``` `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.