CFCE logo
Focused certification exam prep
Start practice

CFCE Exam Domains 2026: Complete Guide to All 7 Content Areas

TL;DR
  • The seven domains are IACIS's official core competency areas, from Pre-Examination Procedures through Presentation of Findings.
  • CFCE is a multi-stage process: four peer-review problems, a hard-drive practical, and a 100-question written test.
  • Both final components, the practical and the written test, each require at least 80%.
  • External candidates must document 72 hours of training aligned with the core competencies.

How the Seven Core Competency Areas Fit the Process

The Certified Forensic Computer Examiner credential is administered directly by the International Association of Computer Investigative Specialists (IACIS). Unlike many certifications built around a single proctored sitting, CFCE is a staged, performance-oriented process. The seven content areas are IACIS's official core competencies, and they run through every stage: the coached peer-review problems, the hard-drive practical, and the written knowledge test.

That structure changes how you should read a domain list. A topic like "File Systems" is not only a block of multiple-choice questions. It is also something you must demonstrate by working through a real image, documenting what you found, and defending your conclusions in writing. If you are new to the credential, the overview in What Is CFCE Certification? explains the basics before you dive into the domains here.

StageFormatTime AllowedThreshold
Peer-review problemsFour coached, scenario-based problems30 days eachCompleted with peer review and coaching
Hard-drive practicalIndependent examination of a drive30 daysAt least 80%
Written knowledge test100 questions14-day completion windowAt least 80%

Note that these are completion windows, not a single timed exam sitting. For a deeper look at what the threshold means, see CFCE Passing Score 2026: Exactly What You Need to Pass.

Domain 1: Pre-Examination Procedures

Everything a forensic examiner does well starts before the first byte is read. Pre-Examination Procedures covers the legal, procedural, and preparatory groundwork that protects the integrity of evidence and the admissibility of your findings. Candidates who treat this domain as "soft" material often lose points in the peer-review problems, where sloppy documentation is caught by reviewers.

Domain 1: Pre-Examination Procedures

Expect to demonstrate that you can set up and document an examination properly before analysis begins.

  • Legal authority and scope: understanding what you are authorized to examine and why it matters
  • Evidence intake, chain of custody, and documentation of the item as received
  • Write-protection and acquisition planning so source media is never altered
  • Hash verification of acquired images to establish integrity
  • Preparing a clean, validated forensic workstation and tool set
  • Contemporaneous note-taking that another examiner could use to repeat your work

In the peer-review problems, this domain surfaces as your case notes. Reviewers are not only checking whether you found the right artifact; they are checking whether your process is repeatable and defensible.

Domain 2: Computer Fundamentals

Computer Fundamentals is the conceptual bedrock. You cannot reason about a deleted file or a damaged partition table without understanding how data is represented, stored, and addressed. The written test leans on this domain for knowledge-style questions in true/false, multiple choice, and matching formats.

Domain 2: Computer Fundamentals

Know how data is represented and how hardware and boot processes shape what ends up on a drive.

  • Number systems and data representation, including binary, hexadecimal, and character encodings
  • How storage media are organized: sectors, clusters, and logical block addressing
  • The boot process and what firmware and boot code leave behind
  • Hardware components that matter to an examiner, including storage interfaces and media types
  • Byte ordering and how multi-byte values appear when you view raw data
  • Timestamps and how different systems record time

Hexadecimal fluency deserves special attention. Later domains assume you can read a hex view of a partition table or file system structure and interpret the values by hand, not just trust a tool's parsed output.

Why fundamentals pay off later: Questions in the partition and file system domains often hide a fundamentals question inside them, such as converting a little-endian value or calculating an offset. Weakness in Domain 2 quietly costs points in Domains 3 through 5.

Domain 3: Partition Schemes

Partition Schemes covers how a physical disk is divided into logical volumes and how you recognize, interpret, and recover those structures. Many candidates find this domain the first real leap from conceptual knowledge to hands-on analysis, because it requires reading raw structures rather than clicking through a tool.

Domain 3: Partition Schemes

Be able to identify the partitioning method in use and interpret its structures at the byte level.

  • The legacy master boot record layout, including the partition table entries and signature
  • GUID-based partitioning, its header, and its protective structure
  • Extended and logical partitions and how chained structures are followed
  • Locating the start and size of each volume from raw values
  • Recognizing unallocated space between partitions where data may remain
  • Detecting damaged, missing, or deliberately altered partition tables

A common practical scenario is an image with a corrupted or absent partition table. You are expected to find where the volumes begin using other evidence, then proceed with analysis. This is exactly the kind of problem where a working understanding of the structure beats memorizing a field list.

Domain 4: File Systems

File Systems is typically the heaviest conceptual domain for working examiners. It tests whether you understand how operating systems organize, name, allocate, and track files, and what that organization leaves behind for an investigator. You should be comfortable with the structures of the major file systems you are likely to encounter in casework.

