FortiCloud unifies Fortinet's hosted services under one account. What it covers in 2026, recent renames, and how to govern access with IAM.
FortiCloud is Fortinet's cloud portal: a single account and sign-in that gives access to the vendor's hosted services, from FortiGate Cloud management to FortiSASE, cloud-hosted FortiAnalyzer and FortiManager, and identity services. It also brings together asset registration, support contracts and user access control. For administrators, the practical question is less "what is FortiCloud" than "how do I govern it", because this account controls devices, licences and logs across the whole estate.
Fortinet documents FortiCloud as a unified login that ties its cloud services to FortiCare support, asset management and Identity and Access Management (IAM). The documentation for the portal is now released on a year-based cadence (versions 26.1, 26.2 and 26.3 in 2026), and the service catalogue shown on the Fortinet documentation site groups the offerings into several families:
The list changes regularly. Before building a design around a given service, check its current page on docs.fortinet.com and the product life cycle information published in the FortiCloud support documentation.
Two changes regularly cause confusion in project documents and tender specifications.
Map old names to new ones before applying older procedures.
The FortiCloud account that registered your products holds considerable power: it can move assets, manage contracts and open every cloud portal linked to them. Treating it as a shared team login is a common weakness. The IAM portal provides the tools to avoid this:
Fortinet also supports multi-factor authentication for these accounts through FortiToken, email, SMS or third-party authenticator apps. A sound baseline is to keep the primary account for emergencies only, protect it with strong MFA, and give every administrator a named IAM user with the minimum profile required.
Moving management or logging to a SaaS portal does not transfer all security duties to the provider. NIST SP 800-145 defines SaaS and PaaS models in which the provider runs the underlying infrastructure while the customer keeps control of configuration and data. In practice, Fortinet operates the platform, but you remain responsible for:
The cloud security mitigation strategies published by the NSA and CISA in 2024 stress identity and access management on the customer side, which applies directly to a FortiCloud tenant.
A few habits make a FortiCloud deployment easier to manage and audit:
Running FortiCloud services well depends on knowing the products they manage. Administrators who configure FortiGate policies, VPNs and security profiles, whether locally or from a cloud portal, can build that base with the FortiOS 7.6 Administrator – NSE 4 certification preparation. Teams centralising configuration across many devices will find the FortiManager 7.6 Administrator certification preparation relevant, and those in charge of logs and reporting can follow the FortiAnalyzer 7.6 Administrator certification preparation. These courses prepare for Fortinet certification exams; they are not delivered on Fortinet's behalf.
FortiCloud is the administrative backbone of Fortinet's hosted services, and its catalogue keeps evolving, as the FortiIdentity Cloud and FortiAppSec Cloud renames show. Secure it like any privileged system: named IAM users, least-privilege profiles, MFA, and regular reviews of assets and audit logs. Check the official documentation before each design decision, since services and names can change from one release to the next.