Detection engineering is the practice of designing, building, testing and maintaining the rules and analytics that spot attacker activity in security data. It treats detections like software: each one has a purpose, a test, an owner and a version history, instead of being a one-off rule someone wrote years ago.
It is the point where threat intelligence turns into protection. Intelligence describes how attackers operate; detection engineering makes sure the SOC would notice if they did.
Detection-as-code means keeping detection rules in version control, reviewing changes like code and testing them automatically before deployment. Open formats such as Sigma, a vendor-neutral way to write detection rules that can be converted to many SIEM query languages, make detections portable between tools.
Who does detection engineering?
Dedicated detection engineers in larger teams, or senior SOC analysts and threat hunters in smaller ones. It works best in close contact with the CTI team.
How is detection engineering different from threat hunting?
Threat hunting searches for attackers who evaded existing detections. Detection engineering turns what hunters and CTI learn into lasting, automated detections.
Anomali pairs out-of-the-box detections with threat intelligence and ATT&CK mappings, giving detection engineers curated context to build and prioritize detections.
See out-of-the-box detections or request a demo.