By Global ITN · 18 November 2026

Which FortiGate model fits our users, traffic and inspection requirements?

Choose a FortiGate by the traffic and security functions it must handle at peak demand, including the workload after a failure. Use user count as context, then validate a shortlist against inspected throughput, sessions, VPNs, interfaces and your intended FortiOS configuration.

Illustration of Peak inspected workload, Testable model choice, using performance equipment and workflow composition

Measure the workload before selecting a model

Collect traffic observations from representative busy periods rather than relying on the internet circuit’s advertised speed. Include inbound and outbound usage, application peaks, remote workers, branch connections and any traffic routed between internal networks.

Count simultaneous devices as well as people. Phones, laptops, printers and connected equipment may create very different workloads from the same employee headcount. Record whether backups, large file transfers or guest access coincide with normal business demand.

Separate what you measured from what you expect to add. This makes growth assumptions visible and gives reviewers a way to challenge an unnecessarily large or small recommendation.

Illustration of Measure busy-period demand, Traffic and sessions, using monitor equipment and workflow composition

Collect the sizing inputs

Users and devices

What to measure or decide: Staff, guests, BYOD, IoT, servers and expected growth.

Why it affects the choice: Concurrent sessions and endpoints affect policy, inspection and capacity needs.

WAN bandwidth

What to measure or decide: Current and planned circuits, peak use, failover and traffic asymmetry.

Why it affects the choice: Security processing must support the traffic that actually traverses the firewall.

Inspection profile

What to measure or decide: Which security services and encrypted-traffic inspection will be enabled.

Why it affects the choice: Headline throughput can differ materially from throughput under inspection.

Remote access and VPN

What to measure or decide: Concurrent remote users, site-to-site tunnels and expected traffic per tunnel.

Why it affects the choice: VPN performance and tunnel count should fit the working pattern.

Interfaces and topology

What to measure or decide: WAN, LAN, VLAN, fibre, copper, PoE needs, routing and segmentation.

Why it affects the choice: Port type and count can constrain the design even when throughput is sufficient.

Availability

What to measure or decide: Single unit or high-availability pair, maintenance approach and failure tolerance.

Why it affects the choice: Resilience can affect model quantity, cabling, configuration and budget.

Lifecycle and growth

What to measure or decide: Expected users, circuit upgrades, applications and security changes.

Why it affects the choice: Choose capacity for a realistic planning horizon, not only today’s load.

Read the correct performance rows

Fortinet publishes separate firewall, IPS, NGFW, threat protection and IPsec measures, with test-condition footnotes. Those figures describe different workloads and should not be treated as interchangeable. Fortinet product matrix

Start by writing down the security policy you actually need. Will traffic undergo intrusion prevention, malware checking, application control or encrypted traffic inspection? Ask which published result is relevant and what the benchmark does not represent.

Do not promise production performance from a single datasheet number. If inspection or unusual applications are central to the design, request validation using representative traffic and the proposed software release.

Illustration of Relevant test rows, Enabled inspection, Compare like workloads, using compare equipment and workflow composition

Check sessions, VPNs and physical interfaces

A throughput comparison alone can miss other constraints. Ask the designer to check:

  • simultaneous sessions and connection creation during busy periods
  • site-to-site and remote-access VPN requirements
  • routing, segmentation and policy complexity
  • WAN and LAN port types, speeds and transceivers
  • management and logging destinations
  • power, mounting and environmental requirements

Fortinet’s SD-WAN ordering guide also lists security, throughput, interface connectivity and redundancy among branch and hub selection considerations. Fortinet SD-WAN ordering guide

Treat published maxima as limits to evaluate, not targets to run against every day. Ask what operating headroom remains with the intended features enabled.

Illustration of Sessions and physical ports, VPN topology, using interfaces equipment and workflow composition

Do not ignore topology and operations

Check physical requirements as well as processing capacity. Rack depth, power, cooling, cable types, interface count, optics and physical access can affect implementation. Confirm how the firewall will connect to switches, access points, internet circuits and any existing security appliance. For a high-availability pair, document which ports and links are duplicated and how each failure scenario is tested.

Operational fit matters too. Decide who will maintain the rules, review logs, approve changes, manage firmware and respond to alerts. If several sites are involved, consider whether configuration and policy need to be consistent centrally. Confirm what support and security subscriptions are required for the features selected and how renewals will be managed.

Size for the failure scenario

Define which services must continue if a firewall or circuit fails. If one appliance will carry the protected workload after failover, evaluate that workload on the surviving unit.

For dual circuits, explain whether traffic will normally use both and what happens when only one remains. Application priority and available circuit capacity may matter as much as the appliance choice.

Illustration of Normal path, Surviving appliance, Required services, using failover equipment and workflow composition

Turn the shortlist into a testable proposal

Request a short design record showing measured demand, growth assumptions, selected inspection features and acceptance tests. Include the exact model, FortiOS release and subscriptions that the recommendation relies on.

Our FortiGate quotation checklist helps carry those requirements into the order. If an existing small appliance is under review, compare renewal and refresh using the 40F and 60F decision guide.

Illustration of Demand and design record, Acceptance tests, using handover equipment and workflow composition

How GlobalITN helps

GlobalITN has supported Singapore businesses since 2013, supplying and renewing Cisco Meraki and Fortinet licences and hardware, with our own engineers across Singapore, Hong Kong, Australia and Vietnam for survey, deployment and on-the-ground support. We can review your traffic evidence, inspection requirements and site constraints, then scope the hardware and engineering work needed to validate the design.

Explore our Cisco Meraki services and our Meraki MX versus FortiGate comparison, FortiGate project support, or send your requirements through our contact page.

Frequently asked questions

Can we choose a model from employee count alone?

No. Two offices with the same headcount can have different inspection, VPN and application demands. Supply workload evidence alongside user numbers.

Should firewall throughput match our internet speed?

Check the relevant inspected workload and internal traffic as well. Raw firewall throughput alone does not establish suitability for your security policy.

Does a larger model fix every performance problem?

No. Investigate circuits, configuration, application behaviour and logging alongside appliance utilisation before recommending replacement.

What if we cannot measure the current network?

Document conservative assumptions and arrange a representative pilot or technical review. Keep the uncertainty visible in the recommendation and acceptance plan.

Does firewall throughput equal threat-protection throughput?

No. Published figures may use different test conditions and enabled services. Compare the performance measure that matches the intended security profile.

Will SSL deep inspection affect FortiGate capacity?

It can. Fortinet notes that inspection level affects performance, so validate the model against the planned inspection configuration.

Should a Singapore SME buy spare capacity for growth?

Include realistic growth and planned circuit or security changes in the sizing exercise. The amount of headroom should follow the business plan and lifecycle.