Threat-Hunting Guide Shows How to Detect Attacks on FortiGate Appliances

· Original article ↗

Summary

Wiz outlines how defenders can use agentless FortiGate logs to hunt for suspicious logins, rogue admin accounts, certificate and NAT changes, configuration theft, malicious scripts, and unusual network traffic.

Key points

  • Virtual appliances are often internet-facing, highly privileged, and lack traditional endpoint agents, leaving defenders with limited visibility.
  • Wiz's agentless workload detection collects and parses local FortiGate logs for threat hunting and incident investigation.
  • The playbook details how to identify credential stuffing through failed and successful login events, unusual source IPs, and suspicious accounts.
  • It recommends correlating logins with admin-account creation, certificate changes, NAT or port-forwarding modifications, and configuration downloads.
  • FortiGate configuration exports can expose credentials and network details; attackers have used stolen configurations to access internal environments.
  • FortiManager script deployments and unexpected local outbound traffic, including ICMP, can reveal backdoors, lateral movement, or command-and-control activity.
  • The article describes enabling log ingestion and non-OS disk scanning to collect appliance logs in Wiz.

Article Details

Defense Focus
Use agentless collection and analysis of FortiGate and FortiManager logs to detect exploitation, credential abuse, persistence, configuration theft or tampering, suspicious network activity, and lateral movement.
Detection Methods
  • Correlate bursts of failed admin logins with successful logins, account lockouts, source IPs, login times, and expected geographic or account patterns.
  • Detect new local super_admin accounts and correlate account creation with recent SSO or unusual login events; flag disabled MFA and unrestricted trusthost settings.
  • Monitor local certificate additions, edits, or deletions and CLI certificate commands; correlate changes with suspicious logins, unexpected accounts, and maintenance windows.
  • Flag FortiCloud SSO logins using unexpected or disposable email addresses and correlate them with SSO account creation or deletion.
  • Detect new or modified VIP, DNAT, port-forwarding, and firewall-policy objects, especially unrestricted exposure or sensitive destination ports.
  • Identify configuration downloads or show full-configuration commands by unexpected users, soon after suspicious logins or account creation, or in unusual volume.
  • Monitor FortiManager script deployments for unexpected users, timing, target groups, directory traversal, shell commands, and references to /bin/ or /tmp.
  • Hunt both forwarded and local traffic for unusual destinations, ports, protocols, external connections from the firewall, and unexpected ICMP traffic.
  • Compare device type and operating system with observed network behavior to identify anomalous device activity.
Data Sources
  • FortiGate authentication logs, including login success, failure, and account-lockout events.
  • FortiGate configuration-change, admin-action, certificate, VIP, firewall-policy, and configuration-download logs.
  • FortiManager object-change and script-deployment logs.
  • FortiGate local and forwarded traffic logs, including device type and operating-system fields.
  • Cloud control-plane events and runtime signals correlated with appliance logs.
Rule Types
  • Wiz event queries for FortiGate and FortiManager events.
  • Built-in threat-detection rules using correlated appliance logs.
Platforms
  • Wiz platform with Agentless Workload Detection.
  • FortiGate appliances and FortiManager.
Defensive Actions
  • Enable Defend Agentless Workload Detection through the Preview Hub and verify workload or machine log ingestion in Event Management settings.
  • Enable Non-OS disk scanning so FortiGate logs are collected.
  • Review suspicious logins, newly created administrator accounts, certificate changes, configuration downloads, NAT changes, and script deployments together to establish event sequence and origin.
  • Investigate unexpected local traffic from FortiGate devices as well as forwarded traffic through them.
  • After a FortiGate compromise, rotate administrator credentials, API tokens, certificates, and other credentials integrated with the firewall, as recommended by the cited incident-response advisories.

Indicators of compromise

TypeIndicatorContext
EMAILadmin@attacker[.]localEmail value in the subject fields of an example attacker-generated FortiGate VPN certificate.
EMAILcloud-init@mail[.]ioEmail pattern identified by the article as observed in FortiCloud SSO attacks.
EMAILcloud-noc@mail[.]ioEmail pattern identified by the article as observed in FortiCloud SSO attacks.
EMAILsupport@openmail[.]proDisposable email address used in an observed FortiCloud SSO login preceding attacker-created administrator access.

MITRE ATT&CK

CVE

Threat Actors

Malware

Vendors

Products

Tools

Countries

Industries

Related Articles