KARIM ASHRAF SPACE.
  • Who Am I ?
  • WRITEUPS
    • What about Practice in Cyber Security?
    • Dark Side of VSCode
    • What about Cy-nix Machine?
    • Cyberdefenders Labs
      • Web Investigation Blue Team Lab
      • Red Stealer Blue Team Lab
      • WebStrike Blue Team Lab
      • BlueSky Ransomware Blue Team Lab
      • PsExec Hunt Blue Team Lab
      • OpenWire Blue Team Lab
      • 3CX Supply Chain Blue Team Lab
      • PoisonedCredentials Lab
      • Reveal Lab
    • Lets Defend
      • Incident Responder Path
        • Cybersecurity Incident Handling Guide
          • Introduction to Incident Handling
          • Incident Handling Steps
          • Preparation
          • Detection and Analysis
          • Containment, Eradication, and Recovery
          • Post-Incident Activity
        • Incident Response on Windows
          • How to Create Incident Response Plan?
          • Incident Response Procedure
          • 3 Important Things
          • Free Tools That Can Be Used
          • Live Memory Analysis
          • Task Scheduler
          • Services
          • Registry Run Keys / Startup Folder
          • Files
          • Checklist
        • Incident Response on Linux
          • How to Create Incident Response Plan?
          • Incident Response Procedure
          • 3 Important Things
          • Users and Groups
          • Processes
          • Files and File System
          • Mounts
          • Network
          • Service
          • Cron Job
          • SSH Authorized Keys
          • Bash_rc & Bash_profile
          • Useful Log Files
        • Hacked Web Server Analysis
          • Introduction to Hacked Web Server Analysis
          • Log Analysis on Web Servers
          • Attacks on Web Servers
          • Attacks Against Web Applications
          • Vulnerabilities on Servers
          • Vulnerabilities in Programming Language
          • Discovering the Web Shell
          • Hacked Web Server Analysis Example
        • Log Analysis with Sysmon
          • Introduction and Set Up of Sysmon
          • Detecting Mimikatz with Sysmon
          • Detecting Pass The Hash with Sysmon
          • Detecting Privilege Escalation with Sysmon
        • Forensic Acquisition and Triage
          • Introduction to Forensics Acquisition and Triage
          • Acquiring Memory Image From Windows and Linux
          • Custom Image Using FTK and Mounting Image for Analysis
          • KAPE Targets for Acquisition
          • KAPE Modules for Triage and Analysis
          • Triage Using FireEye Redline
          • Acquisition and Triage of Disks Using Autopsy
        • Memory Forensics
          • What is Memory Forensics
          • Memory Analysis Procedures
        • Registry Forensics
          • Introduction to Windows Registry Forensics
          • Acquiring Registry Hives
          • Regedit and Registry Explorer
          • System, Users and Network Information
          • Shellbags
          • Shimcache
          • Amcache
          • Recent Files
          • Dialogue Boxes MRU
        • Event Log Analysis
          • Introduction to Event Logs
          • Event Log Analysis
          • Authentication Event Logs
          • Windows Scheduled Tasks Event Logs
          • Windows Services Event Logs
          • Account Management Events
          • Event Log Manipulation
          • Windows Firewall Event Logs
          • Windows Defender Event Logs
          • Powershell Command Execution Event logs
        • Browser Forensics
          • Introduction to Browser Forensics
          • Acquisition
          • Browser Artifacts
          • Tool: BrowsingHistoryView
          • Manual Browser Analysis
          • Hindsight Framework
        • GTFOBins
          • Introduction to GTFOBins
          • Shell
          • Command
          • Reverse Shell
          • Bind Shell
          • File Upload
          • File Download
          • Sudo
        • Hunting AD Attacks
          • Introduction to Active Directory
          • Hunting AS-REP Roasting Attack
          • Hunting for Kerberoasting Attacks
          • Hunting for LDAP Enumerations (Bloodhound_Sharphound)
          • Hunting for NTDS Database Dumping
          • Hunting for Golden Ticket Attacks
          • Hunting for NTLM Relay Attacks
        • Writing a Report on Security Incident
          • Introduction to Technical Writing
          • Reporting Standards
          • Reporting Style
          • Report Formatting
          • Report Templates
        • How to Prepare a Cyber Crisis Management Pla
          • Introduction to Crisis Management
          • General Preparation
          • Tools
          • Backups
          • Alerts and End of Crisis
        • Advanced Event Log Analysis
          • Process Creation
          • DNS Activity
          • File/Folder Monitoring
          • BITS Client Event Log
          • Network Connections Event Log
          • MSI Event Logs
        • USB Forensics
          • Introduction to USB Forensics
          • USB Registry Key
          • USB Event Logs
          • Folder Access Analysis via Shellbags
          • File Access Analysis via Jumplists
          • Automated USB Parsers Tools
        • Windows Disk Forensics
          • SRUM Database
          • Jumplists
          • Recycle Bin Artifacts
          • RDP Cache
          • Thumbnail Cache
    • BTLO LABS
      • Bruteforce BTLO
    • The Complete Active Directory Security Handbook
      • Introduction
      • Active Directory
      • Attack Technique 1: Pass the Hash: Use of Alternate Authentication Material (T1550)
      • Attack Technique 2: Pass the Ticket: Use of Alternate Authentication Material (T1550)
      • Attack Technique 3: Kerberoasting
      • Attack Technique 4: Golden Ticket Attack
      • Attack Technique 5: DCShadow Attack
      • Attack Technique 6: AS-REP Roasting
      • Attack Technique 7: LDAP Injection Attack
      • Attack Technique 8: PetitPotam NTLM Relay Attack on a Active Directory Certificate Services (AD CS)
      • Conclusion & References
    • Windows Privilege Escalation
      • Tools
      • Windows Version and Configuration
      • User Enumeration
      • Network Enumeration
      • Antivirus Enumeration
      • Default Writeable Folders
      • EoP - Looting for passwords
      • EoP - Incorrect permissions in services
      • EoP - Windows Subsystem for Linux (WSL)
      • EoP - Unquoted Service Paths
      • EoP - $PATH Interception
      • EoP - Named Pipes
      • EoP - Kernel Exploitation
      • EoP - AlwaysInstallElevated
      • EoP - Insecure GUI apps
      • EoP - Evaluating Vulnerable Drivers
      • EoP - Printers
      • EoP - Runas
      • EoP - Abusing Shadow Copies
      • EoP - From local administrator to NT SYSTEM
      • EoP - Living Off The Land Binaries and Scripts
      • EoP - Impersonation Privileges
      • EoP - Privileged File Write
      • References
      • Practical Labs
    • Advanced Log Analysis
      • Key Windows Event IDs for Cybersecurity Monitoring
      • Analyzing a Series of Failed Login Attempts from Multiple IP Addresses
      • Steps to Investigate Suspicious Outbound Network Traffic
      • Identifying and Responding to Lateral Movement within a Network
      • Distinguishing Between Legitimate and Malicious PowerShell Executions
      • Detecting and Analyzing a Potential Data Exfiltration Incident Using Log Data
      • Steps to Analyze PowerShell Logging (Event ID 4104) for Malicious Activity
      • How to Identify an Internal Pivot Attack Using Log Data
      • Indicators in Logs Suggesting a Privilege Escalation Attack
      • How to Detect Command and Control (C2) Communication Using Log Analysis
      • How to Analyze Logs to Detect a Brute-Force Attack on an RDP Service
      • How to Analyze Logs to Detect a Brute-Force Attack on an RDP Service
      • How to Detect the Use of Living-Off-the-Land Binaries (LOLBins) in Logs
      • How to Detect Malware Masquerading as a Legitimate Process Using Log Analysis
      • How to Detect and Analyze Lateral Movement Using Windows Event Logs
      • How to Detect Potential Ransomware Attacks in Their Early Stages Using Log Analysis
      • How to Detect and Analyze Privilege Escalation Using Windows Event Logs
      • How to Detect the Use of Mimikatz or Similar Tools in Log Data
      • How to Detect and Analyze DNS Tunneling Through Log Analysis
      • How to Detect a Pass-the-Hash (PtH) Attack Using Logs
      • How to Detect and Analyze an Attacker’s Use of a Remote Access Trojan (RAT) Using Log Data
      • How to Detect Lateral Movement Using Windows Event Logs
      • How to Detect and Investigate Data Exfiltration Using Logs
      • How to Identify and Analyze an Internal Phishing Campaign Using Email and System Logs
      • How to Detect and Analyze Ransomware Activity Using Logs
      • How to Detect Malicious PowerShell Activity Using Log Analysis
      • How to Detect and Respond to Brute-Force Attacks Using Log Data
      • How to Detect Privilege Escalation Attempts Using Windows Event Logs
      • How to Detect and Analyze Suspicious Domain Name Resolution Requests in DNS Logs
      • How to Detect and Respond to Unauthorized Access to Critical Files
      • How to Detect and Analyze Suspicious PowerShell Command Execution
      • How to Detect and Investigate Account Takeover (ATO) Attempts Using
      • How to Detect and Analyze the Use of Living Off the Land Binaries (LOLBins)
      • How to Detect and Investigate Lateral Movement
      • How to Detect and Investigate Data Exfiltration
      • How to Detect and Analyze Suspicious Activity Involving Service Accounts
      • How to Detect and Investigate Anomalous PowerShell Activity Related to Credential Dumping
      • How to Detect and Analyze the Execution of Unsigned or Malicious Executables
      • How to Detect and Investigate Abnormal Spikes in Network Traffic
    • Methods for Stealing Password in Browser
      • Important Tables and Columns
      • Important Queries
      • Profiles
      • Tools
        • HackBrowserData
        • Browser-password-stealer
        • BrowserPass
        • WebBrowserPassView
        • Infornito
        • Hindsight
        • BrowserFreak
        • BrowserStealer
    • Hack The Box Tracks
      • Soc Analyst Path 2024
        • 1. Incident Handling Process
          • Incident Handling Definition & Scope
          • Incident Handling's Value & Generic Notes
          • Cyber Kill Chain
          • Incident Handling Process Overview
          • Preparation Stage (Part 1)
          • Preparation Stage (Part 2)
          • DMARC
          • Endpoint Hardening (& EDR)
          • Network Protection
          • Privilege Identity Management / MFA / Passwords
          • Vulnerability Scanning
          • User Awareness Training
          • Active Directory Security Assessment
          • Purple Team Exercises
          • Detection & Analysis Stage (Part 1)
          • Initial Investigation
          • Incident Severity & Extent Questions
          • Incident Confidentiality & Communication
          • Detection & Analysis Stage (Part 2)
          • The Investigation
          • Initial Investigation Data
          • Creation & Usage Of IOCs
          • Identification Of New Leads & Impacted Systems
          • Data Collection & Analysis From The New Leads & Impacted Systems
          • Containment
          • Eradication
          • Recovery
          • Post-Incident Activity Stage
          • Reporting
        • 2. Security Monitoring & SIEM Fundamentals
          • What Is SIEM?
          • The Evolution Of SIEM And How It Works
          • SIEM Business Requirements & Use Cases Log Aggregation & Normalization
          • Data Flows Within A SIEM
          • What Are The Benefits Of Using A SIEM Solution
          • What Is the Elastic Stack?
          • The Elastic Stack As A SIEM Solution
          • How To Identify The Available Data
          • The Elastic Common Schema (ECS)
          • SOC Definition & Fundamentals
          • Evolution of Security Operations Centers (SOCs)
          • What Is MITRE ATT&CK?
          • What Is A SIEM Use Case?
          • How To Build SIEM Use Cases
          • SIEM Visualization Example 1: Failed Logon Attempts (All Users)
          • SIEM Visualization Example 2: Failed Logon Attempts (Disabled Users)
          • SIEM Visualization Example 3: Successful RDP Logon Related To Service Accounts
          • SIEM Visualization Example 4: Users Added or Removed from a Local Group
          • What Is Alert Triaging?
  • COURSES SUMMARY
    • TCM SEC
      • TCM linux Privilege Escalation
      • TCM OSINT
    • The SecOps Group
      • Certified AppSec Practitioner exam
      • CNSP Review
    • Cybrary
      • Cybrary Offensive Pentesting
  • TIPS&TRICKS
    • Windows Shorcuts Arrow Remover
    • Kali KEX
    • Intel TurboBoost
    • Pentest_Copilot
    • Ferdium
    • Youtube Adblock_Bybass
    • Burb-Bambdas
    • Burb Customizer
    • BetterFox
