Scott Plichta | Splunk .conf2014
summary
Describes a real incident where a malware outbreak that took three days to resolve without Splunk is diagnosed to root cause and contained in three hours using Splunk. Engineers correlate mail, proxy, network and application logs, search an IP and a mail subject across systems, find the phishing vector that hit five people, delete offending messages, block links and restore service with minimal downtime. Argues cloud means no perimeter so dashboards must show patch and exposure status.
AI-written summary · about