Domain 4: File Systems

Understand allocation, metadata, and directory structures well enough to explain what a tool is telling you.

  • Volume boot records and the layout of key file system structures
  • How files are tracked: metadata records, directory entries, and allocation maps
  • Cluster allocation, slack space, and how file size relates to allocated space
  • What happens to metadata and content when a file is deleted
  • Timestamp behavior across file operations such as create, modify, access, and move
  • Comparing characteristics of different file system families

Slack space and deletion behavior are favorites for knowledge questions because they connect directly to evidence recovery. If you understand why content can persist after a directory entry is marked unused, many data recovery questions become straightforward.

Domain 5: Data Recovery

Data Recovery is where the previous three domains converge. Having identified the partitions and understood the file system, you must now retrieve information that is not readily visible: deleted files, fragments, and content in unallocated or slack space. This domain is heavily represented in the hard-drive practical, where you are expected to find and document what is actually on the drive.

Domain 5: Data Recovery

Demonstrate both tool-assisted and manual approaches to recovering and validating data.

  • Recovering deleted files using file system metadata when it still exists
  • File signature analysis and carving when metadata is gone
  • Identifying files whose extensions do not match their true content
  • Examining unallocated space and slack space for residual data
  • Handling compressed, encrypted, or otherwise obscured content at a conceptual level
  • Validating that recovered data is complete and attributing it to its source location

One discipline that separates strong candidates is verifying recoveries rather than assuming them. A carved file that opens but is incomplete, or a fragment mistaken for a whole document, is a documented finding that must be described accurately.

Domain 6: Windows Artifacts

Windows Artifacts reflects the reality that a large share of casework involves Windows systems. This domain tests your ability to locate and interpret the traces that user and system activity leave behind, and to reason about what those traces do and do not prove.

Domain 6: Windows Artifacts

Know where activity evidence lives and how to interpret it responsibly.

  • The registry: its structure, key hives, and what categories of information they hold
  • User activity evidence such as recently used items, shortcut files, and jump lists
  • Recycle Bin behavior and how deleted items are tracked
  • Web browsing and download history stored in user profiles
  • Evidence of external device usage and program execution
  • Event logs and other system-level records that corroborate activity

The interpretive skill matters as much as the location knowledge. An artifact showing a file was opened is not proof of who opened it or why. Peer-review reviewers look for careful language that separates observation from inference, a habit that carries directly into the final domain.

Domain 7: Presentation of Findings

Presentation of Findings is the domain candidates most often underestimate, and it is arguably the one that defines a professional examiner. Technical skill is only useful if you can communicate results accurately to investigators, attorneys, and courts. In CFCE, this competency is exercised constantly through the written reports in the peer-review problems.

Domain 7: Presentation of Findings

Convey technical results clearly, accurately, and without overstating what the evidence shows.

  • Structuring a forensic report with scope, methods, findings, and conclusions
  • Describing technical results so a non-technical reader can follow them
  • Distinguishing facts you observed from opinions you formed
  • Documenting limitations, assumptions, and anything you could not determine
  • Preparing for testimony and cross-examination of your methodology
  • Ethical obligations, including objectivity and avoiding advocacy for either side

Key Takeaway

Treat every peer-review problem as a rehearsal for a real report. Write each one as if it will be read by someone who cannot ask you questions, because in practice that is exactly who reads forensic reports.

Where Each Domain Gets Tested

Because the process spans multiple stages, the same domain appears in different forms. Understanding which stage emphasizes which skills helps you aim your preparation. The mapping below is a practical reading of how the competencies typically show up, not an official weighting.

DomainMost Visible InTypical Demand
Pre-Examination ProceduresPeer-review problemsProcess, documentation, integrity
Computer FundamentalsWritten testConceptual recall and calculation
Partition SchemesWritten test and practicalReading raw structures
File SystemsWritten test and practicalStructure and behavior knowledge
Data RecoveryHard-drive practicalHands-on recovery and validation
Windows ArtifactsPractical and written testLocation and interpretation
Presentation of FindingsPeer-review problemsClear, defensible reporting

The written test uses true/false, multiple choice, matching, and short essay or fill-in-the-blank items. The short-answer formats reward precise terminology, so practice stating definitions in your own words rather than only recognizing the right option. To gauge how demanding the whole process is, read How Hard Is the CFCE Exam? Complete Difficulty Guide 2026, and for what the numbers do and do not tell you, see CFCE Pass Rate 2026: What the Data Shows.

Independence is part of the exam: The final certification work must be completed independently, and candidates sign a notarized declaration that they received no assistance. Coached peer-review problems allow collaboration with reviewers, but the practical and written test do not. Plan your preparation so you can perform alone.

