Splunk Detection and Incident Response

Detect and Investigate Attacks in Splunk

Write the SPL that turns Splunk's data into detections and an investigation: scope and shape searches, accelerate them with tstats over CIM data models, hunt across identity, endpoint, network, and cloud, and run an incident end to end. Every search runs on the page against the Northgate Engineering corpus, with no Splunk license and no instance to stand up.

Included with Premium, from $19.99/month, or $179/year and save 25%. Preview the first module free, no account needed.
Practice included: graded Splunk drills, plus the Practice Hub.
View Pricing Take End of Course Exam → 40 CPE Credits

What you'll be able to do

Scope and shape searches so they stay fast: indexes, sourcetypes, the search pipeline, and the search-time cost model
Normalize across sources with the Common Information Model and query whole categories through data models
Accelerate detection at scale with tstats, and write detections with eventstats, streamstats, transaction, and subsearches
Engineer tuned detections with defensible thresholds, lookup-driven allowlisting, and systematic false-positive reduction
Hunt and correlate across identity, endpoint, network, web, DNS, and cloud sources in a single investigation
Triage a lead, scope the blast radius, reconstruct a timeline, preserve evidence, and write a defensible incident report
SEC405 | Premium tier | 11 modules across 6 phases | 36–40 hours at your own pace | 40 CPE credits | Free preview, no account needed

Course Syllabus

Every module and every lesson. Open a module to see its lessons.

Download the full syllabus (PDF)

Phase 1: Foundations

SPL0
Course OrientationCourse Preview

What Splunk Detection and Incident Response teaches: write tstats-accelerated detections over CIM data models, hunt across identity, endpoint, network, and cloud, and run an incident end to end from the search bar.

7 lessonsHide lessons
  1. SPL0.1 Purpose and ScopePreview
  2. SPL0.2 Getting the Most From This CoursePreview
  3. SPL0.3 The SIEM Is the Whole Estate in One PlacePreview
  4. SPL0.4 An Attack Is a Trail Across SourcesPreview
  5. SPL0.5 Detection Is Signal Against NoisePreview
  6. SPL0.6 The NE Environment and Its EvidencePreview
  7. SPL0.7 The On-Page Toolkit and SetupPreview
SPL1
The Splunk Detection and IR Landscape

How Splunk stores and retrieves data, search-time versus index-time, the Common Information Model, where NE's evidence lives, and your first detection-grade searches against the corpus.

10 lessonsHide lessons
  1. SPL1.1 Indexes and Search Scoping
  2. SPL1.2 Sourcetypes and Fields
  3. SPL1.3 The Search Pipeline
  4. SPL1.4 Search-Time versus Index-Time
  5. SPL1.5 Shaping Results
  6. SPL1.6 The Common Information Model
  7. SPL1.7 Data Models
  8. SPL1.8 Knowing NE's Data
  9. SPL1.9 Your First Detection-Grade Searches
  10. SPL1.10 Module Summary

Phase 2: The Splunk Analysis Surface

SPL2
Data Models, CIM, and tstats

The accelerated-search backbone: how CIM data models normalize NE's sources, how tstats reads the acceleration summary to search millions of events in moments, and how to point it at the Authentication, Endpoint...

10 lessonsHide lessons
  1. SPL2.1 Why Raw Search Doesn't Scale
  2. SPL2.2 The Anatomy of tstats
  3. SPL2.3 The CIM Data Models in NE
  4. SPL2.4 tstats over Authentication
  5. SPL2.5 tstats over Endpoint
  6. SPL2.6 tstats over the Network and Web Models
  7. SPL2.7 tstats over Change and Email
  8. SPL2.8 From Acceleration to Detection
  9. SPL2.9 When tstats Can't See It
  10. SPL2.10 Module Summary

Phase 3: Detection Engineering

SPL4
Detection Engineering in Splunk

The lifecycle and discipline that turns a search into a production detection: hypothesis to correlation search, calibrating thresholds from data, false-positive reduction, suppression and scheduling, testing, and...

8 lessonsHide lessons
  1. SPL4.1 Search, Alert, Detection
  2. SPL4.2 From Hypothesis to Correlation Search
  3. SPL4.3 Calibrating Thresholds From Data
  4. SPL4.4 Precision and False-Positive Reduction
  5. SPL4.5 Suppression, Throttling, and Scheduling
  6. SPL4.6 Testing a Detection
  7. SPL4.7 Detection-as-Code and the Lifecycle
  8. SPL4.8 Module Summary
