Detection engineering is much more than writing signatures. It is the framework that builds, tests, deploys and maintains detections alongside the rest of your infrastructure, so they are managed like any other engineered system.
Built on feedback loops
Detection engineering runs on feedback loops. Every alert outcome, false positive, missed attack, incident and threat hunt carries important information. A mature detection program captures that information and feeds it back, so each detection gets better than the last.
Who it is for
Security engineers, analysts, incident responders, threat hunters and the team leads responsible for detection. Attendees need experience or education beyond junior level.
Format
1 to 5 days, on-site or online, for up to 10 people, built from the modules you choose.
Modules
- Detection engineering as a discipline and a lifecycle
- Deciding what to detect, using threat intelligence and MITRE ATT&CK
- The telemetry and data sources detections depend on
- Writing detections, including YARA, Sigma and behavior-based rules
- Detection as code, with version control, peer review and automated testing
- Deploying and maintaining detections alongside the rest of your infrastructure
- Building feedback loops from alert triage, incidents, threat hunting and testing
- Measuring coverage, detection quality and alert fatigue
What you will be able to do
- Design a detection framework that fits your existing infrastructure
- Take a detection through its whole lifecycle, from idea to retirement
- Build feedback loops that turn alert outcomes and incidents into better detections
- Measure what your detections cover and where the gaps are
Pricing
- Priced per team
- From £1,750 a day for up to 4 people
- From £2,750 a day for up to 10 people1
- Prices exclude VAT
- See pricing for every option
-
Discounts: 15% off for businesses based on the Isle of Man and 10% off for retainer clients, up to 25% combined. Micro businesses with 4 or fewer employees get heavily discounted pricing, so contact us for details. See the terms. ↩︎