🔏
RootGuard
HomeSOC OperationsIncident ResponseWindows ForensicsLinux ForensicsKQL Investigations
  • Welcome
    • RootGuard
      • Who Am I?
        • Professional Profile
  • Resources Hub
    • Blogs
      • Articles
        • Safeguarding SMEs: The Strategic Importance of a Security Operations Center (SOC)
      • Posts
        • Roadmap to Becoming a Cybersecurity Specialist
        • Starting a Career in Cybersecurity
        • A Guide to Landing Your First Cybersecurity Analyst Role
        • Moving from Intermediate to Expert Incident Responder
  • SOC Operations
    • Introduction
      • Development Resources
        • SOC Analysts Roadmap
        • Becoming A SOC Analyst
        • SOC Analysts Prep Interview Questions
    • Essential Skills
      • Critical Windows EventIDs to Monitor
    • Junior Analyst Skills
      • Splunk Use Cases
      • KQL Use Cases
        • Reconnaissance (TA0043)
        • Initial Access (TA0001)
        • Execution (TA0002)
        • Persistence (TA0003)
        • Privilege Escalation (TA0004)
        • Defence Evasion (TA0005)
        • Credential Access (TA0006)
        • Discovery (TA0007)
        • Lateral Movement (TA0008)
        • Collection (TA0009)
        • Command and Control (TA0011)
        • Exfiltration (TA0010)
        • Impact (TA0040)
      • Investigating Common Attacks
        • Domain Dominance Attacks - Detection & Analysis
        • Investigating a Suspected AD FS Distributed Key Management (DKM) Attack
        • Authentication From Suspicious DeviceName
        • Identifying Interactive or RemoteInteractive Session From Service Account
        • Identifying Split or Part Archive File Transfers
        • Detect Potential Cleartext Credentials in Command Line
        • Detecting Command Line Interpreters Launched via Scheduled Tasks
        • Detecting Files Containing Potentially Sensitive Data
        • Detecting DeviceNetworkEvents From Windows Processes and Domains by TLD
        • Detecting Silent cmd.exe Execution With Redirected STDERR & STDOUT
        • Detecting Low Prevalence DLL Loaded From Process In User Downloads Directory
        • Detecting Virtual Drive Mounted From Archive
        • Identify Execution of Script From User's Downloads Folder
        • Identify Potential RDP Tunneled Sessions
        • Identify Instances of PowerShell Invoke-WebRequest, IWR or Net.WebClient
        • Identify Processes Launched by PowerShell Remoting (WSMProvHost.exe)
        • Detect DeviceNetworkEvents for LOLBAS with Download or Upload Functions
        • Detect Execution of PSEXESVC via Remote Systems
        • Identify Suspicious String in Service Creation ImagePath
        • Identify File with Double Extensions
        • Detect Potential Cleartext Credentials in Commandline
        • Detect When Large Number of Files Downloaded From OneDrive or SharePoint
        • Identify and Investigate Phishing Attacks with KQL
      • PowerShell for SecOps
        • Powershell Remoting
        • Reconnaissance Discovery
        • Initial Access Discovery
        • Execution Discovery
        • Persistence Discovery
        • Privilege Escalation Discovery
        • Defence Evasion Discovery
        • Credential Access Discovery
        • Discovery
        • Lateral Movement Discovery
        • Collection Discovery
        • Command & Control (C2) Discovery
        • Exfiltration Discovery
        • Impact Discovery
      • Packet Analysis (pcap)
        • Tcpdump
        • Tcpdump (Intermediate)
        • Tshark
        • Ngrep
      • Investigating Suspicious Emails Using KQL
    • Intermediate and Advanced Skills
      • Investigate Using MITRE ATT&CK Methodology
        • Reconnaissance (TA0043) Techniques
        • Resource Development (TA0042) Techniques
        • Initial Access (TA0001) Techniques
        • Command Execution (TA0002) Techniques
        • Persistence (TA0003) Techniques
        • Privilege Escalation (TA0004) Techniques
        • Defence Evasion (TA0005) Techniques
        • Credential Access (TA0006) Techniques
        • Discovery (TA0007) Techniques
        • Lateral Movement (TA0008) Techniques
        • Collection (TA0009) Techniques
        • Command and Control (C2) (TA0011) Techniques
        • Exfiltration (TA0010) Techniques
        • Impact (TA0040) Techniques
    • Vulnerability Management
    • Malware Analysis
  • DFIR
    • Incident Response
      • Incident Triage
        • Triage Types and Processes
        • PowerShell for Detection and Analysis
          • Malware or Compromise Investigation
          • Lateral Movement Discovery
        • Registry Analysis
        • Sysinternals Intrusion Analysis
        • PowerShell Intrusion Analysis
        • Velociraptor Intrusion Analysis
        • Zimmerman Tools Intrusion Analysis
      • KAPE Artifacts Analysis
      • Velociraptor Artifacts Analysis
      • Using The Unified Kill Chain Model to Analyse Individual Cyber Attacks
        • Phase 1 - Gaining an Initial Foothold
          • Gaining Access to the Network
          • Establishing a Foothold
          • Network Discovery
      • Response Strategies
        • Privilege Escalation Assessment
        • Command and Control Assessment
        • Command Execution Assessment
        • Defence Evasion Assessment
        • Detection Assessment
        • Discovery Assessment
        • Exfiltration Assessment
        • Initial Access Assessment
        • Initial Impact Assessment Techniques
        • Lateral Movement Assessment
        • Persistence Assessment
    • Windows Forensics
      • Evidence of Execution
      • Window Artifact Analysis
        • Account Usage
        • User Activity Tracking (Event Logs)
        • Program Execution
        • File and Folder Opening
        • File Download
        • Browser Usage
        • Deleted File or File Knowledge
        • External Device & USB Usage
    • Linux Forensics
      • Linux Commandline Basics
      • Host Compromise Assessment
    • KQL for Defender & Sentinel
      • MDO (Office)
      • MDI (Identity)
      • MDE (Endpoint)
    • Memory Forensics
      • Memory Forensics (Volatility 3)
    • Playbooks
      • First Responder DFIR Playbook
        • Device Isolation
        • Evidence Collection
          • Acquire Triage Image Using KAPE
          • Acquire Triage Data Using Velociraptor
          • Acquire Triage Data Using Powershell
          • Acquire Triage Memory Image
          • Acquire Image Using FTK
          • AXIOM Cyber Data Collection
        • Windows Forensic Artefacts
          • Application Execution
          • File & Folder Knowledge
          • External Device Usage
          • Network Activity
          • Windows Event Logs
        • Initial Analysis
          • Memory Analysis (Vol 3)
          • Axiom Cyber Examiner
  • Detection Engineering
    • AD Attack Detections & Mitigations
      • Kerberoasting
      • Authentication Server Response (AS-REP) Roasting
      • Password Spraying
      • MachineAccountQuota Compromise
      • Unconstrained Delegation
      • Password in Group Policy Preferences (GPP) Compromise
      • Active Directory Certificate Services (AD CS) Compromise
      • Golden Certificate
      • DCSync
      • Dumping ntds.dit
      • Golden Ticket
      • Silver Ticket
      • Golden Security Assertion Markup Language (SAML)
      • Microsoft Entra Connect Compromise
      • One-way Domain Trust Bypass
      • Security Identifier (SID) History Compromise
      • Skeleton Key
      • Active Directory Security Controls
      • Active Directory Events for Detecting Compromise
    • Attack Triage Playbooks (KQL Triage)
      • Windows Malware Detection Playbook
      • Linux Host Intrusion Detection Playbook (CLI)
      • Linux Intrusion Detection Playbook
      • Large-Scale Compromise Detection Playbook
      • Ransomware Detection Playbook
      • Phishing Email Compromise Detection Playbook
      • Scam Detection Playbook
      • Customer Phishing Detection Playbook
      • Insider Abuse Detection Playbook
      • Information Leakage Detection Playbook
      • Social Engineering Detection Playbook
      • Malicious Network Behaviour Detection Playbook
      • Windows Intrusion Detection Playbook
      • Vulnerability Detection Playbook
      • Business Email Compromise Detection Playbook
    • Process Execution (KQL Triage)
    • Threat Hunting
      • Hunting Ransomware Indicators
      • Hunting With KQL
        • Detecting Malware Infection (MITRE ATT&CK: T1566, T1059)
        • Discovery Activities (MITRE ATT&CK: T1016, T1083, T1046)
        • Credential Theft (MITRE ATT&CK: T1003, T1078)
        • Lateral Movement (MITRE ATT&CK: T1076, T1021)
        • Data Theft (MITRE ATT&CK: T1041, T1071)
        • Detecting CommandLine Executions (MITRE ATT&CK: T1059)
        • Windows Security Logs (Identity and Logon Activities)
      • Hunting With Splunk
