← Back to Integration
NETWORK SECURITY

Integration with Fortinet FortiManager Integration with SPOG.AI

SPOG.AI integrates with Fortinet FortiManager to centralize managed firewall inventory, ADOM and VDOM context, high-availability status, license information, and NAT translation visibility. The connector uses read-only JSON-RPC API access and enriches matching records in the SPOG.AI CMDB.

Key Features

CapabilityDescription
Managed Device InventoryImports FortiManager-managed firewall identity, model, serial number, management IP, and FortiOS version.
ADOM and VDOM ContextDiscovers ADOMs, devices, and VDOMs dynamically.
HA and License VisibilityCollects high-availability status and available antivirus and IPS license status.
NAT Translation DiscoveryCollects virtual IP, VIP group, and central DNAT translation data.
CMDB EnrichmentCorrelates Fortinet firewalls and translated IP services with SPOG.AI records.

How the Integration Works

The SPOG Appliance sends authenticated HTTPS requests to the FortiManager /jsonrpc endpoint using a bearer API token. It discovers ADOMs, managed devices, VDOMs, system and HA status, license status, and NAT translation tables, then normalizes and enriches the resulting firewall and service records in SPOG.AI. The connector performs read operations only.

Prerequisites

Before configuring the integration, ensure the following prerequisites are met:

  • Tenant Admin authorization in SPOG.AI and permission to create integrations.
  • FortiManager JSON API access and a dedicated REST API administrator with read-only permissions.
  • FortiManager HTTPS base URL and API token.
  • Trusted Hosts configured to permit the SPOG Appliance egress IP when restrictions are enabled.
  • Outbound HTTPS access from the SPOG Appliance to FortiManager on TCP 443.

Configuration

1. Create a REST API Administrator

Create a dedicated integration identity in FortiManager.

  • Navigate to System Settings > Admin > Administrators and create a REST API administrator.
  • Assign the minimum read permissions needed for ADOM, device, status, license, and policy-object queries.
  • Restrict Trusted Hosts to the SPOG Appliance egress IP or approved range.

2. Generate the API Token

Generate a token for the REST API administrator.

  • Copy the token when displayed and store it in a secrets vault.
  • Do not place the token in tickets, logs, or documentation.

3. Configure and Link the Integration

Add the FortiManager integration in SPOG.AI.

  • Enter the FortiManager base URL and API token.
  • Enable HA group aliasing only when that correlation behavior is required.
  • Run Test Connection, save the integration, and link it to the required appliance.

Configuration Fields

Use the fields below when creating the integration in SPOG.AI.

FieldRequirementDescription
base_urlMandatoryFortiManager HTTPS base URL without /jsonrpc, for example https://fortimanager.company.com.
api_keyMandatoryBearer API token generated for the FortiManager REST API administrator.
add_ha_group_aliasOptionalWhen true, adds the FortiManager HA group name as an asset alias. Default: false.

Security and Connectivity

  • Use a dedicated REST API administrator with read-only, least-privileged access.
  • Restrict access with Trusted Hosts and rotate or revoke the API token according to organizational policy.
  • Store the token in a secrets vault and monitor FortiManager administrative logs for abnormal API activity.
  • Allow outbound HTTPS port 443 to FortiManager and require TLS 1.2 or later.
  • Note: the current connector disables certificate verification internally; use a trusted network path and track remediation before production deployment.

Validation and Data Coverage

Run Test Connection or start the appliance job, then confirm FortiManager-enriched firewall assets and NAT translation records in SPOG.AI. Verify ADOM, device, VDOM, HA, and license context against FortiManager. A 401 indicates an invalid token, a 403 indicates insufficient permissions or Trusted Host restrictions, and connection failures usually indicate DNS, routing, firewall, proxy, or certificate issues.

DataCoverage
Firewall InventoryManaged device name, hostname, management IP, serial number, platform, FortiOS version, and physical or virtual classification.
Administrative ContextADOM and VDOM membership, system status, and HA status.
LicensingAvailable antivirus and IPS license-status data.
NAT TranslationsVirtual IP translations, VIP groups, and central DNAT records, including translated-service relationships.
Not ImplementedPolicy-package ingestion, configuration changes, active drift calculation, webhooks, and command execution are not performed by the current connector.

Uninstalling the Integration

  • Delete the FortiManager integration in SPOG.AI and unlink it from the appliance.
  • Disable or delete the dedicated FortiManager REST API administrator and revoke its token.
  • Remove obsolete Trusted Host, firewall, proxy, or allowlist rules.