Powered by GitBook
On this page
  • Incident Responder Profile
  • Core Competencies
  • 1. Containment
  • 2. Eradication
  • 3. Recovery
  • 4. Post-Recovery Check
  • Key Tools for Incident Response
  • Best Practices for Incident Response
  1. WRITEUPS
  2. Lets Defend
  3. Incident Responder Path
  4. Cybersecurity Incident Handling Guide

Containment, Eradication, and Recovery

PreviousDetection and AnalysisNextPost-Incident Activity

Last updated 6 months ago

Incident Responder Profile

Experienced Incident Responder specializing in the containment, eradication, and recovery phases of cybersecurity incidents. Adept at isolating compromised systems, removing threats, and restoring operations while preserving evidence for post-incident analysis. Proficient in developing tailored strategies to protect critical systems and ensure minimal disruption during incident response. Committed to reinforcing organizational resilience through structured and methodical response protocols.


Core Competencies

1. Containment

  • Objective: Prevent the spread of an incident and limit the attacker’s access.

  • Key Actions:

    • Immediate Action:

      • As soon as an incident is confirmed, initiate containment to minimize damage.

    • Containment Methods:

      • Isolate Devices: Move compromised systems to a secure, segmented network.

      • Disable Services: Stop affected services that could propagate the attack.

      • Power Down or Disconnect: For severe incidents, physically disconnect or shut down devices.

      • Account Disabling: Disable compromised accounts in the Active Directory or corporate network.

    • EDR Utilization:

      • Use Endpoint Detection and Response (EDR) tools to isolate devices.

      • Allow communication only with the EDR server for further analysis and live forensics.

    • Critical System Strategies:

      • For high-priority assets (e.g., financial systems, healthcare databases):

        • Avoid full network isolation to prevent operational disruption.

        • Implement controlled containment measures such as application whitelisting or firewall rules.

