TR EN RU
Book a Technical Call
Risk surface Protection layers Incident and recovery route Security

Enterprise Firewall Selection: A Practical Guide

A step-by-step guide to assessing capacity, visibility, manageability and operations criteria when selecting an enterprise firewall.

Published by: AnatoliaCore Technical Editorial Team

How is firewall capacity calculated?

If a firewall is sized by internet line speed, capacity can fall short once security services are switched on. Concurrent sessions, new sessions per second, application traffic, SSL inspection, VPN, threat profiles, log volume and the HA scenario should be measured together.

How do SSL inspection and VPN load affect the choice?

TLS decryption adds cryptographic processing and certificate operations; VPN adds load depending on tunnel count, encryption and the user/branch profile. The different throughput figures on a vendor datasheet should be compared under the same test conditions as the security profile you will use.

Central management and logging criteria

Across multiple devices, the need for templates, separation of duties, change history and bulk policy management drives the central management decision. On the logging side, daily volume, retention, search, time synchronization, SIEM forwarding and personal-data requirements are sized.

Enterprise firewall selection checklist

The short checklist below is a practical field reference for enterprise firewall selection projects:

Control AreaExpected Output
Traffic profilePeak bandwidth, sessions, applications and growth
Security loadSSL, VPN and active profiles
OperationsCentral management, permissions and change
EvidencePoC result, logging and failover measurement

A Weighted Selection Matrix Instead of a Shortlist

The matrix weights should be set before product demos, based on workload and risk priorities. Because vendor figures may be measured with different traffic profiles, throughput, SSL inspection and session capacity should only be compared once test conditions are matched.

Candidates are scored on performance, security features, integration, operational load, licensing model and lifecycle. Instead of ‘the most features’, the preferred architecture is the one that meets the mandatory requirements and that the team can operate.

PoC and Acceptance Testing

During a pilot or PoC, realistic traffic, SSL, VPN, policy, logging and failover scenarios are run. Acceptance criteria are written before the test; an interface demo or a theoretical maximum alone does not count as proof of capacity.

Technical Selection Criteria

  • Real throughput: the figure measured with threat protection and TLS/SSL inspection enabled is what counts; the catalog number alone is not enough.
  • NGFW capabilities: application awareness, IPS/IDS, URL filtering and sandboxing.
  • High availability (HA): active/passive or active/active, session synchronization.
  • Segmentation and policy management: security zones, rule base hygiene and central management.

Related Service Pages

To turn this guide into a project, review the service pages below.

Technology Perspective

Fortinet product families, use cases and technology selection considerations are covered on our related technology page.

Fortinet Details

Quote and Contact

You can schedule a technical pre-assessment call to scope the work for your organization.