Malware and Memory Forensics — Lesson 2: Acquisition, File Systems, Operating Systems, and Artifact Preservation

Learning Objectives

• Explain the structures, services, data, settings, roles, and dependencies governing Forensic Acquisition and Disk Images.
• Implement and validate File Systems, Operating-System Artifacts, and Hash Validation and Preservation Controls using reviewable evidence.
• Evaluate the condition where a control passes a basic check but fails during Operating-System Artifacts because File Systems data, version, or dependency assumptions differ and select a proportionate corrective response.

Detailed Topics

• Forensic Acquisition applied to the course scenario, expected behavior, dependencies, controls, and evidence.
• Disk Images applied to the course scenario, expected behavior, dependencies, controls, and evidence.
• File Systems applied to the course scenario, expected behavior, dependencies, controls, and evidence.
• Operating-System Artifacts applied to the course scenario, expected behavior, dependencies, controls, and evidence.
• Hash Validation and Preservation Controls applied to the course scenario, expected behavior, dependencies, controls, and evidence.

Instructor Demonstration

The instructor traces an investigation team must preserve evidence integrity, reconstruct events, distinguish facts from hypotheses, and support legal or internal decision-making. The walkthrough connects tools, configuration or analysis logic, system messages, decisions, and evidence captured in the memory-image log, process and network timeline, malware indicators, and forensic report. It also tests the exception where a control passes a basic check but fails during Operating-System Artifacts because File Systems data, version, or dependency assumptions differ.

Hands-On Exercise

Complete a controlled, authorized EC-Council exercise covering Acquisition, File Systems, Operating Systems, and Artifact Preservation and preserve the verified result in the memory-image log, process and network timeline, malware indicators, and forensic 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 memory-image log, process and network timeline, malware indicators, and forensic 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 control passes a basic check but fails during Operating-System Artifacts because File Systems data, version, 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 memory-image log, process and network timeline, malware indicators, and forensic 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, File Systems, Operating Systems, and Artifact Preservation, explain the resulting security or operational behavior, and defend the outcome through the memory-image log, process and network timeline, malware indicators, and forensic report.