GNFA logo
Focused certification exam prep
Start practice

GNFA Exam Domains 2026: Complete Guide to All 8 Content Areas

TL;DR
  • The GIAC Network Forensic Analyst (GNFA) objective list names exactly eight domains, and GIAC publishes no percentage weights for them.
  • The exam has 66 questions in 3 hours, mixing multiple-choice items with hands-on CyberLive tasks; 70% is the minimum passing score.
  • The exam is open book with hardcopy materials, so a well-built index is a real study deliverable.
  • FOR572 is the SANS course aligned with this certification, but training is optional and there are no formal prerequisites.

How to Read the GNFA Objective List

The GIAC Network Forensic Analyst (GNFA) certification validates the ability to examine network evidence: packet captures, flow records, proxy logs, wireless traffic, and the logging infrastructure that surrounds them. GIAC publishes its scope under "Exam Certification Objectives & Outcome Statements," and the headings fall into eight domains, listed here in the issuer's published order:

  1. Common Network Protocols
  2. Encryption and Encoding
  3. NetFlow Analysis and Attack Visualization
  4. Network Architecture
  5. Network Protocol Reverse Engineering
  6. Open Source Network Security Proxies
  7. Security Event and Incident Logging
  8. Wireless Network Analysis

Two caveats matter before you build a plan. First, GIAC does not publish percentage weights for these domains in the objective list, so any article claiming "Domain 3 is 20% of the exam" is inventing a number. Second, the assigned attempt's objectives, format, and passing score at the GIAC attempts page take precedence over any third-party summary, including this one. Verify them when you activate your attempt.

If you are new to the credential itself, our overview pages What Is GNFA Certification? and GNFA Certification cover the basics. This guide goes deeper on what each domain asks of you.

Exam Mechanics That Shape Domain Prep

Domain preparation only makes sense against the exam's actual structure. GIAC administers the GNFA as a single proctored, web-based exam through Pearson VUE (onsite) or ProctorU (remote), subject to attempt-specific eligibility.

ElementGNFA Detail
Total questions66
Time limit3 hours, covering the complete exam including CyberLive
Question typesMultiple-choice plus performance-based CyberLive tasks
Minimum passing score70%
Reference policyOpen book: hardcopy books, notes, and an index only; no internet or personal electronic references
Tools in the exam engineOn-screen calculator and scratch notepad
Answer changesSubmitted answers cannot be changed
Breaks15 minutes of break time allowed
Attempt window120 days from activation
Fees$999 certification attempt, $899 retake, $399 official practice exam (excluding sales tax; SANS tuition separate)

Three of these details change how you study. The 3-hour limit includes CyberLive, so hands-on tasks compete with multiple-choice items for the same clock. Answers cannot be changed once submitted, which rewards careful reading over speed-clicking. And because the exam is open book, your index is part of your performance: a topic you can locate in 20 seconds is worth more than one you half-remember. For more on pricing and renewal, see our GNFA certification cost breakdown; for the score threshold, see GNFA passing score.

Open book is not easy mode: Materials resembling practice or exam questions and answers are prohibited, and with 66 questions in 3 hours you cannot afford to research every item. Treat reference materials as a way to confirm details such as field names, flag values, and command syntax, not to learn concepts mid-exam.

Domain 1: Common Network Protocols

This is the foundation on which every other domain rests. Network forensics is, at its core, the discipline of knowing what normal protocol behavior looks like so you can recognize what is abnormal, malformed, or abused.

Common Network Protocols

You need packet-level fluency, not just conceptual familiarity with the protocol stack.

  • Reading headers and fields for IP, TCP, UDP, and ICMP, including how they behave in scans and anomalies
  • Application protocols commonly seen in investigations, such as DNS, HTTP, and email-related traffic
  • Distinguishing legitimate protocol use from tunneling, covert channels, and misuse
  • Filtering and dissecting captures with tcpdump and Wireshark-style tooling

Practical tip: practice answering "what would this field look like if it were abused?" rather than only "what does this field mean?" Questions in this domain tend to reward the investigator's mindset. The public FOR572 introductory lab on tcpdump and Wireshark is a free way to build this muscle, though it assumes the FOR572 SIFT Workstation VM and warns that results may vary on other VMs.

Domain 2: Encryption and Encoding

Investigators constantly encounter traffic that is obscured, whether by legitimate encryption or by an attacker's encoding. This domain covers how to tell the two apart and what evidence remains useful when payloads are not readable.

Encryption and Encoding