SPL6
Endpoint Attack Detection

Detecting the endpoint-compromise chain on the Endpoint data model and Sysmon: process ancestry, encoded execution, LOLBins, credential theft, persistence, lateral movement, and host-based C2, engineered against NE's...

11 lessonsHide lessons
  1. SPL6.1 The Endpoint Attack Surface
  2. SPL6.2 Baselining Endpoint Activity
  3. SPL6.3 Process Ancestry: the Anomalous Parent
  4. SPL6.4 Command-Line Analysis
  5. SPL6.5 LOLBins and Living Off the Land
  6. SPL6.6 Credential Theft
  7. SPL6.7 Persistence
  8. SPL6.8 Lateral Movement
  9. SPL6.9 Endpoint C2 and Network Activity
  10. SPL6.10 Correlating the Endpoint Kill Chain
  11. SPL6.11 Module Summary

Phase 4: Hunting and Correlation

SPL8
Threat Hunting

The proactive search for the intrusion no rule caught: hypothesis-driven hunting, tstats over accelerated data models for whole-estate speed, and the cloud as a hunting surface, working a real AWS account compromise...

8 lessonsHide lessons
  1. SPL8.1 What Threat Hunting Is
  2. SPL8.2 Hunting at Scale with tstats
  3. SPL8.3 The Cloud Attack Surface
  4. SPL8.4 Hunting Cloud Reconnaissance
  5. SPL8.5 Hunting Credential Access and Defense Evasion
  6. SPL8.6 Following an Actor Across Sources
  7. SPL8.7 From a Hunt to a Detection
  8. SPL8.8 Module Summary

Phase 5: Incident Response

SPL9
Triage and Scoping

The incident-response entry point in Splunk: triage a queue to the one lead that matters, validate it against independent telemetry, scope the blast radius across identity, endpoint, network, and cloud, reconstruct...

8 lessonsHide lessons
  1. SPL9.1 The Incident Response Entry Point
  2. SPL9.2 Triaging the Queue
  3. SPL9.3 Validating the Lead
  4. SPL9.4 Scoping the Blast Radius
  5. SPL9.5 Session Reconstruction with transaction
  6. SPL9.6 Building the Incident Timeline
  7. SPL9.7 From a Lead to a Scoped Incident
  8. SPL9.8 Module Summary
SPL11
Incident Response, Evidence, and Reporting

The Splunk-driven incident response workflow after the investigation: preserve search-derived evidence, derive the remediation picture, contain and evict the attacker across identity, endpoint, network, and cloud...

9 lessonsHide lessons
  1. SPL11.1 From Timeline to Response
  2. SPL11.2 Preserving Evidence From Search
  3. SPL11.3 Deriving the Remediation Picture
  4. SPL11.4 Containing and Evicting Identity
  5. SPL11.5 Containing and Evicting Endpoint and Network
  6. SPL11.6 Validating the Eviction
  7. SPL11.7 Writing the Incident Report
  8. SPL11.8 Detection as Code
  9. SPL11.9 Module Summary

Phase 6: Capstone

SPL12
Capstone: Full-Chain Incident in Splunk

The capstone: applying the whole course method to a fresh edge-to-identity intrusion, from a single alert on an internet-facing host through triage, reconstruction of the entry and the pivot inward, correlation and a...

8 lessonsHide lessons
  1. SPL12.1 The Capstone Brief
  2. SPL12.2 Triage and Scope the Lead
  3. SPL12.3 Reconstructing the Entry
  4. SPL12.4 Reconstructing the Pivot Inward
  5. SPL12.5 Correlating and the Master Timeline
  6. SPL12.6 The Objective and the Response
  7. SPL12.7 The Capstone Report and Debrief
  8. SPL12.8 Module Summary

Phase 0: Course Resources

SPL90
Cheatsheets

SPL by investigation area, each search with the fields that carry the decision and what the result does not establish.

