FortiGate deny RFC1918 + bogon source addresses on WAN ingress

This guide gives you a copy-and-paste Fortinet FortiGate configuration for Egress hygiene (fortigate deny rfc1918 wan anti spoof), plus the rationale behind each line and a free SafeCadence analyzer that scores your existing config against this same best-practice template.

What this snippet does

This Fortinet FortiGate template implements FortiGate deny RFC1918 + bogon source addresses on WAN ingress. It’s been distilled from vendor documentation, NIST SP 800-41 / SP 800-53, and CISA hardening guidance — and battle-tested by SafeCadence on real production engagements.

The configuration template

You can browse and copy the live snippet (with one-click copy + citations) from the SafeCadence Config Templates Library:

▶ Open the live template (with copy button)

Why this matters

  • Reduces attack surface by enforcing explicit deny + logging.
  • Generates audit evidence automatically (logs hit on any blocked traffic).
  • Aligns with PCI DSS req. 1, NIST SP 800-41 Rev.1, CISA CPGs.

How to validate your config

Copy your existing Fortinet FortiGate running-config and paste it into the matching SafeCadence analyzer. The analyzer will tell you exactly which best-practice checks pass, which fail, and the per-finding fix:

Need help applying this in production?

SafeCadence offers paid engagements for Fortinet FortiGate hardening — change windows, validation, rollback, and knowledge transfer. Free 30-minute scoping consult.

📧 hello@safecadence.com

Related free tools