Incident Response

Outlines a structured approach to manage and mitigate security incident effectively.

Incident Response Process

Incident: Act of violating an explicit or implied security policy.

Seven Stages:

  1. Preparation: Strengthening systems and networks to resist attacks.
  2. Detection: Identifies security incidents. We move on once we have triaged and categorized the incident.
  3. Analysis: Thorough examination and evaluation of incident. Understand scope, impact, and potential consequences. Stakeholders informed, containment begins, initial response actions taken.
  4. Containment: Limit incident’s impact by securing data and protecting business operations.
  5. Eradication: Aims to remove malicious activity from system/network.
  6. Recovery: Restore systems and services to secure state. Often involves restoring to known-good backup, installing security patches, and implementing configuration updates.
  7. Post-incident activity/Lessons learned: Happens after containment, eradication, and full recovery.
    1. Root cause analysis: Identifies incident’s source and how to prevent it in the future.
    2. Lessons learned process: Documents experiences during incidents in a formalized way.
    3. After-action report: Collects formalized information about what occurred.

Threat Hunting

Cybersecurity method for finding hidden threats not caught by regular security monitoring.

Steps:

  1. Establish a hypothesis: Predict high-impact, likely events through threat modeling.
  2. Profiling Threat Actors and Activities: Envision how potential attackers might intrude and what they aim to achieve.
  3. Analyze: Analyze logs and data on processes, file systems, and server changes to gather information.

Threat Hunting v. Standard Detection: Normal sensors work at detecting known threats; threat hunting is about finding undetected issues, things that bypass existing rules, and cases where queries do not yield expected data.

Root Cause Analysis

Systematic process to identify initial source of an incident and how to prevent it from occurring again. Make sure this process uses a no-blame approach, the goal is find out what occurred to cause the incident.

Incident Response Training and Testing

Digital Forensic Procedures

Process of investigating and analyzing digital devices and data to uncover evidence for legal disputes. Should always adhere to organization’s procedures.

Phases:

  1. Identification: Ensures safety of scene, secures it to prevent evidence contamination, and determines the scope of the evidence to be collected.
  2. Collection: Process of gathering, preserving, and documenting physical or digital evidence in various fields.
  3. Analysis: Systematically scrutinizing data to uncover relevant information such as potential signs of criminal activity, hidden files, timestamps, and user interactions.
  4. Reporting: Documenting findings, processes, and methodologies used during a digital forensic investigation.

Legal Hold: Formal notification that instructs employees to preserve all potentially relevant electronic data, documents, and records.

Electronic Discovery: Process of identifying, collecting, and producing electronically stored information during potential legal proceedings.

Forensic analysts must adhere to a code of ethics that maintains:

  1. Avoiding bias
  2. Repeatable actions
  3. Preservation of evidence

Data Collection Procedures

Standard forensic data collection procedures to remember:

  1. Capture RAM (Memory).
  2. Capture a bit-by-bit disk image of the storage drive.
  3. Utilize forensic tools such as Forensic Toolkit (FTK) or EnCase.
  4. Capture screenshots of the machine.
  5. Always follow the order of volatility when collecting evidence.
  6. Collect statements from witnesses and administrators.
  7. Review licensing and documentation for all systems.
  8. Track man hours and billing.

Data Acquisition: Method and tools used to create a forensically sound copy of the data from a source device, such as system memory or a hard disk.

Order of Volatility:

  1. CPU registers and cache memory
  2. System memory, routing tables, ARP caches, process table, temporary swap files
  3. Persistent mass storage (HDD/SDD/flash drive)
  4. Remote logging and monitoring data
  5. Physical configuration and network topology
  6. Archival media