Splunk Certified Cybersecurity Defense Analyst
Splunk Test Blueprint - Cybersecurity Defense Analyst
Overview
The exam and certification are officially documented on Splunk's website. The exam code SPLK-5001 is widely recognized in the industry and community as the identifier for this exam, although Splunk's primary landing page focuses on the descriptive name. The blueprint is available as a PDF from the official domain.
This is independent preparation content. Not affiliated with or endorsed by Splunk or any certification body.
Practice Products for This Certification
Splunk
SPLK-5001
SPLK-5001
Splunk Certified Cybersecurity Defense Analyst# Splunk Certified Cybersecurity Defense Analyst (SPLK-5001) Study Guide ## Domain 1: The Cyber Landscape, Frameworks, and Standards ### SOC Roles and Organization **Explanation:** A Security Operations Center (SOC) is a centralized unit that deals with security issues. Roles are typically tiered: Tier 1 (Analyst) monitors and triages; Tier 2 (Incident Responder) investigates deeply; Tier 3 (Hunter/Architect) handles advanced threats and infrastructure design. **Key Concepts:** - **Analyst:** Focuses on monitoring and initial triage of notable events. - **Engineer:** Maintains the Splunk infrastructure and data ingestion pipelines. - **Architect:** Designs the overall security posture and scaling strategies. ### Cyber Industry Controls and Frameworks **Explanation:** Frameworks provide a common language for security. Splunk integrates these to map alerts to known adversary behaviors. **Key Concepts:** - **MITRE ATT&CK:** A globally-accessible knowledge base of adversary tactics and techniques based on real-world observations. - **NIST Cybersecurity Framework:** Provides a policy framework of computer security guidance (Identify, Protect, Detect, Respond, Recover). - **Splunk Integration:** Splunk Security Essentials (SSE) maps searches directly to MITRE ATT&CK techniques. ## Domain 2: Threat and Attack Types, Motivations, and Tactics ### Attack Vectors and Tactics **Explanation:** Understanding how attackers enter a network (vectors) and what they do once inside (tactics). **Key Concepts:** Phishing, Brute Force, SQL Injection, and Lateral Movement. ### Data Source Assessment **Explanation:** Analysts must know if they have the right data to detect specific threats. **Tools:** - **Splunk Security Essentials (SSE):** Used to perform a Data Inventory and see which MITRE techniques are covered by current data. - **Common Sourcetypes:** `WinEventLog:Security`, `linux_secure`, `cisco:asa`, `stream:http`. ## Domain 4: Investigation, Event Handling, Correlation, and Risk ### Investigation Stages and Monitoring **Explanation:** Splunk defines a structured approach to investigation: 1. Detection, 2. Triage, 3. Investigation, 4. Response, 5. Reporting. **Metrics:** - **MTTR (Mean Time to Respond):** The average time taken to neutralize a threat. - **Dwell Time:** The duration an attacker remains undetected in the environment. ### Risk Based Alerting (RBA) **Explanation:** RBA shifts focus from individual noisy alerts to high-risk entities. Instead of alerting on a single failed login, RBA assigns "Risk Scores" to objects (users/systems). When a threshold is met, a **Risk Notable** is generated. **Key Terms:** - **Risk Object:** The entity (user/system) being tracked. - **Contributing Events:** The individual events that added to the risk score. ## Domain 5: SPL and Efficient Searching ### Security-Focused SPL Commands **Explanation:** Efficient searching is critical for large-scale security data. - **TSTATS:** Extremely fast; searches indexed metadata rather than raw data. Use for high-level summaries. - **REX:** Used for field extraction at search time using regular expressions. - **TRANSACTION:** Groups events together (e.g., a web session), but is resource-intensive. - **EVAL:** Calculates expressions and creates new fields. **Example Query:** `| tstats count from datamodel=Authentication by Authentication.user, Authentication.src` ### Search Best Practices - **Filter Early:** Use specific indexes and sourcetypes at the beginning of the search. - **Avoid Wildcards at the Start:** `*error` is slower than `error*`. - **Use Data Models:** Leverage Accelerated Data Models for faster reporting in ES. ## Domain 6: Threat Hunting and Remediation ### Threat Hunting Techniques **Explanation:** Proactive searching for threats that evaded existing security controls. - **Long Tail Analysis:** Looking for rare events (e.g., a process that only ran once across 10,000 machines). - **Outlier Detection:** Using commands like `anomalydetection` to find statistical deviations. ### SOAR and Adaptive Response **Explanation:** Splunk SOAR (formerly Phantom) automates response actions. - **Adaptive Response Actions:** Actions triggered from a correlation search (e.g., pinging a host, adding an IP to a blocklist, or running a SOAR playbook). - **Playbooks:** Automated workflows that execute security tasks at machine speed.