🔏
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
  • 1. Understanding Possible Impacts
  • 2. Data Collection and Preservation
  • 3. Assessing Data Exfiltration
  • 4. Evaluating Data Integrity
  • 5. System Compromise Assessment
  • 6. Service Disruption Analysis
  • 7. Investigating Persistence Mechanisms
  • 8. Lateral Movement Investigation
  • 9. Documentation and Reporting
  • 10. Post-Investigation Actions
  • 11. ols and Techniques
  • 12. Key Considerations
Edit on GitHub
  1. DFIR
  2. Incident Response
  3. Response Strategies

Initial Impact Assessment Techniques

Description: Forensically investigating the impact of a compromise on workstations and server systems is an essential step in understanding the extent of damage, the data affected, and what steps are necessary for recovery and future prevention. This process involves thoroughly examining affected systems to identify the scope of the attack, assess the damage, and uncover the methods used by the attackers.

1. Understanding Possible Impacts

  • Data Exfiltration: Determining if sensitive data was accessed or stolen.

  • Data Destruction: Assessing if any data was deleted or corrupted.

  • System Compromise: Evaluating the integrity of the operating system and critical software.

  • Service Disruption: Identifying if key services were disrupted or disabled.

  • Persistence: Checking for any signs that the attacker has established ongoing access.

  • Lateral Movement: Investigating whether the compromise spread to other systems in the network.

2. Data Collection and Preservation

  • Forensic Imaging: Use tools like FTK Imager or dd to create exact copies of affected systems' hard drives.

  • Memory Capture: Use tools like Magnet RAM Capture or WinPmem to capture volatile memory.

  • Log Collection: Secure all relevant logs, including system logs, application logs, security logs, and network logs.

3. Assessing Data Exfiltration

  • Network Traffic Analysis: Use tools like Wireshark or Tcpdump to analyse network traffic for signs of data being sent to external locations.

  • Log Analysis: Check firewall, web proxy, and server logs for unusual outbound traffic.

4. Evaluating Data Integrity

  • File System Analysis: Examine the file system for signs of deletion, alteration, or encryption of files.

  • Data Recovery Techniques: Use data recovery tools to attempt to restore deleted or corrupted files.

5. System Compromise Assessment

  • Malware Analysis: Look for and analyse any malware that may have been used in the attack.

  • Rootkit Detection: Employ rootkit detection tools to uncover any stealthy malware or tools used by the attackers.

  • Integrity Checks: Run integrity checks on critical system files and configurations.

6. Service Disruption Analysis

  • System and Application Logs: Review these logs for service stop events, crashes, or configuration changes that could indicate sabotage.

  • Dependency Checks: Ensure critical services and applications function properly and depend on uncompromised components.

7. Investigating Persistence Mechanisms

  • Startup Items: Check for unauthorised scripts or programs in startup locations.

  • Scheduled Tasks and Cron Jobs: Look for tasks that may provide ongoing access or trigger malicious activities.

  • Registry (Windows): Examine registry keys commonly used for persistence.

8. Lateral Movement Investigation

  • Active Directory and Network Logs: Analyse these logs for signs of credential use on multiple systems.

  • Endpoint Detection and Response (EDR) Data: Review EDR data for patterns that suggest movement across the network.

9. Documentation and Reporting

  • Detailed Documentation: Keep a comprehensive record of all findings, methodologies, and evidence paths.

  • Impact Report: Prepare a detailed report summarising the impact, including data loss, system integrity issues, and business disruption.

10. Post-Investigation Actions

  • Remediation and Mitigation: Implement necessary measures to recover data, restore services, and secure the network.

  • Incident Review and Policy Update: Conduct a thorough review of the incident to improve future security posture and incident response capabilities.

11. ols and Techniques

  • Digital Forensics:

    • Specialised tools for evidence collection and analysis:

      • OpenText EnCase Forensics (commercial tool)

      • FTK (Forensic Toolkit)

      • Volatility (memory forensics)

      • Autopsy (open-source)

      • Cyber Triage (commercial tool)

      • Binalyze AIR (commercial tool)

      • Belkasoft (commercial tool)

      • Oxygen Forensics (commercial tool)

      • X-ways Forensics (commercial tool)

      • The Sleuth Kit (open-source tool)

      • Eric Zimmerman Tools (open-source tool)

    • Techniques include timeline analysis, file recovery, and reverse engineering.

  • Incident Response:

    • Tools for monitoring, containment, and eradication:

      • SIEM (Splunk, QRadar, Microsoft Sentinel, Sumo Logic, Graylog, Elastic Security, LogRhythm, Datadog, Exabeam)

      • EDR (CrowdStrike, SentinelOne, Defender for Endpoint, Cortex XDR, FortiEDR)

      • Firewalls and IDS/IPS systems

    • Techniques include log analysis, threat containment, and system restoration.

12. Key Considerations

  • Legal and Compliance Factors: Ensure the investigation complies with legal and regulatory requirements.

  • Chain of Custody: Maintain an accurate chain of custody for all forensic evidence.

  • Confidentiality: Handle all data securely, maintaining confidentiality and integrity throughout the process.

Forensic investigations into the impact of a compromise require a multi-faceted approach, combining technical analysis with an understanding of business operations and data sensitivity. Tailoring the investigation to the specifics of the incident and the environment is essential for a comprehensive assessment.

PreviousInitial Access AssessmentNextLateral Movement Assessment

Last updated 5 months ago