Powered by GitBook
On this page
  • Introduction
  • Triage & Investigation
  • Incident Response Workflow
  • Threat Hunting
  • Vulnerability Response
Edit on GitHub
  1. Detection Engineering

Attack Triage Playbooks (KQL Triage)

PreviousActive Directory Events for Detecting CompromiseNextWindows Malware Detection Playbook

Last updated 4 months ago

Introduction

Cybersecurity playbooks are essential for incident investigations, providing a structured, repeatable, and efficient framework to address security threats within an organisation. They outline predefined steps, detection techniques, and response strategies, enabling security teams to effectively identify, analyse, and mitigate incidents. By leveraging advanced query languages like KQL in tools such as Microsoft Defender and Sentinel, playbooks enhance the ability to uncover malicious activities, correlate threat intelligence, and streamline investigations. Their use fosters consistency in handling incidents, reduces response times, and minimises the impact of breaches. It also serves as a valuable resource for training and preparedness in an evolving threat landscape.

Note: The playbooks are focused on incident detection and analysis, NOT the entire incident response lifecycle. The idea is to help you confirm a true positive as early as possible using KQL queries. Beyond that point, the appropriate resources can be allocated to the response effort.

The following are some playbooks that can assist as a starting point for your KQL-based incident triage and analysis:

Triage & Investigation

The triage and investigation process is a critical component of effective cybersecurity operations, focused on quickly identifying, prioritising, and analysing potential security incidents to minimise risk and impact. Triage involves the initial assessment of alerts to determine their severity, validity, and urgency, enabling teams to focus on the most critical threats. Investigation dives deeper into the identified incidents, uncovering the root cause, scope, and potential impact and guiding appropriate response actions.

Playbooks are pivotal in these processes by providing standardised, step-by-step guidance tailored to specific incidents. They streamline triage by defining clear criteria for alert prioritisation and validating suspected threats, ensuring consistency and reducing false positives. During an investigation, playbooks offer predefined queries, analysis methods, and workflows, empowering analysts to uncover indicators of compromise, trace attack vectors, and correlate events efficiently. By reducing ambiguity and improving response times, playbooks enhance the overall effectiveness of triage and investigation while supporting continuous learning and operational improvement.

Incident Response Workflow

The incident response process is a cornerstone of effective cybersecurity operations, designed to detect, contain, mitigate, and recover from security incidents in a systematic and efficient manner. It follows a structured approach, typically involving preparation, detection, analysis, containment, eradication, recovery, and post-incident review, to minimise the impact of incidents on organisational operations and assets.

Playbooks are vital tools that enhance the incident response process by providing predefined, step-by-step procedures tailored to specific types of incidents. They offer clear guidance on detecting and analysing threats, escalating issues, and executing containment and remediation actions, ensuring consistency and reducing response times. By incorporating advanced detection techniques, such as KQL queries for platforms like Microsoft Defender and Sentinel, playbooks help responders quickly identify indicators of compromise, trace attack vectors, and understand the scope of an incident. Playbooks also promote coordination among teams, standardise communication workflows, and support compliance with regulatory and organisational requirements. Ultimately, they enable security teams to respond to incidents more effectively and learn from each event to strengthen defences over time.

Threat Hunting

The threat hunting process is a proactive cybersecurity activity focused on identifying potential threats that have evaded traditional detection methods. It involves exploring data across an organisation to uncover hidden malicious activities, anomalies, or indicators of compromise before they escalate into significant incidents. Threat hunting leverages a hypothesis-driven approach, using intelligence, patterns, and known tactics to identify and mitigate risks early in the attack lifecycle.

Playbooks are invaluable tools in the threat hunting process, providing predefined strategies, queries, and workflows that guide hunters in systematically analysing data and pursuing hypotheses. They ensure consistency in methodologies, help analysts cover all potential attack surfaces, and reduce the time needed to uncover hidden threats. By including advanced detection techniques, such as KQL queries for platforms like Microsoft Defender and Sentinel, playbooks enable hunters to efficiently sift through large datasets, identify anomalies, and trace complex attack chains. Additionally, playbooks support documentation and collaboration by outlining processes and findings, contributing to organisational learning and improving future threat hunting efforts.

Vulnerability Response

The vulnerability response process is critical to an organisation’s cybersecurity strategy. It is focused on identifying, assessing, prioritising, and remediating vulnerabilities across systems, applications, and networks. By addressing security weaknesses before adversaries can exploit them, the process aims to reduce the attack surface. It includes vulnerability scanning, risk assessment, patch management, and validation to ensure an organisation maintains a strong security posture.

Playbooks significantly enhance the vulnerability response process by providing structured and repeatable workflows for handling vulnerabilities. They define clear steps for assessing the criticality of vulnerabilities, prioritising remediation efforts based on risk, and effectively implementing patches or mitigation strategies. Playbooks also include predefined queries and automated tasks for identifying vulnerable assets, tracking remediation progress, and verifying fixes. By standardising the process, playbooks improve efficiency, consistently apply best practices, and reduce human error. Additionally, they enable better collaboration between teams, faster response times, and compliance with regulatory requirements while supporting continuous improvement in vulnerability management practices.

Windows Malware Detection Playbook
Linux Host Intrusion Detection Playbook (CLI)
Linux Intrusions Detection Playbook
Large-Scale Compromise Detection Playbook
Ransomware Detection Playbook
Phishing Compromise Detection Playbook
Scam Detection Playbook
Customer Phishing Detection Playbook
Insider Abuse Detection Playbook
Information Leakage Detection Playbook
Social Engineering Detection Playbook
Malicious Network Behaviour Detection Playbook
Windows Intrusion Detection Playbook
Vulnerability Detection Playbook
Business Email Compromise Detection Playbook