Sequencing Your Preparation by Domain

Rather than studying the seven domains in the order listed, many candidates do better by front-loading the foundations that everything else depends on, then layering on hands-on work. Here is one domain-driven sequence that matches how the skills build on each other. For a broader plan, the CFCE Study Guide 2026: How to Pass on Your First Attempt covers the full approach.

Weeks 1-2

Foundations: Domains 1 and 2

  • Build a documentation habit and practice case notes on every lab exercise
  • Drill hexadecimal, endianness, and sector and cluster arithmetic until it is automatic
Weeks 3-4

Structures: Domains 3 and 4

  • Parse partition tables and file system structures by hand in a hex viewer
  • Practice rebuilding a missing partition table on a practice image
Weeks 5-6

Recovery and artifacts: Domains 5 and 6

  • Recover deleted content with and without metadata, then validate each result
  • Work through registry, user activity, and Recycle Bin artifacts on a Windows image
Week 7

Integration: Domain 7 and review

  • Write a complete report from a practice image and have someone critique it
  • Run through practice questions across all seven domains

For quick refreshers close to your written test window, keep a condensed reference handy; the CFCE Cheat Sheet 2026: One-Page Review of Must-Know Facts is useful for this. You can also test your recall with the practice questions on the CFCE practice test site.

Who Values the Credential

The CFCE is aimed at practicing digital forensic examiners, so the employers who value it are those that put examiners in front of real evidence: law enforcement agencies, government and military investigative organizations, and private-sector forensic and incident-response practices. Because the certification demonstrates peer-reviewed, hands-on competence rather than only test-taking ability, it tends to carry weight with agencies that need examiners whose work will face scrutiny in legal proceedings.

If you are weighing the career side, see CFCE Jobs for the roles that look for this credential, CFCE Salary Guide 2026: Complete Earnings Analysis for compensation context, and Is the CFCE Certification Worth It? Complete ROI Analysis 2026 for the broader decision.

Eligibility, Cost, and Cycle Mechanics

A few logistics shape how you apply the domain knowledge above. External candidates, meaning those who did not come through IACIS Basic Computer Forensic Examiner (BCFE) training, pay $800 USD for external certification, which includes a study guide. For BCFE graduates, the initial certification cycle is included in course tuition. External candidates must document 72 hours of training aligned with the core competencies, and IACIS membership is not an eligibility requirement. Background-check requirements apply, with exceptions tied to government employment or clearances. External cycles begin in March and September.

If one final component does not go your way, a single failed component, either the practical or the written test, may be retaken once without charge in the next cycle. Failing both components fails the certification process. Details on prerequisites are in CFCE Requirements 2026: Eligibility, Prerequisites & How to Qualify, cycle timing is covered in CFCE Exam Dates 2026: Testing Windows, Deadlines & Scheduling, and the full fee picture is in CFCE Certification Cost 2026: Complete Pricing Breakdown.

Keeping the Credential Current

The seven domains do not stop mattering after you pass. CFCE certification renews every three years, and the renewal requirements keep your competency fresh: 40 documented hours of digital or computer forensics education, a third-year proficiency exercise, and qualifying professional activity. That activity can be three forensic examinations, relevant supervision or management, or three IACIS proficiency tests during the cycle. The renewal fee is $150 for nonmembers or for members who have not paid all three years of dues.

Start tracking early: Because renewal requires documentation of education hours and examinations, begin a simple log the day you certify. Reconstructing three years of training records at the last minute is a common and avoidable headache.

Frequently Asked Questions

What are the seven CFCE exam domains?

They are IACIS's official core competency areas: Pre-Examination Procedures, Computer Fundamentals, Partition Schemes, File Systems, Data Recovery, Windows Artifacts, and Presentation of Findings. Each is exercised across the peer-review problems, the hard-drive practical, and the written knowledge test.

Is the CFCE a single timed exam?

No. It is a multi-stage process: four coached peer-review problems with 30 days each, a 30-day hard-drive practical, and a 100-question written test with a 14-day completion window. These are completion windows, not one timed sitting.

What score do I need on the final components?

Both the hard-drive practical and the written knowledge test require at least 80%. Passing one but not the other means retaking the failed component once, free of charge, in the next cycle. Failing both fails the certification process.

What question formats appear on the written test?

The 100-question written test uses true/false, multiple choice, matching, and short essay or fill-in-the-blank questions. The short-answer formats reward precise terminology, so practice explaining concepts in your own words.

Do I need IACIS training or membership to sit for CFCE?

No. External candidates can pursue certification without membership, but they must document 72 hours of training aligned with the core competencies. BCFE graduates have their initial certification cycle included in course tuition. For background on the credential itself, see What Is CFCE?.

Ready to pass your CFCE exam?

Put this into practice with free CFCE questions across every exam domain.