Know the difference between hiding content and merely reshaping it.

  • Encoding schemes versus true encryption, and how to recognize common encodings in captured data
  • What TLS-protected sessions still reveal through metadata, handshake details, and timing
  • Why encrypted traffic shifts investigations toward flow data, logs, and endpoint or proxy evidence
  • Recognizing obfuscated command-and-control or exfiltration that relies on encoding

A recurring theme: when you cannot read the payload, you reason from what you can observe. Candidates who treat encryption as a dead end struggle here; candidates who ask "what does the surrounding evidence tell me?" do well.

Domain 3: NetFlow Analysis and Attack Visualization

Flow records summarize who talked to whom, when, for how long, and how much. They are lightweight, retainable at scale, and invaluable when full packet capture is unavailable.

NetFlow Analysis and Attack Visualization

Think in terms of patterns across many records rather than individual packets.

  • What flow records contain and what they deliberately omit compared to full packet capture
  • Using flow data to identify scanning, beaconing, data exfiltration, and lateral movement
  • Aggregation and filtering to surface anomalies in large datasets
  • Visualizing relationships and timelines so an attack narrative becomes visible

This domain pairs naturally with Domain 7. Flow data tells you that a host talked to something unusual; logs tell you what that host was doing. Learn to move between the two views fluently.

Domain 4: Network Architecture

You cannot find evidence if you do not know where it lives. Network architecture, in forensic terms, is the map of collection points and the devices that shape traffic.

Network Architecture

Understand how design choices determine what evidence exists.

  • Where sensors, taps, and span ports sit, and what each can and cannot see
  • The effect of NAT, load balancers, and segmentation on attribution and traffic visibility
  • Evidence sources across routers, switches, firewalls, and other infrastructure
  • Planning collection so that an investigation has the data it needs when an incident occurs

Expect scenarios where the correct answer depends on realizing that a given vantage point simply cannot observe a particular conversation. Thinking about the topology first often eliminates wrong choices quickly.

Domain 5: Network Protocol Reverse Engineering

This is the most distinctive domain in the GNFA objective list and the one most likely to separate prepared candidates from underprepared ones. When you meet an unfamiliar or custom protocol, you must derive its structure from captured traffic.

Network Protocol Reverse Engineering

The skill is inference from observation, which is exactly the kind of task that suits hands-on CyberLive-style questions.

  • Identifying message boundaries, length fields, delimiters, and type indicators in unknown traffic
  • Spotting structure by comparing multiple samples of the same protocol conversation
  • Decoding custom or malware-specific communications to understand what an implant is doing
  • Documenting protocol behavior so it can be turned into detection signatures
Why this domain deserves extra hours: Memorization does not help here. Fluency comes only from working through real captures by hand. Budget lab time, not just reading time, for this domain.

Domain 6: Open Source Network Security Proxies

Web proxies sit on the path between users and the internet, which makes their logs a rich evidence source. This domain focuses on open source proxy technology and what it records.

Open Source Network Security Proxies

Proxy evidence is often the easiest way to reconstruct what a user or implant actually requested.

  • How forward proxies operate and what their access logs capture
  • Reading proxy logs to trace browsing activity, downloads, and suspicious destinations
  • Using proxy and cache evidence to recover what was transferred
  • Interpreting proxy behavior alongside packet and flow evidence

As with the other evidence-centric domains, the key skill is correlation: a proxy log line becomes far more powerful when you can match it to a flow record and a packet capture of the same event.

Domain 7: Security Event and Incident Logging

Logs are the connective tissue of an investigation. This domain addresses how security events are generated, collected, and analyzed during incident response.

Security Event and Incident Logging

Know what logs exist, how reliable they are, and how to read them under time pressure.

  • Common log sources and formats across network and security devices
  • Centralized collection and why timestamps and time synchronization matter
  • Correlating events across multiple systems to build a coherent timeline
  • Recognizing gaps, tampering, and the limits of what logs can prove

Because this exam is open book, a strong index of log formats and field meanings pays off here. Practice finding the answer in your own notes quickly, not just knowing it exists.

Domain 8: Wireless Network Analysis

Wireless investigations bring their own frame types, security mechanisms, and attack patterns. The certification scope explicitly includes wireless analysis, and the objective list devotes a full domain to it.

Wireless Network Analysis

