⛏️ Get Splunky!
Lv.1Intern
0 XP
0
Home Map Stats Drill Board Log In
CoursesArticlesSPL Cheat SheetCertification PathAboutPrivacyTerms

Splunky is an independent, free study resource. It is not affiliated with, endorsed by, or sponsored by Splunk or Cisco. Splunk, SPL and related marks are trademarks of Splunk, a Cisco company, and are used here only to identify the certifications this site helps you study for.

© 2026 Splunky

Back to Floor
IR Command • Room 5

Post-Incident Reviews & Detection Feedback Loops

The fourth phase of NIST SP 800-61 — Post-Incident Activity — is where architectural improvements are born. A structured, blameless post-incident review (PIR) examines the timeline of the incident: when the attack began, when telemetry entered Splunk, when a detection fired (MTTD), and when containment completed (MTTR).

For the security architect, every incident is a test of the architecture. Did a missing log source delay investigation? Did a correlation search miss a variant of a technique? Did a SOAR playbook fail because an API token expired? The architect turns PIR findings directly into engineering backlog items: new data onboarding, detection tuning, or SOP updates in Mission Control.

Track "Time to Telemetry" separately from MTTD. If an endpoint buffers logs for 30 minutes before forwarding, even a real-time correlation search has a 30-minute blind window.

Knowledge Check

Prove your understanding to clear the room (Rewards XP)
❤️❤️❤️
Question 1 of 1
After a major incident, a Post-Incident Review reveals that the attacker moved laterally for 6 hours before an alert fired because internal SMB traffic was not logged. What architectural action closes this root cause?
ALower the threshold on existing perimeter firewall rules
BFeed the visibility gap into the data onboarding and sensor placement backlog (e.g., East-West NDR or Windows Security event telemetry) and validate with a Purple Team test
CIncrease the number of Tier 1 analysts on shift
DArchive the incident ticket once systems are restored