Collecting Volatile Evidence From Compromised Host

---
name: collecting-volatile-evidence-from-compromised-host
description: Use when collect volatile forensic evidence from a compromised system
  following order of volatility, preserving memory, network connections, processes,
  and system state before they are lost. Use when working with collecting volatile
  evidence from compromised host.
domain: cybersecurity
tags:
- incident-response
- dfir
- forensics
- volatile-evidence
- memory-forensics
- chain-of-custody
subdomain: incident-response
mitre_attack:
- T1003
- T1055
- T1059
- T1547
version: '1.0'
author: oyi77
license: Apache-2.0
nist_csf:
- RS.MA-01
- RS.MA-02
- RS.AN-03
- RC.RP-01
category: cybersecurity
---

# Collecting Volatile Evidence From Compromised Host

## Overview

Cybersecurity skill for collecting volatile evidence from compromised host. Follows industry best practices and security standards.

## When to Use
**Trigger phrases:**
- "collecting volatile evidence from compromised host"
- "Collect volatile forensic evidence from a compromised system following order of "

- Security incident confirmed and compromised host identified
- Before system isolation, shutdown, or remediation begins
- Memory-resident malware suspected (fileless attacks)
- Need to capture network connections, running processes, and system state
- Legal proceedings may require forensic evidence preservation
- Incident requires root cause analysis with volatile data


## When NOT to Use

- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope


## Prerequisites
- Forensic collection toolkit on USB or network share (trusted tools)
- WinPmem/LiME for memory acquisition
- Write-blocker or forensic workstation for disk imaging
- Chain of custody documentation forms
- Secure evidence storage with integrity verification
- Authorization to collect evidence (legal/HR approval for insider cases)

## Workflow

```python
# Example: IOC detection
import re

IOC_PATTERNS = {
    "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
    "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
    "hash_md5": r"\b[a-f0-9]{32}\b",
    "hash_sha256": r"\b[a-f0-9]{64}\b",
}

def extract_iocs(text: str) -> dict:
    return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
```

1. **Define Objectives** — Clarify the goals and scope for volatile evidence from compromised host.
2. **Gather Resources** — Collect tools, data, and access needed for volatile evidence from compromised host.
3. **Execute Process** — Carry out volatile evidence from compromised host operations methodically.
4. **Verify Quality** — Check results against acceptance criteria.
5. **Document Outcomes** — Record findings, decisions, and next steps.

## Tools

- **Analysis Platform** — Data processing and visualization
- **Collaboration Tools** — Team coordination and knowledge sharing


## Process

1. **Prepare** — Gather requirements, verify prerequisites, set up environment
1. **Execute** — Run collecting volatile evidence from compromised host workflow with configured parameters
1. **Verify** — Validate output meets requirements, document results

## Verification

- [ ] All volatile evidence from compromised host procedures executed completely and documented
- [ ] Findings validated against multiple data sources
- [ ] False positives identified and filtered
- [ ] Results documented with evidence and timestamps
- [ ] Recommendations provided with risk-based prioritization

## Anti-Rationalization Table

| Rationalization | Reality |
|---|---|
| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |
| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |