- What a detection should explain: behavior, data, logic, and response
- Map attacker behavior to MITRE ATT&CK without treating every technique as a rule
- Select useful fields and normalize records across log sources
- Read basic SPL and KQL searches; document data assumptions
Practical training · Course outline
Detection Engineering Training
Build, test, and tune detections across identity, endpoint, network, and cloud logs.
Course at a glance
Turn security logs into detections your team can explain, test, and trust.
This is the course outline. Ask us about the next cohort, delivery format, and which training platforms will be available before enrolling.
Build and test the detections security teams rely on.
A focused 35-hour course for analysts ready to move from investigating alerts to building them. Learn to choose the right log sources, write clear detection logic, test it against suspicious and benign examples, and document when a rule should fire. Finish by bringing the workflow together in a reviewable detection pack.
Core focus
Is this training right for you?
Check the background expected before you explore the full curriculum.
Who it’s for
- SOC analysts moving into detection engineering
- Junior detection engineers
- Incident responders who want to build better alerts
What you should know first
- Comfortable investigating common SOC alerts
- Basic understanding of Windows and network logs
- Introductory experience searching in a SIEM
How you’ll practise
- Work through focused detection-design scenarios
- Explain why an alert fired and when it should not
- Review and improve a final detection pack
Skills you’ll practise in this course.
Each outcome is tied to practical investigation or engineering work.
- Identify the telemetry a detection needs before writing a query
- Write and explain SPL or KQL logic against the data available to you
- Map a rule to the attacker behavior it is meant to detect
- Test a rule with malicious and benign examples, then reduce noise
- Document alert context and a sensible investigation path
- Present a detection pack with assumptions, test cases, and gaps
What is detection engineering?
Detection engineering turns suspicious behavior into documented security rules that a SOC can test, tune, and investigate.
Start with the behavior you want to find, check that the required logs exist, then write and validate the rule. Review benign matches so a useful detection does not become a source of unnecessary alerts.
SPL, KQL, Sigma and MITRE ATT&CK
Use Splunk SPL and KQL to express search logic against the available data. Sigma provides a structured detection-rule format, while MITRE ATT&CK helps describe the attacker behavior a rule is meant to detect. Data sources and field mappings still need validation for each environment.
Example: a password-spray detection
Look for one source attempting sign-ins across many accounts. Check the time window and account count, then test against ordinary failed logins and authorized activity. Document why the rule should fire, when it should not, and what an analyst should investigate next.
New to investigating security logs? Explore our SOC analyst training before choosing a course focused on rule design.
Platforms and methods in the syllabus.
Hands-on access to a platform depends on the cohort. Confirm the available environment before enrolling.
What you’ll produce.
Build practical work you can discuss and explain, not just a record of attendance.
- Detection hypotheses and data-source notes
- ATT&CK-mapped rule drafts
- Positive and benign test cases
- Tuning decisions and responder guidance
- Capstone detection pack
Assessment standards
The capstone is designed to test your reasoning and rule quality.
- The rule describes a specific observable behavior
- Required fields and data-source assumptions are documented
- Tests include suspicious and benign examples
- Tuning choices preserve useful coverage
- The response guidance is supported by the evidence
Safe lab conduct
Exercises use sample or explicitly authorized training data.
- Use sample or explicitly authorized training data only
- Never run containment against a real device as part of an exercise
- Treat AI suggestions as drafts that require human validation
- Record assumptions and evidence for every conclusion
Explore the 8 course modules.
Open a module to see its key topics and proposed practice exercise.
Put the lessons into practice.
These are the exercises planned in the course outline. Platform access is confirmed before enrolment.
Course exercises
- Password-spray detection using sample sign-in events
- Suspicious process-chain investigation
- Network beaconing and DNS review
- Cloud privilege-change rule exercise
- Approval-gated response workflow design
- Final detection pack with test cases and tuning notes
Part of the Detection Engineer path.
Specialize in the detection lifecycle: from ATT&CK-driven strategy through SPL and Sigma authoring, correlation rules, tuning, and validation.
The team behind CyberAccend
Across CyberAccend, our curriculum is designed and training delivered by 10+ engineers with professional experience at Microsoft, Cisco, Google and other technology companies.
Mentorship & guidance
Need help with a topic or your next career step?
Use mentorship to work through difficult concepts, plan what to study next, and prepare for interviews.
What to know before you enrol.
Who is this Detection Engineering training for?
The course is designed for SOC analysts, junior detection engineers, and incident responders who already investigate common alerts. You should understand Windows and network logs and have introductory experience searching in a SIEM.
Does the course cover Splunk SPL, KQL and Sigma?
The syllabus includes Splunk Search Processing Language (SPL), Kusto Query Language (KQL), Sigma as a detection-rule format, and MITRE ATT&CK mapping. You work from the telemetry and fields available rather than assuming one query runs unchanged on every platform.
How long is the Detection Engineering course?
The published outline contains eight modules and 35 hours, covering foundations, identity, endpoint, network, cloud, response automation, AI-assisted review, and a detection-engineering capstone.
What practical detection exercises are included?
Planned exercises include a password-spray search, suspicious process-chain analysis, network-beaconing review, a cloud privilege-change rule, and an approval-gated response workflow. The capstone brings rule logic, test cases, tuning decisions, and investigation guidance into a detection pack.
How is detection engineering different from SOC analyst training?
SOC analyst training focuses on investigating alerts and deciding what happened. Detection engineering focuses on deciding which behavior should create an alert, which logs support the rule, how to test it, and how to reduce unnecessary noise. Investigation experience helps you design useful detections.
What should I confirm before enrolling?
This page is a public course outline, not an active learner workspace. Confirm the cohort schedule, delivery format, platform access, fees, and certificate arrangements with CyberAccend before enrolling. Recordings and access to specific lab platforms are not promised by this outline.
Next step
Is Detection Engineering right for you?
Ask about the next cohort, course schedule, and whether your experience is a good fit.