detection-rules
Loading

FortiGate Configuration File Downloaded

This rule detects the download of a FortiGate device configuration file. Configuration exports contain sensitive data including administrator password hashes, LDAP bind credentials, VPN pre-shared keys, routing tables, and firewall policies. Threat actors exploiting CVE-2026-24858 have been observed exporting the full device configuration immediately after gaining access to harvest credentials and map the internal network.

Rule type: eql
Rule indices:

  • logs-fortinet_fortigate.*

Rule Severity: medium
Risk Score: 47
Runs every: 5m
Searches indices from: now-9m
Maximum alerts per execution: ?
References:

Tags:

  • Use Case: Threat Detection
  • Tactic: Collection
  • Resources: Investigation Guide
  • Domain: Network
  • Data Source: Fortinet
  • Data Source: Fortinet FortiGate

Version: ?
Rule authors:

  • Elastic

Rule license: Elastic License v2

This alert indicates that a FortiGate device configuration file was downloaded. Configuration files contain highly sensitive information including administrator credentials, LDAP/RADIUS secrets, VPN pre-shared keys, certificate private keys, and the complete network topology.

In the FG-IR-26-060 campaign, threat actors exported the full device configuration shortly after creating rogue administrator accounts, using the harvested credentials for lateral movement and to maintain access through alternative channels.

  • Review source.user.name to determine which account initiated the download and fortinet.firewall.ui for the source interface and IP address (e.g., GUI, CLI, or API). Verify whether this administrator is authorized to export device configurations.
  • Check whether a scheduled backup process or configuration management tool performed this action. Look for preceding SSO login events or administrator account creation events on the same device and determine whether the downloading account was recently created.
  • Check observer.name to identify which device had its configuration exported and search for configuration download events across other FortiGate devices in the fleet.
  • Check for firewall policy changes, VPN configuration modifications, or additional admin account creation after the download. Determine whether any credentials from the configuration have been used for lateral movement.
  • Scheduled configuration backups performed by FortiManager, Ansible, or other automation tools.
  • Administrator-initiated backups during planned maintenance or before firmware upgrades.
  • Configuration audits or compliance checks that require config export.
  • If unauthorized, treat all credentials in the configuration as compromised. Rotate all passwords, pre-shared keys, LDAP bind credentials, and RADIUS secrets contained in the configuration.
  • Revoke and reissue any certificates whose private keys were included in the export.
  • Audit the administrator account that performed the download for compromise and check for other indicators of compromise on the device (rogue admins, policy changes).
  • If the activity is expected, document the backup activity and verify it was performed through an authorized process. Ensure configuration backups are stored securely with appropriate access controls.
any where event.dataset == "fortinet_fortigate.log" and
    event.code == "0100032095" and
    fortinet.firewall.action == "download"

Framework: MITRE ATT&CK