Performing Disk Forensics Investigation
Overview
Cybersecurity skill for performing disk forensics investigation. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"performing disk forensics investigation"
"Conducts disk forensics investigations using forensic imaging, file system analy"
A security incident requires forensic analysis of a system's persistent storage
Evidence preservation is needed for potential legal proceedings or HR investigations
Deleted files, browser history, or application artifacts must be recovered
A timeline of user or adversary activity must be reconstructed from file system metadata
Malware persistence mechanisms stored on disk need identification and documentation
Do not use for volatile evidence (running processes, network connections); use memory forensics with Volatility instead.
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 workstation with write-blocking hardware or software (Tableau T35u, Arsenal Image Mounter)
- Forensic imaging software: FTK Imager, Guymager, or dd with dcfldd
- Analysis platform: Autopsy, FTK (Forensic Toolkit), or X-Ways Forensics
- Sufficient storage (2-3x the target drive size for image plus working copies)
- Chain of custody forms and evidence bags for physical media
- Hash verification tools for evidence integrity (SHA-256)
Workflow
# 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()}
- Plan Operations — Define objectives, scope, and success criteria for disk forensics investigation operations.
- Prepare Environment — Set up tools, access, and data sources required for disk forensics investigation.
- Execute Core Workflow — Perform the disk forensics investigation operations following established procedures.
- Validate Results — Verify that results meet quality standards and objectives.
- Report Findings — Document results, observations, and recommendations.
- Follow Up — Track remediation actions and verify fixes where applicable.
Tools
- Analysis Platform — Data processing and visualization
- Collaboration Tools — Team coordination and knowledge sharing
Process
- Reconnaissance — Gather target information, identify attack surface, enumerate services
- Analysis/Exploitation — Execute the technique, analyze results, document findings
- Reporting — Document IOCs, write findings, provide remediation recommendations
Verification
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. |
1---2name: performing-disk-forensics-investigation3description: Use when conducts disk forensics investigations using forensic imaging, file system analysis, artifact recovery, and timeline reconstruction to support incident response cases. Utilizes tools such as FTK Imager, Autopsy, and The Sleuth Kit for evidence acquisition, deleted file recovery, and artifact examination. Activates for requests involving disk forensics, hard drive analysis, forensic imaging, file recovery, evidence acquisition, or digital forensic investigation. '.4license: Apache-2.05---67# Performing Disk Forensics Investigation89## Overview1011Cybersecurity skill for performing disk forensics investigation. Follows industry best practices and security standards.1213## When to Use14**Trigger phrases:**15- "performing disk forensics investigation"16- "Conducts disk forensics investigations using forensic imaging, file system analy"171819- A security incident requires forensic analysis of a system's persistent storage20- Evidence preservation is needed for potential legal proceedings or HR investigations21- Deleted files, browser history, or application artifacts must be recovered22- A timeline of user or adversary activity must be reconstructed from file system metadata23- Malware persistence mechanisms stored on disk need identification and documentation2425**Do not use** for volatile evidence (running processes, network connections); use memory forensics with Volatility instead.262728## When NOT to Use2930- When you lack proper authorization for testing31- For production systems without change management32- When the task requires legal or compliance expertise beyond technical scope333435## Prerequisites3637- Forensic workstation with write-blocking hardware or software (Tableau T35u, Arsenal Image Mounter)38- Forensic imaging software: FTK Imager, Guymager, or dd with dcfldd39- Analysis platform: Autopsy, FTK (Forensic Toolkit), or X-Ways Forensics40- Sufficient storage (2-3x the target drive size for image plus working copies)41- Chain of custody forms and evidence bags for physical media42- Hash verification tools for evidence integrity (SHA-256)4344## Workflow4546```python47# Example: IOC detection48import re4950IOC_PATTERNS = {51 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",52 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",53 "hash_md5": r"\b[a-f0-9]{32}\b",54 "hash_sha256": r"\b[a-f0-9]{64}\b",55}5657def extract_iocs(text: str) -> dict:58 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}59```60611. **Plan Operations** — Define objectives, scope, and success criteria for disk forensics investigation operations.622. **Prepare Environment** — Set up tools, access, and data sources required for disk forensics investigation.633. **Execute Core Workflow** — Perform the disk forensics investigation operations following established procedures.644. **Validate Results** — Verify that results meet quality standards and objectives.655. **Report Findings** — Document results, observations, and recommendations.666. **Follow Up** — Track remediation actions and verify fixes where applicable.6768## Tools6970- **Analysis Platform** — Data processing and visualization71- **Collaboration Tools** — Team coordination and knowledge sharing727374## Process75761. **Reconnaissance** — Gather target information, identify attack surface, enumerate services771. **Analysis/Exploitation** — Execute the technique, analyze results, document findings781. **Reporting** — Document IOCs, write findings, provide remediation recommendations7980## Verification8182- [ ] All disk forensics investigation procedures executed completely and documented83- [ ] Findings validated against multiple data sources84- [ ] False positives identified and filtered85- [ ] Results documented with evidence and timestamps86- [ ] Recommendations provided with risk-based prioritization8788## Anti-Rationalization Table8990| Rationalization | Reality |91|---|---|92| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |93| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |94| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |