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.
What you'll be able to do
Course Syllabus
Every module and every lesson. Open a module to see its lessons.
Download the full syllabus (PDF)
Phase 1: Foundations
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
- SPL0.1 Purpose and ScopePreview
- SPL0.2 Getting the Most From This CoursePreview
- SPL0.3 The SIEM Is the Whole Estate in One PlacePreview
- SPL0.4 An Attack Is a Trail Across SourcesPreview
- SPL0.5 Detection Is Signal Against NoisePreview
- SPL0.6 The NE Environment and Its EvidencePreview
- SPL0.7 The On-Page Toolkit and SetupPreview
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
Phase 2: The Splunk Analysis Surface
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
- SPL2.1 Why Raw Search Doesn't Scale
- SPL2.2 The Anatomy of tstats
- SPL2.3 The CIM Data Models in NE
- SPL2.4 tstats over Authentication
- SPL2.5 tstats over Endpoint
- SPL2.6 tstats over the Network and Web Models
- SPL2.7 tstats over Change and Email
- SPL2.8 From Acceleration to Detection
- SPL2.9 When tstats Can't See It
- SPL2.10 Module Summary
The compute layer: eventstats and streamstats for baselining, bin for time shape, transaction for session reconstruction, subsearch and join for correlation, lookup for enrichment and allowlisting, and rex for...
9 lessonsHide lessons
- SPL3.1 eventstats: Comparing to a Baseline
- SPL3.2 streamstats and bin: Detection Over Time
- SPL3.3 transaction: Reconstructing a Session
- SPL3.4 subsearch and join: One Search Feeding Another
- SPL3.5 lookup: Enrichment
- SPL3.6 lookup: Threat Intel and Allowlisting
- SPL3.7 rex and spath: Extracting What the Model Doesn't Give
- SPL3.8 Composing the Compute Layer
- SPL3.9 Module Summary
Phase 3: Detection Engineering
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
- SPL4.1 Search, Alert, Detection
- SPL4.2 From Hypothesis to Correlation Search
- SPL4.3 Calibrating Thresholds From Data
- SPL4.4 Precision and False-Positive Reduction
- SPL4.5 Suppression, Throttling, and Scheduling
- SPL4.6 Testing a Detection
- SPL4.7 Detection-as-Code and the Lifecycle
- SPL4.8 Module Summary
Detecting the identity attacks that dominate cloud intrusions, on the Authentication model: password spray, MFA gaps, risky sign-ins, impossible travel, adversary-in-the-middle token replay, and OAuth persistence...
11 lessonsHide lessons
- SPL5.1 The Identity Attack Surface
- SPL5.2 Baselining an Identity
- SPL5.3 Detecting Password Spray
- SPL5.4 MFA Gaps and Weak Authentication
- SPL5.5 Risky Sign-Ins and the Risk Signal
- SPL5.6 Impossible Travel
- SPL5.7 Adversary-in-the-Middle Token Replay
- SPL5.8 Token Replay in the Non-Interactive Logs
- SPL5.9 Anomalous Service Principals and OAuth Persistence
- SPL5.10 Correlating the Identity Kill Chain
- SPL5.11 Module Summary
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
- SPL6.1 The Endpoint Attack Surface
- SPL6.2 Baselining Endpoint Activity
- SPL6.3 Process Ancestry: the Anomalous Parent
- SPL6.4 Command-Line Analysis
- SPL6.5 LOLBins and Living Off the Land
- SPL6.6 Credential Theft
- SPL6.7 Persistence
- SPL6.8 Lateral Movement
- SPL6.9 Endpoint C2 and Network Activity
- SPL6.10 Correlating the Endpoint Kill Chain
- SPL6.11 Module Summary
Phase 4: Hunting and Correlation
Detecting an intrusion in the traffic that leaves the estate: beacon cadence and shape in proxy logs, exfiltration by volume, DNS as a covert channel, threat-intel and CIDR matching at the egress, and the perimeter...
10 lessonsHide lessons
- SPL7.1 The Network, Web, and DNS Attack Surface
- SPL7.2 Baselining Egress Traffic
- SPL7.3 Detecting Beaconing
- SPL7.4 C2 Over Web: Shape Beyond Cadence
- SPL7.5 Exfiltration by Volume
- SPL7.6 DNS as a Covert Channel
- SPL7.7 Threat Intelligence at the Egress
- SPL7.8 The Perimeter View: Firewall and Denied Traffic
- SPL7.9 Correlating the Network View into the Kill Chain
- SPL7.10 Module Summary
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
Phase 5: Incident Response
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...
Full multi-source incident reconstruction in Splunk: work backward to initial access, reconstruct the identity, endpoint, network, and cloud stages each in depth, correlate them into one chain, and assemble a...
10 lessonsHide lessons
- SPL10.1 From Skeleton to Defensible Timeline
- SPL10.2 Working Backward to Initial Access
- SPL10.3 The Identity Foothold and Its Expansion
- SPL10.4 Reconstructing the Endpoint Stage
- SPL10.5 Correlating Endpoint to Network
- SPL10.6 Reconstructing the Cloud Stage
- SPL10.7 Correlating the Chain Across Planes
- SPL10.8 Building the Master Timeline
- SPL10.9 The Objective and the Narrative
- SPL10.10 Module Summary
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
- SPL11.1 From Timeline to Response
- SPL11.2 Preserving Evidence From Search
- SPL11.3 Deriving the Remediation Picture
- SPL11.4 Containing and Evicting Identity
- SPL11.5 Containing and Evicting Endpoint and Network
- SPL11.6 Validating the Eviction
- SPL11.7 Writing the Incident Report
- SPL11.8 Detection as Code
- SPL11.9 Module Summary
Phase 6: Capstone
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
Phase 0: Course Resources
SPL by investigation area, each search with the fields that carry the decision and what the result does not establish.
Ordered procedures for the situations that recur: validating a lead, scoping an identity, building a timeline, tuning a noisy detection and proving an eviction.
Building a Splunk instance that runs this course's searches, with the license decision that determines which modules you can actually practice in it.
Six worked investigations against the course corpus, each ending in a written finding with its confidence stated and its gaps named.
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.
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.
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
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
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.
What you'll learn
Key course takeaways
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.
End of Course Exam
Complete the course, then prove your skills under time pressure. Pass mark: 70. Earn your certificate with CPE credits.
One random scenario per attempt. Certificate issued on pass.