2. Eradication

  • Objective: Eliminate the root cause of the incident and remove all malicious artifacts.

  • Key Actions:

    • Evidence Documentation:

      • Before eradication, capture relevant artifacts for further investigation:

        • Malware hashes, screenshots, and network logs.

        • Save malicious files to an isolated analysis environment.

    • Removal of Malicious Artifacts:

      • Identify and remove all files, scripts, and tools left by the attacker.

      • Disable or delete compromised accounts.

      • Eliminate any unauthorized accounts or credentials added by the attacker.

    • Terminate Malicious Processes:

      • Stop all processes linked to the attack using tools like Task Manager, Process Hacker, or PowerShell.

    • Mitigate Vulnerabilities:

      • Identify vulnerabilities exploited during the attack (e.g., unpatched software, misconfigurations).

      • Apply immediate fixes:

        • Install missing patches.

        • Harden system configurations to prevent re-exploitation.

3. Recovery

  • Objective: Restore affected systems to their original state and prevent recurrence.

  • Key Actions:

    • System Restoration:

      • Restore from clean backups taken before the compromise.

      • If backups are unavailable or compromised:

        • Rebuild systems from scratch using trusted sources.

      • Replace infected or corrupted files with verified clean versions.

    • Patch and Secure:

      • Apply patches to all systems involved to close exploited vulnerabilities.

      • Strengthen security configurations (e.g., enforcing MFA, enabling advanced firewall rules).

    • Credential Updates:

      • Reset credentials for all affected or at-risk accounts.

      • Implement password policies to ensure strong, unique credentials.

    • Post-Recovery Verification:

      • Validate that systems, services, and applications are functioning as expected.

      • Conduct thorough testing, including functional and performance tests.

    • Continuous Monitoring:

      • Monitor the network and systems closely for any signs of residual or continued compromise.

