CF-L3 / CCFT study plan
CF-L3 / CCFT · Give each week a clear focus.
8 weeks · About 7 hours per week
Evidence Identification, Acquisition and Preservation
Rank evidence sources by volatility and justify a collection order for a mixed live-memory-plus-disk scenario
Select the correct hardware, software, or inline write-blocker for each media type and defend the choice
Compute and verify MD5/SHA-256 hashes across acquisition, transport, and storage to prove integrity
Construct chain-of-custody entries for physical media and for provider-held cloud data that would survive cross-examination
Distinguish logical, physical, sparse, and targeted acquisitions and state when each is defensible
Your checkpoint
A one-page evidence acquisition SOP covering volatility order, write-blocker selection, hashing, and custody transfer, stress-tested against 10 written scenarios with at least 8 correct justifications.
Operating System and Application Artifacts
Map Windows registry hives to the user behaviors they evidence (USB connections, Run/RunMRU, ShellBags, autoruns)
Interpret Security, System, and Sysmon event IDs to reconstruct logon sessions and process execution chains
Normalize timestamps from $MFT, $UsnJrnl, and Prefetch into a single unified timeline and explain each timestamp's meaning
Identify Linux access and persistence artifacts in auth.log, cron, systemd units, and shell history
Your checkpoint
A normalized timeline of at least 50 events drawn from a synthetic or public training image, with every event tied to its source artifact and a one-line interpretation of what it proves.
File Systems and Storage Media Analysis & Operating System and Application Artifacts
Parse NTFS structures ($MFT records, $LogFile, $Bitmap, alternate data streams, INDX) and state what each can and cannot establish
Explain file creation, deletion, and slack-space behavior at the structure level in NTFS, FAT/exFAT, and ext4
Recover deleted content and metadata, then document why full recovery is or is not possible in each case
Correlate file system metadata with operating system artifacts to resolve timestamp inconsistencies (timestomping indicators)
Your checkpoint
A written structure-level walkthrough tracing one file through creation and deletion in both NTFS and ext4, paired with a one-page file-system artifact reference sheet.
Forensic Fundamentals, Legal and Ethical Considerations
Differentiate search authorization mechanisms (warrant, consent, subpoena, exigent circumstances) and match each to a fact pattern
Apply admissibility standards and recognized good-practice principles to examiner decisions and tool validation
Connect each procedural step to the documentation that makes it defensible in court
Resolve ethical conflicts such as scope creep, conflicts of interest, and data minimization with a stated course of action
Your checkpoint
A timed 60-question mixed assessment across domains 1, 2, 3, and 4, scoring at least 75 percent, plus a written error log classifying every miss by cause.
Network Forensics and Log Analysis
Decode packet captures at the protocol level (DNS, HTTP, SMB, TLS handshake) to identify command-and-control and exfiltration patterns
Reconstruct a session timeline from firewall, proxy, and flow-record logs while reconciling clock skew between sources
Attribute activity to an internal host using web server, DHCP, and VPN logs
Rank log sources by evidentiary weight and account for retention gaps in the final narrative
Your checkpoint
A two-page written network intrusion narrative reconstructed from a synthetic packet capture plus firewall and proxy logs, with an evidence table citing packet numbers and specific log lines.
Mobile, Cloud and Emerging-Source Forensics & Network Forensics and Log Analysis
Extract and interpret mobile artifacts (message databases, location history, app sandbox data) from logical and file-system-level extractions
Apply the shared-responsibility model to determine what a cloud provider can and cannot produce under legal process
Preserve and authenticate cloud-native and emerging-source evidence such as SaaS audit logs, container images, and IoT device data
Document the limitations of each acquisition method (logical, file system, chip-off, JTAG) where it affects conclusions
Your checkpoint
A mobile and cloud acquisition decision matrix mapping source type to method to obtainable artifacts to limitations, applied and justified across six scenarios.
Reporting, Documentation and Expert Testimony & Mobile, Cloud and Emerging-Source Forensics
Structure an expert report with explicit scope, methodology, findings, limitations, and appendix conventions
Restate technical findings in plain language for a non-technical decision maker without losing accuracy
Prepare direct and cross-examination answers that separate observed fact, inference, and opinion
Apply disclosure obligations and handle exculpatory findings transparently
Your checkpoint
A complete mock expert report of five to eight pages based on one earlier lab, accompanied by a recorded ten-minute mock testimony scored against a self-built rubric.
Reporting, Documentation and Expert Testimony & Forensic Fundamentals, Legal and Ethical Considerations
Complete a full-length timed mock exam and score results by domain
Close the three weakest domain gaps with targeted drills and re-testing
Reproduce from memory a one-page summary of legal standards and procedural flow
Finalize an exam-day plan covering pacing, flagging strategy, and common terminology traps
Your checkpoint
A mock exam result of at least 80 percent overall with no single domain below 70 percent, plus a one-page exam-day execution plan.
Milestones
Week 2: Acquisition SOP and the 50-event normalized timeline are both complete, and you can defend each timeline entry's source artifact without notes.
Week 4: Midpoint assessment scored at least 75 percent across domains 1 through 4, with an error log showing a named cause for every miss.
Week 6: All technical domains have been studied at least once; the mobile and cloud decision matrix is complete for all six scenarios.
Week 8: Full mock exam at or above 80 percent overall, no domain below 70 percent, and a written exam-day plan in hand.