Comprehensive Technical Explanation:
Fireware OS enforces a defined, low-level packet processing pipeline where incoming packets traverse multiple protective inspection stages before reaching the user-defined policy table. Default Threat Protection (which includes Default Packet Handling, Blocked Ports, Blocked Sites, and Flood/Dos Protections) operates at the lowest ingress layers of the network stack.
When a packet arrives at an interface, Fireware immediately performs sanity checks:
1. It validates IP headers for anomalies, malformed headers, and spoofed addresses.
2. It checks whether the source IP address matches the dynamic or static Blocked Sites list.
3. It evaluates whether the packet constitutes a port scan, address probe, or flood attack under Default Packet Handling.
4. It verifies whether the destination port is on the Blocked Ports list.
Only after a packet successfully passes these Default Threat Protection threshold evaluations is it forwarded to the stateful firewall engine to be matched against firewall policies in top-down sequential order. If Default Threat Protection drops a packet, it never reaches policy evaluation. Therefore, the statement that packets are processed by policies before Default Threat Protection is False.
[Reference: WatchGuard Network Security Essentials — Networking, Policies, and NAT: Fireware Packet Processing Architecture and Threat Protection Order., ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――]