Skip to content
Threats Guide

Digital Forensics

Not reviewedNo review date recordedEdit this page on GitHub

Overview

Digital forensics involves the preservation, identification, extraction, documentation, and interpretation of computer media for evidentiary purposes and root cause analysis.

Types of Forensics

1. Memory Forensics (RAM)

  • Running processes
  • Network connections
  • Open files
  • Malware in memory
  • Encryption keys

2. Disk Forensics

  • Deleted files
  • File system analysis
  • Timeline analysis
  • Hidden data
  • Partition recovery

3. Network Forensics

  • Packet capture
  • Connection logs
  • Traffic analysis
  • Protocol analysis

4. Mobile Forensics

  • Call logs
  • Messages
  • App data
  • Location history

Key Concepts

Chain of Custody

Digital Forensics Evidence Workflow

flowchart TD
    A["🚔 Evidence Seized"] --> B["📝 Documented"]
    B --> C["🔐 Stored Securely"]
    C --> D["🔬 Analyzed"]
    D --> E["⚖️ Returned or Presented in Court"]

    %% Styling
    classDef stage fill:#2c3e50,color:#ffffff,stroke:#0b1a2a,stroke-width:2px;
    class A,B,C,D,E stage;

Write Blockers

  • Hardware write blockers
  • Software write blockers
  • Prevents evidence tampering

Imaging Types

  • Physical: Bit-for-bit copy
  • Logical: Files and folders only
  • Live: Running system capture

Forensic Workflow

Digital Forensics Process

flowchart TD
    A["📥 Acquire"] --> B["✅ Verify"]
    B --> C["🔍 Analyze"]
    C --> D["📝 Report"]
    D --> E["⚖️ Present"]

    %% Supporting actions
    A --> A1["💾 Create Forensic Image"]
    B --> B1["🔑 Hash Verification"]
    C --> C1["🛠️ Forensic Tools"]
    D --> D1["📄 Document Findings"]
    E --> E1["🏛️ Court Presentation"]

    %% Styling
    classDef main fill:#34495e,color:#ffffff,stroke:#1b2631,stroke-width:2px;
    classDef support fill:#d6eaf8,color:#000000,stroke:#2e86c1,stroke-width:1.5px;

    class A,B,C,D,E main;
    class A1,B1,C1,D1,E1 support;

Best Practices

  1. Never work on original evidence
  2. Document every keystroke
  3. Use verified tools
  4. Maintain integrity with hashes
  5. Follow legal procedures