acquiring-disk-image-with-dd-and-dcfldd

Automate disk imaging with dd and dcfldd and SHA-256 hash verification.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Axxxxxxaaann/KAIRI-Skills --skill acquiring-disk-image-with-dd-and-dcfldd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acquiring-disk-image-with-dd-and-dcfldd
Source: https://github.com/Axxxxxxaaann/KAIRI-Skills/tree/main/skills/acquiring-disk-image-with-dd-and-dcfldd
Command: npx skills add https://github.com/Axxxxxxaaann/KAIRI-Skills --skill acquiring-disk-image-with-dd-and-dcfldd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Forensic investigators often struggle to produce verifiable, bit-for-bit copies of storage media while preserving evidence integrity across diverse devices.

Core Features & Use Cases

  • End-to-end imaging workflow using dd and dcfldd with built-in hashing (SHA-256) to verify integrity.
  • Supports write-blocked acquisition, hash logging, split imaging, and acquisition reporting.
  • Use Case: Incident response, legal discovery, and archival verification across HDDs, SSDs, and USB drives.

Quick Start

Create a forensic image of a target device (e.g., /dev/sdb) into a case folder, verify the image hash against the source, and generate a JSON acquisition report.

Frequently Asked Questions about acquiring-disk-image-with-dd-and-dcfldd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a forensic disk image with SHA-256 hash verification?

Forensic disk imaging with SHA-256 hash verification is automated using dd and dcfldd workflows. The process creates bit-for-bit copies of storage media, logs hashes to verify evidence integrity, and generates a JSON acquisition report.

Can I use dcfldd for split imaging and evidence acquisition across different drive types?

Yes, dcfldd supports split imaging and evidence acquisition across HDDs, SSDs, and USB drives. It applies write-blocked acquisition techniques to preserve source media integrity while generating detailed hash logs during the copying process.

What is the best way to ensure evidence integrity during disk imaging?

Ensuring evidence integrity during disk imaging requires write-blocked acquisition and SHA-256 hash verification. By comparing the source media hash against the generated image hash, investigators can cryptographically prove the copy is forensically sound.

Does this disk imaging workflow generate reports for legal discovery and incident response?

Yes, the disk imaging workflow generates JSON acquisition reports for legal discovery and incident response. These reports document the imaging process, hash verification results, and case details to support legal evidence collection and archival verification.

When do I need write-blocked acquisition for disk imaging?

Write-blocked acquisition is needed whenever preserving original evidence integrity is required, such as in legal discovery or incident response. It prevents any accidental modification to the source HDD, SSD, or USB drive during the bit-for-bit copying process.

dd vs dcfldd: which should I use for forensic disk imaging?

Both dd and dcfldd are supported for forensic disk imaging. While dd is the standard utility, dcfldd offers enhanced features like split imaging and simultaneous hash calculation, making it highly effective for evidence management and incident response workflows.