🔏
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 Common C&C Techniques
  • 2. Data Collection and Preservation
  • 3. Network Traffic Analysis
  • 4. DNS Query Analysis
  • 5. Firewall and Proxy Logs Analysis
  • 6. Endpoint Analysis
  • 7. Malware Analysis (if applicable)
  • 8. Use of Specialised Forensic Tools
  • 9. Documentation and Reporting
  • 10. Post-Investigation Actions
  • 11. Tools and Techniques
  • 12. Key Considerations
Edit on GitHub
  1. DFIR
  2. Incident Response
  3. Response Strategies

Command and Control Assessment

Description: Forensically investigating Command and Control (C&C) techniques on workstations and server systems involves identifying how an attacker communicates with compromised systems to control them remotely and potentially exfiltrate data. This process is critical for understanding the scope of an attack and mitigating further risks.

1. Understanding Common C&C Techniques

  • Direct Connections: Using tools like remote desktop, SSH, or VNC.

  • HTTP/HTTPS-Based Communication: Often disguised as normal web traffic.

  • DNS-Based Communication: Using DNS queries to send commands or exfiltrate data.

  • Use of Proxy Servers: To route and obfuscate the traffic.

  • Social Media and Cloud Services: Utilising popular platforms to disguise communication.

2. Data Collection and Preservation

  • Forensic Imaging: Create exact images of affected systems using tools like FTK Imager or dd.

  • Memory Capture: Use tools like Magnet RAM Capture or WinPmem for capturing volatile memory, which may contain remnants of C&C communication.

  • Log Collection: Gather network logs, firewall logs, DNS logs, system logs, and web proxy logs.

3. Network Traffic Analysis

  • Traffic Capture and Analysis: Use tools like Wireshark or tcpdump to analyse network traffic for unusual patterns, especially outbound connections to unknown IPs or domains.

  • Protocol Analysis: Look for anomalies in standard protocols (HTTP, DNS, etc.) that could indicate C&C activities.

  • The decryption of Traffic: Where possible, decrypt encrypted network traffic to inspect the contents for command and control communication.

4. DNS Query Analysis

  • Logs Review: Examine DNS query logs for frequent or irregular requests to uncommon domains, which could indicate DNS tunnelling.

5. Firewall and Proxy Logs Analysis

  • Outbound Traffic: Check for any rules or logs that show unusual outbound traffic, especially traffic bypassing standard network egress points.

6. Endpoint Analysis

  • Running Processes: Analyse running processes and their network activity for signs of C&C communications.

  • Startup Items and Scheduled Tasks: Check for persistence mechanisms that may initiate C&C communication upon system restart.

  • Host-based Intrusion Detection Systems: Review alerts and logs for signs of C&C behaviour.

7. Malware Analysis (if applicable)

  • Static and Dynamic Analysis: If malware is identified, perform static and dynamic analysis to understand its communication mechanisms.

  • Reverse Engineering: Reverse-engineering malware may reveal built-in C&C domains or IP addresses.

8. Use of Specialised Forensic Tools

  • Forensic Suites: Tools like EnCase, Autopsy, or X-Ways for comprehensive system analysis.

  • Network Analysis Tools: Wireshark, Tcpdump, NetWitness, and NetworkMiner for network traffic analysis.

9. Documentation and Reporting

  • Detailed Documentation: Record all methodologies, findings, and tools used.

  • Forensic Report: Compile a comprehensive report detailing the C&C investigation, findings, and implications.

10. Post-Investigation Actions

  • Mitigation and Remediation: Implement measures to disrupt the C&C channels and prevent further unauthorised access.

  • Recovery and Notifications: Restore systems and notify relevant stakeholders per organisational and legal requirements.

11. Tools 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 Compliance: Ensure the investigation complies with relevant laws and regulations, especially when decrypting traffic.

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

  • Data Confidentiality: Handle all data securely, maintaining its confidentiality and integrity.

C&C investigation requires a multi-faceted approach, combining network analysis, endpoint inspection, and potentially malware analysis to fully understand the attacker's methods and impact. Tailoring the investigation to the specifics of the incident and the environment is crucial.

PreviousPrivilege Escalation AssessmentNextCommand Execution Assessment

Last updated 5 months ago