A Research-Driven process applied to Threat Detection Engineering Inputs | by Alex Teixeira | Detect FYI

This article is an evolution of a previous one I wrote on Jira Workflows for Detection Engineering teams but more focused on the detection inputs and with the introduction of a new actor: the Detection Researcher. The diagram below is the result of many, many hours working on building and executing ideas around the detection engineering practice for enterprise organizations as part of my work. The idea here is to expose an overall, high-level process while enabling you to pick and choose the boxes according to your team's capabilities, and later draw and refine your own, detailed workflows. This should be applicable to both enterprise and product (vendor) teams. C oncept is where a detection idea is initially discussed. There's no clear understanding or rationale around its value or feasibility yet. Here's where all the drivers and inputs for an idea come from. While some of those blue boxes are self-explanatory, here are a few worth highlighting just to make sure you get the idea: Thr

saved by

• Cooper Edmunds