FortiGate Architecture and Administration
FortiGate is a next-generation firewall running FortiOS — Fortinet's proprietary operating system. Administration interfaces: GUI (HTTPS web interface — port 443 or custom HTTPS port), CLI (SSH or console — FortiOS CLI uses Cisco-like structure: config system interface, show full-configuration, diagnose commands). Configuration model: FortiGate uses a hierarchical configuration structure — top-level objects (interfaces, addresses, services, schedules) are referenced by security policies. FortiGuard: Fortinet's cloud-based threat intelligence subscription — provides real-time updates for IPS signatures, antivirus definitions, web filtering categories, application control signatures, and email filtering. Licensing: FortiCare (hardware support), FortiGuard subscriptions (UTM features — without active subscriptions, IPS, AV, and web filtering use last downloaded signatures). Interfaces: physical, VLAN (802.1Q sub-interfaces), LAG (Link Aggregation), redundant interfaces (active/passive — failover if primary goes down), software switch (bridge multiple ports), VPN interfaces (IPSec tunnel, SSL-VPN).
Security Policies and Traffic Flow
FortiGate security policies control which traffic is permitted between interfaces. Policy components: Source (interface + address object), Destination (interface + address object), Service (protocol/port definitions), Action (ACCEPT or DENY), Security Profiles (applied to accepted traffic for inspection). Policy match order: policies are evaluated top-down, first match wins — more specific policies must appear before broader policies. Implicit deny-all at the bottom (not visible but always present). Address objects: FQDN objects resolve DNS in real time — FortiGate periodically resolves the FQDN and updates the associated IP in policy. Service objects: predefined TCP/UDP port definitions (HTTP = TCP 443, SSH = TCP 22) or custom. SNAT (Source NAT): outbound traffic translated to FortiGate's public IP — overload mode (PAT), fixed port range, IP pool. DNAT (Destination NAT): inbound traffic redirected to internal servers — Virtual IP (VIP) objects map public IP:port to private IP:port. Central SNAT: manage all SNAT rules in one place rather than per policy.
Unified Threat Management (UTM) Security Profiles
FortiGate's security profiles apply deep inspection to allowed traffic. Application Control: identify and control applications by signature (Layer 7 — recognises Facebook, Skype, BitTorrent regardless of port). Action per category: allow, monitor, block, quarantine. IPS (Intrusion Prevention System): detect and block exploit attempts — signature-based (known attacks) and anomaly-based (protocol violations, rate anomalies). IPS profiles assign severity-based actions (alert, drop, reset, quarantine). Antivirus: scan HTTP, HTTPS (with SSL inspection), FTP, SMTP, IMAP, POP3 for malware — flow-based (fast, scan as packets arrive) vs proxy-based (complete file before scanning — more thorough, higher latency). Web Filtering: FortiGuard URL database categorises URLs — block categories (adult, gambling, malware-hosting), allow business categories, apply override for specific URLs. SSL/TLS Deep Inspection: FortiGate acts as man-in-the-middle — decrypts, inspects, re-encrypts traffic. Requires certificate deployment to clients so they trust FortiGate's signing certificate. DNS Filter: block access to malicious domains before TCP connection is established — faster than URL filtering.
VPNs and High Availability
VPN configuration for NSE4. IPSec VPN: two phases — IKE Phase 1 (authenticate peers, establish secure channel: authentication method PSK or certificate, encryption AES-256, DH group 19+ recommended for PFS), IKE Phase 2 (negotiate IPSec tunnel parameters, create the SA pairs for data encryption). Route-based vs policy-based VPN: route-based (virtual tunnel interface, routing controls traffic through tunnel — more flexible, recommended for Fortinet), policy-based (traffic selectors in the policy — simpler but less flexible). SSL-VPN: remote access — web-mode (portal in browser, access web resources and RDP apps), tunnel-mode (FortiClient installs virtual adapter, full network access). Two-factor authentication for SSL-VPN: FortiToken (hardware TOTP token), FortiToken Mobile (smartphone app), email OTP. High Availability: Active-Passive (primary handles traffic, secondary standby — heartbeat monitors primary, automatic failover on failure), Active-Active (both units process traffic — improves throughput, more complex). HA synchronisation: configuration, sessions, and routing tables synchronised via dedicated HA heartbeat interfaces.