10 lessonsHide lessons
  1. Search Patterns
  2. Data Models and CIM
  3. The Compute Layer
  4. Identity Detections
  5. Endpoint Detections
  6. Network, Web and DNS
  7. Threat Hunting
  8. Triage and Scoping
  9. Response and Reporting
  10. The Engine and the Estate
SPL91
Cookbooks

Ordered procedures for the situations that recur: validating a lead, scoping an identity, building a timeline, tuning a noisy detection and proving an eviction.

7 lessonsHide lessons
  1. Validating a Password Spray Lead
  2. Scoping a Compromised Identity
  3. Confirming a Beacon
  4. Tuning a Detection That Fires Too Often
  5. Investigating a Suspicious Execution
  6. Building a Cross-Source Timeline
  7. Proving an Eviction Held
SPL92
Lab Setup

Building a Splunk instance that runs this course's searches, with the license decision that determines which modules you can actually practice in it.

5 lessonsHide lessons
  1. The License Decision, and Why It Comes First
  2. Installing, and the First Ten Minutes
  3. Getting Data In
  4. CIM and Data Model Acceleration
  5. Verify It Works, and What It Cannot Show You
SPL93
Walkthroughs

Six worked investigations against the course corpus, each ending in a written finding with its confidence stated and its gaps named.

6 lessonsHide lessons
  1. The Nineteen That Were Really One
  2. The Host That Resolved Everything
  3. The Host We Could Not Put on the Network
  4. The Account That Stopped Being the Subject
  5. Twenty-Four Minutes on One Laptop
  6. Four Events and a Month
SPL94
Playbooks

Seven playbooks keyed to what actually fires, each with a pre-flight, a sequence, escalation tiers and the false positives that live in that domain.

7 lessonsHide lessons
  1. A Surge of Failed Authentications
  2. A Host Talking on a Schedule
  3. A Process That Should Not Have Run
  4. An Identity Gained Rights It Did Not Have
  5. A Large Amount of Data Left
  6. A Source Stopped Reporting
  7. A Detection Nobody Can Work
SPL95
Playground

Where to practice SPL and use it at work: the drills, the corpus, your own instance, the detection library, and the reference pages worth keeping open.

SPL97
References & Further Reading

Splunk documentation, the Common Information Model, MITRE ATT&CK, Splunk Security Content, NIST SP 800-61 Rev 3, and the threat-intelligence and methodology sources used throughout the Splunk Detection and Incident...

Course Completion

Course Exam

Splunk Detection and Incident Response end-of-course exam: a simulation-based assessment testing your ability to triage, investigate, and respond to a Splunk-detected intrusion you have not seen before, using the...

1 lessonsHide lessons
  1. Course Completion. Splunk Detection and Incident Response

Course overview

Splunk Detection and Incident Response teaches you to detect and investigate attacks using SPL, the Search Processing Language, the way a working detection engineer and incident responder uses it. You learn how Splunk stores and retrieves data, how to write searches that stay fast as the data grows, how to normalize across sources with the Common Information Model, and how to accelerate detection at scale with tstats over data models. From there the course moves into building tuned detections, hunting across the estate, and running an incident from first lead to final report.

Every module works against the same fictional company, Northgate Engineering, and its real attack chains: password spray, adversary-in-the-middle token replay, endpoint compromise, ransomware pre-encryption, and a hybrid pivot to cloud. The course runs against a prepared corpus with a live SPL engine on the page, so you write and run real searches against real evidence with nothing to install, no Splunk license, and no instance of your own.

This is a course in the SPL search and detection craft, not a tour of the Splunk product. It does not cover building dashboards or visualizations, configuring alerts, onboarding data, or Splunk administration. It is what a detection engineer and incident responder does in the search bar, against data that is already there.

How this course works

Splunk rewards knowing where the data model ends and raw search begins. This course runs the same loop for every detection and every investigation it works.

1. Search the model, not the index, where you can. tstats against an accelerated data model is orders of magnitude faster than the equivalent raw search, and the difference decides whether a detection runs at all.

2. Normalize before you correlate. CIM exists so a detection written once works across sourcetypes. A search built on raw field names works until somebody onboards a new log source.

3. Write the detection against the behavior. The technique's requirement rather than the tool's name, the same discipline that survives an attacker changing their kit.

4. Scope before you conclude. A hit is one entity. The investigation is the others, and Splunk's job in an incident is turning one alert into a bounded population.