4. Post-Recovery Check

  • Objective: Ensure thorough documentation and extract insights to improve future response.

  • Key Actions:

    • Documentation:

      • Record all containment, eradication, and recovery actions taken.

      • Include details on timelines, individuals involved, and tools used.

    • Protocol Compliance:

      • Ensure that actions align with organizational incident response policies.

      • Verify compliance with legal, regulatory, or industry-specific standards.

    • Incident Review:

      • Conduct a post-incident review to identify what worked and areas for improvement.

      • Update response plans, playbooks, and training based on lessons learned.

      • Share findings with relevant stakeholders to enhance organizational readiness.


Key Tools for Incident Response

  • Containment:

    • EDR Platforms (CrowdStrike, SentinelOne): For rapid device isolation.

    • Firewall/Network Tools: To implement temporary blocks on malicious IPs.

  • Eradication:

    • Process Hacker, Task Manager, PowerShell: For stopping malicious processes.

    • Autoruns: To remove persistence mechanisms from startup or registry.

  • Recovery:

    • Backup Solutions: Veritas, Veeam for restoring clean backups.

    • Patching Tools: WSUS, Patch Manager for vulnerability remediation.

  • Post-Recovery:

    • SIEM Solutions (Splunk, ELK Stack): For continuous monitoring.

    • Incident Documentation Tools: Jira, Confluence for centralized record-keeping.


Best Practices for Incident Response

  1. Tailored Containment Strategies:

    • Design containment measures that balance security and operational needs.

  2. Preserve Evidence:

    • Ensure that evidence is intact for forensic analysis and compliance purposes.

  3. Communication:

    • Maintain clear communication with all stakeholders, including legal, IT, and executive teams.

  4. Continuous Improvement:

    • Leverage every incident as an opportunity to refine response protocols and tools.

By following a structured approach to containment, eradication, and recovery, this Incident Responder ensures minimal disruption, effective threat neutralization, and swift restoration of normal operations.