Study guide

3.1 Flow-Based vs Proxy-Based Inspection Modes

Fortinet FCP - FortiGate 7.6 Administrator Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

About the Fortinet FCP FortiGate Administrator Exam (FCP_FGT_AD-7.6) How to Study and Prepare for FortiOS 7.6 Certification

2 Chapter 1: Deployment & System Configuration

1.1 Initial Configuration, GUI/CLI Management & Admin Profiles 1.2 FortiGuard Services, Licensing & Firmware Upgrades 1.3 Virtual Domains (VDOMs) & System Operation Modes 1.4 Fortinet Security Fabric & Device Integration 1.5 High Availability (FGCP) Configuration & Election 1.6 System Logging, Diagnostics & Troubleshooting Tools 1.7 FortiGate CNF, FortiGate VM in Public Cloud & FortiSASE Administration

3 Chapter 2: Firewall Policies & NAT

2.1 Firewall Policy Matching & Object Management 2.2 Source Network Address Translation (SNAT) & IP Pools 2.3 Destination NAT (DNAT), Virtual IPs (VIPs) & Central NAT

4 Chapter 3: Content Inspection & Security Profiles

3.1 Flow-Based vs Proxy-Based Inspection Modes 3.2 Antivirus & FortiSandbox Integration 3.3 Intrusion Prevention System (IPS) Configuration 3.4 Web Filtering & Static URL Management 3.5 Application Control & Traffic Shaping 3.6 DNS Filtering & Botnet C&C Protection

5 Chapter 4: Authentication & FSSO

4.1 Local & Remote Authentication (LDAP, RADIUS, 2FA) 4.2 Fortinet Single Sign-On (FSSO) Architecture & Modes

6 Chapter 5: Routing & SD-WAN

5.1 Static Routing, Policy Routes & Reverse Path Forwarding 5.2 SD-WAN Architecture, Performance SLAs & Balancing Rules

7 Chapter 6: SSL VPN & IPsec VPN

6.1 SSL VPN Web Mode & Tunnel Mode Configuration 6.2 IPsec VPN Phase 1 & Phase 2 Fundamentals 6.3 Advanced IPsec Topologies (Hub-and-Spoke & ADVPN)

8 Chapter 7: SSL/SSH Inspection

7.1 SSL Certificate Inspection vs Deep SSL/SSH Inspection 7.2 CA Certificates, Port Handling & Inspection Exemptions

3.1 Flow-Based vs Proxy-Based Inspection Modes

Key Takeaways Explain This Topic AI

Flow-based inspection examines network traffic packet-by-packet using the IPS engine without buffering complete files, offering ultra-low latency and hardware acceleration via SPU/NPU offloading.

Proxy-based inspection terminates client and server connections using the proxy worker daemon (wad), buffering full payloads to provide comprehensive protocol inspection and feature support.

FortiOS 7.6 supports configuring inspection mode per firewall policy or per-VDOM, allowing administrators to optimize performance for high-throughput traffic and apply deep proxy scanning where needed.

Proxy mode is mandatory for advanced capabilities like inserting custom HTTP headers, ICAP offloading, and displaying full client replacement messages after a connection has established.

Flow mode handles malware detection mid-stream by resetting TCP connections (sending RST packets) rather than generating client-side block pages.

Last updated: July 2026

3.1 Flow-Based vs Proxy-Based Inspection Modes

FortiOS security profiles operate under two primary inspection paradigms: Flow-based inspection and Proxy-based inspection . Understanding the architectural differences, engine mechanics, feature availability, and performance characteristics of these modes is essential for Fortinet FCP certification and enterprise security design.

Architectural Comparison

In FortiOS 7.6, security profiles evaluate network traffic to detect threats, enforce content access controls, and monitor application usage. The underlying inspection mode determines how FortiGate processes packets as they move through the system.

1. Flow-Based Inspection Mode

Flow-based inspection analyzes network traffic on a packet-by-packet or stream-chunk basis. Rather than buffering the entire payload or holding back an entire file download, the IPS engine examines incoming packets as they arrive in memory buffers.

Engine Mechanics : Traffic passes through the IPS engine, which uses specialized pattern-matching algorithms to scan for malware signatures, protocol anomalies, and restricted web content in real time.

Hardware Acceleration : Flow inspection leverages Fortinet Security Processing Units (SPUs) and Network Processors (NP7/NPU) alongside Content Processors (CP9) via nTurbo offloading. This bypasses the main CPU for established flows once initial session security checks pass.

Latency & Performance : Delivers ultra-low latency and maximum throughput. It is ideal for time-sensitive applications such as VoIP, real-time video streaming, and high-gigabit internal network segments.

Limitations : Because complete files are not buffered in memory, FortiOS cannot perform deep protocol modifications (such as injecting custom HTTP headers) or unpack complex multi-nested archives beyond fixed memory buffers. If a virus is detected mid-stream after initial HTTP headers have been delivered to the client, FortiGate cannot present an HTML block page; instead, it sends a TCP Reset ( RST ) packet to tear down the connection.

2. Proxy-Based Inspection Mode

Proxy-based inspection establishes the FortiGate as a dual-session intermediary (a full proxy). The client connects to the FortiGate, and the FortiGate originates a separate connection to the destination server.

Engine Mechanics : Traffic is handled by proxy worker processes managed by the WAD (Web Application Defender / Wireless Access Controller / Proxy) daemon. The FortiGate buffers the complete application layer payload (such as an entire HTTP response, email attachment, or FTP file download) in memory before executing security profile scanning.

Deep Protocol Inspection : Once the full object is assembled in the buffer, FortiGate inspects the content, unpacks multi-layer compressed archives, evaluates HTML body scripts, and checks headers.

Latency & Resource Impact : Requires higher RAM allocations and CPU overhead due to connection state tracking and payload buffering. Throughput is lower compared to flow mode, and initial packet arrival at the client is delayed until payload buffering and scanning complete.

Advanced Capabilities : Proxy mode enables advanced features including HTTP header modification/insertion, ICAP (Internet Content Adaptation Protocol) offloading to external DLP/AV servers, explicit web proxy, and consistent delivery of client replacement messages regardless of session state.

Inspection Mode Selection in FortiOS 7.6

In FortiOS 7.6, inspection modes can be specified flexibly:

System / VDOM Level : Set the default inspection mode for the VDOM under config system settings .

Firewall Policy Level : Override or explicitly set the inspection-mode per firewall policy ( flow or proxy ). This permits running high-speed flow-based rules alongside targeted proxy-based inspection policies on the same FortiGate unit.

  • Feature / Metric Flow-Based Inspection Proxy-Based Inspection
  • Primary Engine IPS Engine ( ipsengine ) Proxy Worker Daemon ( wad )
  • Data Handling Packet-by-packet / Stream chunk Full payload buffering in RAM
  • Hardware Acceleration Supported (SPU / NPU / nTurbo / CP9) Limited (Partial SSL offload to CP9)
  • Latency Impact Minimal / Ultra-low latency Higher (Delay introduced during buffering)
  • RAM & CPU Overhead Low to Moderate High (Proportional to active proxy sessions)
  • Mid-Stream Block Action TCP Reset ( RST ) packet Custom HTML Client Replacement Page
  • HTTP Header Alteration Not Supported Supported (e.g., add X-Forwarded-For )
  • ICAP Offloading Not Supported Supported
  • Explicit Web Proxy Not Supported Supported
  • Supported Profiles AV, IPS, Web Filter, App Control, DNS AV, IPS, Web Filter, App Control, CASB, Video Filter
  • CLI Configuration Examples
  • Setting VDOM Default Inspection Mode to Proxy config system settings
  • set inspection-mode proxy
  • end
  • Configuring a Proxy-Based Firewall Policy with Security Profiles config firewall policy
  • edit 10
  • set name "Corp_Proxy_Web_Access"
  • set srcintf "port2"
  • set dstintf "port1"
  • set srcaddr "Corp_LAN_Subnet"
  • set dstaddr "all"
  • set action accept
  • set schedule "always"
  • set service "HTTP" "HTTPS"
  • set inspection-mode proxy
  • set utm-status enable
  • set av-profile "default-proxy"
  • set webfilter-profile "Strict_Web_Filter"
  • set ssl-ssh-profile "deep-inspection"
  • set nat enable
  • next
  • end
  • Configuring a Flow-Based Firewall Policy for High Throughput config firewall policy
  • edit 20
  • set name "HighSpeed_Flow_Policy"
  • set srcintf "port2"
  • set dstintf "port1"
  • set srcaddr "Server_Subnet"
  • set dstaddr "all"
  • set action accept
  • set schedule "always"
  • set service "ALL"
  • set inspection-mode flow
  • set utm-status enable
  • set av-profile "default-flow"
  • set ips-sensor "Critical_Servers_IPS"
  • set nat enable
  • next
  • end

Loading diagram... Packet Traversal: Flow-Based vs Proxy-Based Inspection