5. Reconstruct the timeline from the events you can defend. With the source and the search that produced each one recorded alongside it.

The course closes on a full-chain incident worked entirely in Splunk.

What this course assumes

No minimum experience and no prerequisite course. SPL, data models, CIM and the search head model are built up from the first search.

What makes it go faster: a Splunk instance with data in it. Not required, because every search in the course runs against a corpus the course provides.

What this course does not cover: Splunk administration, index design and infrastructure. This is detection and incident response by somebody who searches Splunk rather than runs it.

Who this course is for

This is an intermediate-to-advanced course. It assumes you can already write basic SPL, a filtered search, a stats aggregation, a simple eval, and builds from there to tstats, data models, advanced commands, and full investigations. Every advanced concept is explained at first use, so you do not need prior detection-engineering experience in Splunk, but you will move fastest if SPL is not brand new to you.

SOC analysts and engineers who can search Splunk but want to build detections that scale
Detection engineers moving from ad-hoc searches to tstats-accelerated rules over CIM data models
Incident responders who need to scope and reconstruct an intrusion across sources in Splunk
Threat hunters who want a repeatable, cross-source method rather than one-off queries

What you'll learn

Scope and shape searches so they stay fast: indexes, sourcetypes, the search pipeline, and the search-time cost model
Normalize across sources with the Common Information Model and query whole categories through data models
Accelerate detection at scale with tstats, and write detections with eventstats, streamstats, transaction, and subsearches
Engineer tuned detections with defensible thresholds, lookup-driven allowlisting, and systematic false-positive reduction
Hunt and correlate across identity, endpoint, network, web, DNS, and cloud sources in a single investigation
Triage a lead, scope blast radius, reconstruct a timeline, preserve evidence, and write a defensible incident report

Key course takeaways

A working library of SPL detections you can adapt to your own Splunk environment
The judgment to set a threshold from the data's distribution rather than a guessed round number
A repeatable method for hunting and correlating across sources rather than searching one at a time
The discipline to separate what the evidence proves from what it only suggests
A Splunk-driven incident response workflow, from triage through containment to a report you can hand over

Things you need to know

What are the prerequisites?

Comfort with basic SPL: a filtered search, a stats aggregation, a simple eval. This is an intermediate-to-advanced course pitched above the beginner material Splunk and others cover well, and it builds from those basics to tstats, data models, the advanced command surface, and full investigations. Every advanced concept is explained at first use, so you do not need prior Splunk detection-engineering experience, only a working familiarity with searching.

What tools does this course use?

SPL throughout, including tstats over accelerated CIM data models, the advanced command surface (eventstats, streamstats, transaction, subsearches, lookups, rex, and spath), and the patterns behind detection-as-correlation-search. The evidence spans identity, endpoint, network, web, DNS, and cloud sources, normalized through the Common Information Model. The course frames detections against MITRE ATT&CK and follows the NIST SP 800-61 incident response method.

Do I need a Splunk license or an instance?

No. Every search runs on the page against a prepared corpus through a built-in SPL engine, so the full method works with nothing to install, no license, and no instance of your own. You write real SPL and get real results against embedded attack chains, and the SPL Lab and Query Practice surfaces give you free-run space to test your own searches against the same data.

How will this course benefit your career?

Splunk is one of the most widely deployed SIEMs, and organizations need people who can do more than search it: who can build detections that scale, tune them so analysts trust them, and drive an investigation from a single lead to a defensible report. That cybersecurity professional capability is in short supply, because most Splunk training teaches the product and the certifications rather than the defender's job against a live adversary. This course builds the detection-and-response capability end to end.

Usage rights and disclaimer

Course materials: Licensed for individual professional development. You may adapt the detection logic, searches, and runbooks for use in your own production environment. You may not redistribute course content or share account credentials.

Fictional environment: All scenarios use Northgate Engineering (NE) and its Splunk estate. Hosts, accounts, addresses, and identities are fictional. Any resemblance to real organizations is coincidental.

COURSE ASSESSMENT

End of Course Exam

Complete the course, then prove your skills under time pressure. Pass mark: 70. Earn your certificate with CPE credits.

40minutes
3phases
100points
1scenario
Take End of Course Exam

One random scenario per attempt. Certificate issued on pass.