Wireless evidence differs from wired captures in what you can see and how you collect it.

  • Wireless frame types and how association, authentication, and data exchange appear in captures
  • Wireless security mechanisms and the weaknesses attackers exploit
  • Identifying rogue access points, deauthentication activity, and other wireless attacks
  • Collecting and interpreting wireless captures for investigative purposes

Candidates from wired-only backgrounds often underestimate this domain. Give it dedicated study time rather than assuming general protocol knowledge will carry you through.

Sequencing the Eight Domains

Since GIAC publishes no weights, the sensible approach is breadth first, then depth where your experience is thinnest. The SANS FOR572 course, which has six preparation sections, is the main published preparation path, but its sections are unweighted curriculum and do not establish exhaustive exam coverage or a one-to-one map to the eight domains. Training is optional and recommended, not required. Here is one way to sequence your own study across six weeks, tied to dependencies between domains:

Week 1

Protocol Foundations

  • Domain 1: packet-level review of core protocols
  • Domain 2: encodings versus encryption, and what metadata survives
Week 2

Where the Evidence Lives

  • Domain 4: map sensors, taps, and device visibility
  • Domain 3: flow records and attack visualization
Week 3

Correlation Sources

  • Domain 6: proxy logs and cache evidence
  • Domain 7: log sources, timelines, and correlation
Week 4

Hands-On Inference

  • Domain 5: protocol reverse engineering with real captures
  • Domain 8: wireless captures and attack patterns
Weeks 5-6

Integration and Index

  • Build and refine your hardcopy index while drilling mixed scenarios
  • Revisit your weakest domain and rehearse time management against the 3-hour limit

Domains 1 and 2 come first because every later domain assumes them. Domain 5 sits late because reverse engineering draws on protocol fluency, encoding knowledge, and architecture awareness all at once. For a fuller preparation framework, read our GNFA study guide, and for a realistic read on effort, see how hard the GNFA exam is.

Key Takeaway

Treat your index as a domain-by-domain deliverable. After finishing each domain, add entries for the commands, field names, and log formats you needed to look up. By exam week, your index should reflect your own weak spots, not a generic table of contents.

Where These Skills Show Up on the Job

The eight domains map to work done in security operations centers, incident response teams, and digital forensics practices. Flow analysis and proxy evidence support threat hunting; log correlation and architecture knowledge support incident scoping; protocol reverse engineering and wireless analysis support deeper investigations and malware understanding. Organizations that handle breach response, consult on forensics, or run mature detection programs are the natural employers of people with this skill set. For role-specific detail, see our pages on GNFA jobs and the GNFA salary guide, and for the value question, whether the certification is worth it.

Certification validity runs four years. Renewal requires 36 approved CPE credits earned during the active period (or a renewal exam) plus the standard $499 renewal fee. That ongoing requirement is a reminder that network forensics evolves, and the domains above are a foundation rather than a finish line.

When you are ready to test yourself against realistic question styles across all eight domains, try the GNFA practice tests, and review the GNFA requirements to confirm you have no eligibility surprises. Note that there are no formal certification prerequisites, though forensic techniques, networking, and Linux shell experience all support preparation.

Frequently Asked Questions

How many domains does the GNFA exam cover?

GIAC's published objective list for the Network Forensic Analyst (GNFA) contains eight domains: Common Network Protocols, Encryption and Encoding, NetFlow Analysis and Attack Visualization, Network Architecture, Network Protocol Reverse Engineering, Open Source Network Security Proxies, Security Event and Incident Logging, and Wireless Network Analysis.

Are the GNFA domains weighted by percentage?

GIAC does not publish official percentage weights in the objective list, so the domains are unweighted. Prepare across all eight rather than relying on any claimed weighting, and check the objectives attached to your assigned attempt on the GIAC attempts page.

What does the GNFA exam format look like?

It is one proctored, web-based exam with 66 questions and a 3-hour time limit, including multiple-choice questions and performance-based CyberLive tasks. The minimum passing score is 70%, and the time limit covers the entire exam, CyberLive included.

Can I bring notes and books to the GNFA exam?

Yes. The exam is open book with hardcopy books, notes, and an index. Internet access, personal electronic references, and materials resembling practice or exam questions and answers are prohibited. Because submitted answers cannot be changed, use your references to confirm details before you commit.

Do I need FOR572 training before taking the GNFA?

No. There are no formal certification prerequisites and training is optional, though SANS FOR572 is the associated course. Hands-on comfort with forensic techniques, networking, and the Linux shell helps, but those are preparation advice rather than eligibility requirements. See our GNFA training overview for options.

Ready to pass your GNFA exam?

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