Skip to main content

Fortinet FortiGate

The Fortinet integration reads FortiGate firewalls through the FortiOS REST API. It runs on an Integrator inside your network, so the firewall's management interface is never exposed to the CyberOptix CTEM Platform.

It is read-only. The integration never changes configuration. In multi-VDOM mode, every VDOM is collected.

What it collects​

SyncCollects
Configuration backupThe full configuration, with secrets stripped on the Integrator before it leaves your network, versioned whenever it changes; firewall policies in evaluation order, per VDOM
Configuration reviewEvery configuration backup and NAT sync is reviewed against the configuration review checks, and what they find is raised as vulnerabilities on the device
Network discoveryInterfaces (zone, VLAN, VDOM and VRF, link state), the networks they are addressed into, and each VDOM's routing table
Host discoveryARP entries and DHCP leases from every VDOM
Exposure correlationVirtual IPs and port forwards, and policies that source-NAT, so an address reachable from outside is tied to what sits behind it

What the firewall reports is kept as its own record, alongside hosts and subnets rather than written into them.

Create a read-only API token​

  1. Create an admin profile with Read access to every permission group and Read-Write to none.
  2. Create a REST API Admin with that profile. Restrict Trusted Hosts to the Integrator's address.
  3. Copy the API token FortiOS shows once when the admin is created.

The Integrator sends the token in an Authorization: Bearer header, never in a URL.

Connect it​

  1. Under Integrations, add Fortinet with the FortiGate's management hostname and the API token.
  2. In the integration's settings, assign the Integrator that can reach the management interface.
  3. Enable the syncs you want.

Certificates​

FortiGates ship with a self-signed management certificate. The first connection accepts it and records its fingerprint on the integration; every later connection must present the same certificate. If you replace the certificate, clear the pinned fingerprint in the integration's settings so the new one is recorded. A certificate issued by a trusted CA is verified normally and never pinned.