CHFI V10 — Lesson 2: Acquisition, Storage Media, File Systems, Operating Systems, and Recovery

Learning Objectives

• Explain the roles, services, data, settings, dependencies, and decision criteria governing forensic acquisition and storage media.
• Implement and validate file-system artifacts, operating-system evidence, and data recovery using controlled evidence and clear acceptance criteria.
• Evaluate the condition where a basic control passes but operating-system evidence fails because file-system artifacts data, configuration order, or dependency assumptions differ and select a proportionate corrective response.

Detailed Topics

• forensic acquisition applied to the course scenario, expected behavior, dependencies, controls, risks, and evidence.
• storage media applied to the course scenario, expected behavior, dependencies, controls, risks, and evidence.
• file-system artifacts applied to the course scenario, expected behavior, dependencies, controls, risks, and evidence.
• operating-system evidence applied to the course scenario, expected behavior, dependencies, controls, risks, and evidence.
• data recovery applied to the course scenario, expected behavior, dependencies, controls, risks, and evidence.

Instructor Demonstration

The instructor traces an investigation team using the CHFI v10 body of knowledge to preserve evidence, reconstruct activity, and support internal or legal decisions. The walkthrough connects tools, configurations or analysis logic, system messages, decisions, and evidence captured in the CHFI v10 case plan, acquisition record, event timeline, and investigation report. It also tests the exception where a basic control passes but operating-system evidence fails because file-system artifacts data, configuration order, or dependency assumptions differ.

Hands-On Exercise

Complete a controlled, authorized EC-Council exercise covering Acquisition, Storage Media, File Systems, Operating Systems, and Recovery and preserve the verified result in the CHFI v10 case plan, acquisition record, event timeline, and investigation report.

1. Confirm scope, authorization, prerequisites, versions, identities, dependencies, and acceptance criteria.
2. Execute the workflow while recording settings, outputs, events, decisions, and system messages.
3. Test normal behavior, one boundary condition, and the stated exception without targeting real third-party systems.
4. Document corrections, evidence, ownership, retest criteria, rollback or recovery, and handover actions.

Scenario Analysis

• Identify which object, service, policy, setting, or sequence most strongly influences forensic acquisition.
• Compare two defensible responses and explain technical, security, operational, legal, and support trade-offs.
• Determine how the CHFI v10 case plan, acquisition record, event timeline, and investigation report should be approved, retained, retested, and updated.

Troubleshooting Guidance

Start where expected behavior first differs from the observed result. Check authorization, prerequisites, identity, configuration order, data quality, version compatibility, connectivity, status, resource limits, and evidence separately. Treat “a basic control passes but operating-system evidence fails because file-system artifacts data, configuration order, or dependency assumptions differ” as a hypothesis until logs, settings, captured outputs, and retest outcomes confirm the cause.

Validation Checklist

• Required components, identities, permissions, settings, safety controls, and dependencies are present.
• The CHFI v10 case plan, acquisition record, event timeline, and investigation report connects each conclusion to objective, reviewable evidence.
• Normal processing, a boundary condition, dependency behavior, and the stated exception were tested.
• Corrections, ownership, retest criteria, rollback or recovery, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply Acquisition, Storage Media, File Systems, Operating Systems, and Recovery, explain the resulting security, governance, business, or operational behavior, and defend the outcome through the CHFI v10 case plan, acquisition record, event timeline, and investigation report.