Fortinet FortiGate VM02 in Uganda
A two-vCPU FortiGate virtual appliance for securing cloud workloads, virtual networks and hybrid infrastructure with FortiOS.
The VM02 is positioned for organisations that need a compact virtual firewall tier with serious security functions, flexible deployment and consistent policy control. It can protect virtual network edges, segmented workloads, cloud applications and site-to-cloud traffic while fitting into the wider Fortinet Security Fabric.
Virtual firewall control where workloads actually run
FortiGate VM02 is a virtualised FortiGate next-generation firewall built for environments where the security boundary is no longer limited to a physical branch or data-centre edge. It runs FortiOS inside supported virtual and cloud infrastructure, allowing security teams to apply firewall policy, network segmentation, virtual private networking and advanced inspection closer to applications and virtual networks.
That positioning matters for Uganda organisations moving business systems into virtualised data centres or public cloud. A physical perimeter appliance may still protect internet access, but east-west application traffic, cloud subnets and hosted services can create additional boundaries. A virtual firewall can be placed at those logical control points without requiring another rack-mounted device. It also gives architects a way to keep familiar FortiGate policy and operational methods across physical and virtual estates.
The VM02 tier is defined primarily by its two-vCPU licensing level. Fortinet’s current product information lists up to 15 Gbps basic firewall throughput for VM02/VM02V, but inspection-intensive figures are lower: Fortinet publishes 1.5 Gbps NGFW throughput and 1.2 Gbps threat-protection throughput in its model comparison. These figures should be treated as sizing references under vendor test conditions, not guaranteed application throughput. Host processor generation, virtualization overhead, SR-IOV or network acceleration, packet size, encrypted traffic and enabled security profiles can materially change performance.
Current purchasing also requires attention to licensing. Fortinet’s recent VM datasheet identifies FortiGate-VM02-S as a subscription license for two vCPU cores, with the exact SKU varying according to the selected support or security bundle and term. Legacy permanent VM licenses stopped being available for new purchase in September 2025, so new projects should be scoped against current subscription ordering rather than an old FG-VM02 perpetual part number found in historical catalogues.
Why organisations choose the VM02 tier
01
Put security inside virtual infrastructure
Deploying a firewall as software allows policy enforcement to sit close to virtual workloads. This is useful when applications, database tiers or tenant networks need separation that a perimeter-only design cannot provide. The business value is cleaner control of traffic between logical environments without adding a physical appliance for each boundary.
02
Use a defined two-vCPU security tier
VM02 gives procurement and architecture teams a clear compute-license boundary. That can simplify sizing for smaller cloud or virtual security zones while retaining the same FortiOS operating model used by larger FortiGate deployments. The key is validating that inspected traffic, not just raw forwarding, fits the tier.
03
Maintain consistent security operations
FortiGate-VM participates in Fortinet Security Fabric and can be centrally managed in broader Fortinet environments. Organisations with existing FortiGate skills can therefore extend familiar policy concepts into virtual and cloud networks, reducing the operational gap between physical and software-defined security controls.
04
Support encrypted site and cloud connectivity
Fortinet publishes 1.5 Gbps VPN throughput for VM02/02V under its stated test methodology. For organisations connecting branches, remote environments or cloud networks, the appliance can combine VPN termination and firewall policy in the same virtual security layer. Tunnel scale and actual encrypted performance must still be validated against the proposed design.
05
Scale architecture without changing the operating model
FortiGate-VM is offered across multiple vCPU tiers. A buyer can start with a model appropriate to current demand while keeping a documented path toward larger VM tiers if traffic, inspection or service density grows. Upgrade and license migration rules should be reviewed before purchase.
06
Avoid unnecessary hardware dependencies
Where the protected environment is already virtual, a virtual firewall can align security deployment with the infrastructure lifecycle. This can be especially useful for hosted platforms, disaster-recovery environments and cloud projects where rack space, appliance logistics or physical cabling are not the primary design model.
A compact virtual FortiGate tier with full-platform thinking
The differentiator is not simply that VM02 is software. It is that the virtual appliance brings FortiOS security and networking functions into supported virtual and cloud environments while giving buyers a clearly bounded two-vCPU licensing tier.
2 licensed vCPU cores
Current VM02-S ordering is based on a two-vCPU subscription tier.
Up to 15 Gbps firewall
Vendor headline firewall figure; actual results depend on system and network configuration.
1.5 Gbps NGFW reference
Published with IPS and application control under Fortinet test conditions.
1.2 Gbps threat protection
Published reference with multiple inspection services enabled.
Up to 10 interfaces
Interface availability can also be constrained by the selected cloud instance or platform.
Broad platform coverage
Fortinet lists major public clouds plus VMware, Hyper-V, KVM and Xen-family support.
FortiGate VM02 specifications that affect sizing
| Specification | VM02 guidance | Buyer note |
|---|---|---|
| Product type | Virtual next-generation firewall | Runs as a virtual appliance rather than dedicated hardware |
| vCPU tier | 2 vCPU cores | Only licensed cores process FortiGate traffic and management tasks |
| Firewall throughput | Up to 15 Gbps | Headline forwarding figure; not a substitute for security-service sizing |
| NGFW throughput | 1.5 Gbps published reference | Measured with IPS and application control in vendor test conditions |
| Threat protection | 1.2 Gbps published reference | Inspection mix and encrypted traffic affect real performance |
| VPN throughput | 1.5 Gbps published reference | Validate tunnel count, encryption profile and host resources |
| Gateway-to-gateway IPsec tunnels | Up to 2,000 | Architecture and platform limits should be checked |
| Network interfaces | Up to 10 | Cloud instance type may impose its own interface limits |
| RAM | S-series has no licensed RAM restriction | Fortinet recommends at least 4 GB for proper operation in current private-cloud guidance, especially with UTM, ZTNA or proxy features |
| Storage | Platform/configuration dependent | Logging design can change storage requirements significantly |
| Platforms | Major public clouds; VMware ESXi/vSphere/NSX-T, Hyper-V, KVM, Xen/XenServer and others documented by Fortinet | Confirm supported version and deployment image before ordering |
| Current licensing | FortiGate-VM02-S annual subscription family | Bundle and duration determine the exact order code |
The most important numbers are the inspected-throughput references, vCPU entitlement and interface requirements. A 15 Gbps firewall figure describes a very different workload from 1.2 Gbps threat protection with multiple security services active. Buyers planning internet-edge inspection, application publishing or VPN aggregation should estimate peak and sustained traffic, identify how much traffic will be decrypted, and state which security profiles will be enabled. Cloud architects should also verify the selected instance type because the underlying platform can limit interfaces or network bandwidth independently of the FortiGate license. For private-cloud deployments, host CPU characteristics and virtualization networking matter. If the project requires the extended IPS database introduced in newer FortiOS releases, Fortinet notes that certain workloads require eight vCPUs or more; that requirement would move the design beyond VM02. FourTeck can use these inputs to determine whether VM02 is appropriate or whether a larger VM tier should be quoted.
Five questions to answer before requesting a VM02 quote
01 — What traffic and security workload will the firewall process?
Separate raw firewall traffic from inspected traffic. State expected internet bandwidth, east-west application flows, VPN load and whether IPS, application control, malware inspection, web filtering, SSL inspection or proxy functions will be active. These choices determine whether the two-vCPU tier has enough processing headroom.
02 — How large is the protected environment?
Provide the number of users, servers, cloud subnets, virtual networks, sites, VPN peers and expected concurrent sessions where known. Interface count can be just as important as CPU licensing in a virtual firewall design, particularly on public-cloud instance types with strict virtual NIC limits.
03 — Which platform and network architecture already exist?
Specify VMware, Hyper-V, KVM, Proxmox or public cloud, plus the platform version and intended topology. Fortinet supports a broad range of environments, but image format, acceleration options, routing design, interface mapping and high-availability methods differ by platform.
04 — What growth, VDOM and subscription requirements are expected?
Consider traffic growth over the subscription period, planned applications, additional security services and virtual domain requirements. Current S-series licensing uses subscription SKUs whose exact code depends on support/security bundle and duration. Optional VDOM subscription licensing may also be relevant.
05 — What deployment and support outcome is required?
Clarify whether the requirement is license supply only, design validation, renewal planning, migration from an older VM license, or a wider cloud-security project. For a useful quote, provide the desired term, target activation date, quantity and any existing Fortinet estate that should integrate with the VM.
Quote Preparation
Share platform, FortiOS target version, expected peak traffic, enabled security services, VPN requirements, interface count, high-availability requirement, desired subscription term, FortiGuard bundle preference and quantity. If you are replacing an existing FortiGate-VM, include the current model and license type.
Business environments where VM02 can make sense
Virtual data-centre segmentation
An organisation hosting application servers and databases on a supported hypervisor may need policy enforcement between logical tiers. VM02 can be inserted as a virtual firewall so traffic between selected network segments passes through FortiOS controls. This is useful where physical switching boundaries do not provide the desired inspection. The design should validate virtual NIC count, routing mode, host resource reservation and expected east-west throughput.
Public-cloud workload protection
A business moving services to AWS, Azure, Google Cloud or another supported cloud may want FortiGate policy consistency around cloud networks. VM02 can serve as a cloud firewall tier using BYOL subscription licensing where appropriate, while some platforms also offer marketplace consumption options. Instance bandwidth, interface limits, availability-zone architecture and cloud routing must be considered alongside the FortiGate license.
Hybrid connectivity and VPN termination
For an environment connecting offices or data-centre resources to a hosted workload, the VM can terminate IPsec VPN and enforce traffic policy in the same virtual appliance. Fortinet publishes a 1.5 Gbps VPN throughput reference for VM02/02V. Actual encrypted throughput depends on the host and configuration, so branch count and peak tunnel traffic should be included in sizing.
Disaster-recovery security boundary
A secondary virtual environment can require the same policy logic as the primary site even if it is activated only during tests or recovery. A FortiGate VM can help maintain a familiar security architecture in that environment. Buyers should still plan licensing, HA expectations, image availability, backup configuration and subscription continuity before relying on it for recovery operations.
Deep dive 1: performance is a workload question
Virtual firewall performance is influenced by more variables than a hardware appliance specification can imply at first glance. The VM02 license makes two vCPU cores available to FortiGate processing, but the speed of those cores, the hypervisor scheduler, virtual network drivers, acceleration features and contention on the host all affect practical results. Public-cloud instances add another layer because each instance family has its own network and interface characteristics.
The security policy matters just as much. Basic stateful firewalling is less computationally demanding than combining intrusion prevention, application identification, malware scanning and SSL inspection. That is why Fortinet publishes different performance categories. A buyer who only sees the 15 Gbps firewall number can dramatically underestimate the resources required for a heavily inspected internet connection. The 1.5 Gbps NGFW and 1.2 Gbps threat-protection references are more relevant starting points for security-service sizing, but they remain laboratory references.
For procurement, the practical approach is to document peak traffic, average traffic, encrypted percentage and the services applied to each major flow. Add growth margin rather than sizing exactly to today’s measured bandwidth. Where traffic demand is close to the VM02 inspected-throughput reference, a larger VM tier may provide a safer operational margin.
Deep dive 2: platform flexibility with platform-specific decisions
FortiGate-VM is designed for broad virtual and cloud deployment, but portability does not mean every environment is identical. Architecture should be validated for the selected platform before the license is ordered.
Private cloud
Fortinet documents support across VMware ESXi/vSphere, Microsoft Hyper-V, KVM, Xen/XenServer and other listed environments. Check the exact supported version, image and networking method.
Public cloud
Major cloud platforms support FortiGate-VM. Instance type can control available interfaces and network capacity independently of the two-vCPU license.
Licensing model
Current VM02-S BYOL ordering is subscription based. Public clouds may also provide on-demand/PAYG models whose commercial and migration rules differ from BYOL.
Deep dive 3: licensing is part of the architecture
For a new deployment, the license should be treated as a technical dependency rather than a line item added after design. Fortinet’s current virtual-appliance datasheet lists VM02-S under an annual subscription scheme, with the order code built around the two-vCPU level, selected support/security bundle and duration. The S-series also removes licensed RAM restrictions, but CPU entitlement remains central to the model tier.
This is especially important when older online references show the historical FG-VM02 perpetual license. Fortinet states that permanent FortiGate-VM licenses ceased new sale on 29 September 2025. Existing customers may still have support, renewal or migration considerations, but a new Uganda project should be quoted using currently orderable subscription options.
Buyer decision checklist
- Confirm whether the requirement is a new subscription, renewal or migration.
- Choose the security/support bundle based on required FortiGuard services rather than selecting by price alone.
- Confirm the term and activation timing.
- State whether additional VDOM capacity is required.
- For public cloud, compare BYOL with the platform’s supported on-demand model where commercially relevant.
- For HA, confirm that both nodes use compatible license types and sizing.
What buyers should check before purchase
| Risk | What to confirm | Why it matters | Share with FourTeck |
|---|---|---|---|
| Wrong performance tier | Inspected traffic and enabled services | Security throughput is lower than raw firewall throughput | Peak Mbps/Gbps and inspection profile |
| Platform mismatch | Hypervisor/cloud and version | Image, drivers, NICs and HA methods vary | Platform name, version and topology |
| Incorrect subscription | Bundle, term, renewal/migration status | Entitlements define services and support | Required security services and term |
| Interface shortfall | Required virtual interfaces and cloud instance limits | A design may need more network interfaces than an instance exposes | Network diagram and interface count |
Also confirm high-availability expectations, logging destination, FortiManager or FortiAnalyzer integration, VDOM requirements and the expected upgrade path. These details can change both the technical architecture and the exact subscription order code. Where the VM is part of a larger project, quantity and target activation dates should be provided early so quotation and delivery coordination can be planned without assuming immediate availability.
Uganda availability and service guidance
FourTeck can assist organisations in Uganda with product selection, current subscription identification, quote preparation and deployment planning for FortiGate virtual firewall requirements. Availability can vary according to the FortiGuard bundle, subscription duration, license type and project quantity, so the most useful request is one that includes the intended platform and security workload. For Kampala projects, FourTeck can review whether the two-vCPU tier is appropriate before a commercial quote is prepared. Delivery in this context may include electronic licensing or entitlement processes rather than physical shipment, depending on the ordered SKU. Warranty and support expectations should be discussed in terms of the selected FortiCare or security bundle because a virtual appliance does not follow the same hardware replacement model as a physical firewall. FourTeck can also help customers document renewal timing, migration requirements and alternative VM sizing where the requested configuration is not the best match.
Coverage within Uganda
Businesses and project teams in Kampala, Entebbe, Jinja, Mbarara and Gulu can contact FourTeck for quotation and procurement coordination. The service discussion should focus on the deployment environment, subscription entitlement and project schedule rather than assumptions about local stock, because FortiGate-VM is a licensed virtual product and current orderability depends on the selected Fortinet program and bundle.
Regional project support
Organisations operating across Uganda and neighbouring markets often want one security architecture across several hosted environments or offices. FortiGate-VM can support that kind of standardisation because FortiOS is available across physical, virtual and cloud form factors, but each site or cloud should still be sized and licensed for its actual role. FourTeck can coordinate quote discussions for Uganda and selected East Africa or Africa projects where relevant, including requirements that involve Kenya or cross-border IT procurement. Regional availability, licensing eligibility and commercial terms should be confirmed for each destination rather than assumed from another market.
For regional enquiries, buyers can review FourTeck Uganda, FourTeck Kenya, FourTeck Africa, or the FourTeck UAE site when a wider sourcing discussion is required. These links are intended for procurement coordination; they do not imply identical stock, pricing or service conditions across countries.
Related products and sizing alternatives
FortiGate VM01
Consider when the workload is smaller and one licensed vCPU is sufficient. Validate inspected throughput and interface needs before stepping down.
FortiGate VM04
A four-vCPU path for workloads that need more processing headroom than VM02. Useful when projected inspected traffic is close to the VM02 ceiling.
FortiManager
Relevant to organisations that need centralised management across multiple FortiGate appliances or virtual instances.
FortiAnalyzer
Consider when the project needs centralised logging, analytics and reporting beyond the local VM design.
Why buyers contact FourTeck for virtual firewall projects
01. Product selection guidance can compare the requested VM tier with actual traffic and security-service requirements instead of treating every two-vCPU deployment as identical.
02. Configuration review can identify platform, interface, high-availability, VDOM and management dependencies before they become procurement problems.
03. Quote assistance can map the requirement to a current subscription bundle and term, important now that new perpetual FortiGate-VM licensing is no longer the normal purchase path.
04. Uganda procurement coordination can bring technical and commercial inputs together for single licenses, renewals and project quantities without making unsupported stock or delivery promises.
05. Alternative matching can move the design to VM01, VM04 or another appropriate FortiGate tier when VM02 does not fit the measured workload.
FortiGate VM02 buyer questions
01. What is FortiGate VM02 used for?
It is a virtual next-generation firewall for protecting virtualised and cloud network environments. Typical roles include workload segmentation, internet-edge policy, VPN termination, cloud network inspection and extending FortiOS controls into infrastructure where a physical appliance is not the preferred form factor. The correct role depends on throughput, platform and security-service requirements.
02. How many vCPUs does VM02 use?
The VM02 tier is licensed for two vCPU cores. A virtual machine instance can sometimes expose more processors, but Fortinet licensing determines how many cores FortiGate uses for traffic and management. Current S-series licensing is subscription based, so the exact order code also reflects the chosen security/support bundle and duration.
03. Is 15 Gbps the expected security throughput?
No. The 15 Gbps figure is Fortinet’s published firewall throughput reference. The vendor separately lists 1.5 Gbps NGFW throughput and 1.2 Gbps threat-protection throughput for VM02/02V under its stated test conditions. Real performance varies with host hardware, virtualization networking, traffic mix, encryption and enabled security profiles.
04. Can VM02 run in public cloud?
Yes. Fortinet positions FortiGate-VM for major public clouds and also documents private-cloud hypervisors such as VMware, Hyper-V, KVM and Xen-family platforms. The selected cloud instance must still meet network-interface and performance requirements. Buyers should also decide whether BYOL subscription or a supported marketplace consumption model is appropriate.
05. Does the current VM02 license restrict RAM?
Fortinet’s current S-series datasheet states that S-series FortiGate-VM licenses do not have RAM restrictions across vCPU levels. Fortinet’s current private-cloud guidance recommends at least 4 GB RAM for proper operation, especially when UTM, ZTNA or proxy features are enabled. Actual memory allocation should reflect the enabled functions and FortiOS guidance.
06. Do I need a FortiGuard subscription bundle?
Current VM02-S ordering uses subscription licensing, and the exact SKU incorporates the selected support or security bundle and term. The appropriate bundle depends on which security services and support coverage your organisation requires. Provide those requirements when requesting a quote so the commercial line item matches the intended security design.
07. Can I still buy the old perpetual FG-VM02 license?
Fortinet states that permanent FortiGate-VM licenses stopped being available for new purchase on 29 September 2025. Existing perpetual-license customers may have renewal or migration paths, but new deployments should be scoped against current subscription licensing. If replacing an existing VM, share its current license type before a migration quote is prepared.
08. How do I know whether VM02 or VM04 is better?
Compare inspected traffic, security services, VPN load, interface requirements and growth margin. VM04 provides a higher vCPU tier and higher published performance references. If the expected VM02 workload sits near its inspected-throughput range, the larger tier may offer more operational headroom. FourTeck can review these inputs before quotation.
09. What information should I send for a Uganda quote?
Send the target hypervisor or cloud, expected peak bandwidth, security features, VPN requirements, number of interfaces, HA requirement, subscription term, preferred FortiGuard bundle and quantity. If you already operate FortiGate products, include the current model and management environment so compatibility and migration considerations can be reviewed.
Build the VM02 quote around your real security workload
Tell FourTeck where the virtual firewall will run, how much traffic it must inspect, which FortiGuard services are required and how long the subscription should cover. Those details allow the team to review the two-vCPU tier, identify the current license family and prepare a more useful Uganda quotation.
- Cloud or hypervisor platform and version
- Peak and inspected traffic estimate
- VPN, interfaces and high-availability needs
- Required security services and subscription term
- Quantity and target activation date
Reviews
There are no reviews yet.