FortiManager Centralized Management | Securevalley

· Nouh Droussi · Fortinet · Maroc · 4 min read · Updated

FortiManager brings ADOMs, shared policy packages, templates and revision history to FortiGate fleets. Core concepts, change control and management plane security.

FortiManager is Fortinet's centralized management platform for FortiGate firewalls and other Fabric devices: it stores device configurations, manages firewall policies and objects in shared packages, deploys changes to many devices at once and keeps a revision history for rollback. It becomes useful as soon as an organization runs more than a handful of FortiGates, several sites, or an SD-WAN network. In 2026 the current branch is FortiManager 8.0, with version 8.0.1 released in September 2026, and it can manage FortiOS versions from 7.0 to 8.0.

Why centralize security management

Managing each firewall through its own interface works for one or two devices. Beyond that, the same object is defined differently on each unit, rules drift apart, and nobody can say with confidence which configuration is running where. Centralized management addresses three recurring needs:

Core concepts: ADOMs, device database and policy packages

FortiManager organizes managed devices into administrative domains (ADOMs). An ADOM groups devices of a given product family and firmware version, and can separate business units, regions or, for service providers, customers. Administrators can be restricted to specific ADOMs.

For each managed FortiGate, FortiManager keeps a device-level database containing settings such as interfaces, routing and system parameters. Firewall rules and security profiles are handled separately in policy packages. A policy package is assigned to one or more installation targets, and the objects it uses come from a common object database in the ADOM. Changing an object once updates every package that references it at the next installation.

Provisioning templates complete this model. System, SD-WAN, IPsec and other templates define standard settings once and apply them to groups of devices, which is particularly valuable for branch networks built on a common design.

A controlled change process

The most important benefit of FortiManager is not speed but control. A typical change follows these steps:

Scripts, including CLI scripts and Jinja-based templates, handle repetitive changes, and the JSON API allows integration with automation tools and ticketing systems. Automation should always go through the same review and preview steps as manual changes.

Protecting the management plane

A platform that can push configuration to every firewall is a high-value target. In October 2024, Fortinet published advisory FG-IR-24-423 for CVE-2024-47575, a critical missing-authentication flaw in the FortiManager daemon that communicates with managed devices, and CISA added it to its Known Exploited Vulnerabilities catalog. The episode is a reminder of some basic rules:

Recent releases have also reduced the attack surface: shell access was removed in 7.6.0, the XML API is no longer supported from 7.6.5, and Management Extension Applications were removed in 7.6.4. Check these changes before upgrading if any of your procedures relied on them.

Planning a deployment or migration

Before importing existing FortiGates, clean up their configurations: remove unused objects, harmonize naming, and document exceptions. Import one device, review how its policies and objects were interpreted, then proceed by groups. Decide early how many ADOMs you need, which firmware versions they will host, and who administers each one. FortiManager can also act as a local FortiGuard distribution server for devices that should not reach the internet directly, which must be taken into account in network flows and sizing.

High availability, regular backups and a tested restoration procedure are essential, since losing the management platform does not stop the firewalls but does stop controlled change.

Skills and training

Running FortiManager well requires solid FortiOS knowledge, an understanding of ADOMs, policy packages, templates and installation behavior, and the discipline to troubleshoot installation failures. Securevalley Training offers the FortiManager 7.6 Administrator certification preparation course for these topics. Administrators who are not yet comfortable with FortiGate itself should start with FortiOS 7.6 Administrator, and teams that also centralize logs can continue with FortiAnalyzer 7.6 Administrator.

Conclusion

FortiManager turns a collection of individually managed firewalls into a governed estate with shared objects, reviewed changes and traceable history. Its value depends on a clear ADOM design, a disciplined change process and a well-protected management plane. Organizations that treat it as critical infrastructure, rather than as a convenience tool, get both efficiency and security from it.