Check throughput, connection setup and concurrent sessions against one explicitly entered measured feature profile.
Security
Firewall inspection and session sizing
Check throughput, connection setup and concurrent sessions against one explicitly entered measured feature profile.
Example inputs · Replace these with your measurements to build your plan.
Method, example and sources
Record the inspection, firmware and traffic conditions behind the capacity figures.
Apply the same unused-capacity reserve to each independent limit.
Compare throughput, connection setup and session occupancy separately.
Retain review-needed status until matching-profile evidence is supplied.
Worked example. 1,200 Mbps with 25% unused reserve requires 1.6 Gbps of matching-profile capacity. A 2.5 Gbps profile passes that check independently of CPS and sessions.
Throughput, connection setup and session occupancy are independent constraints.
Required profile throughput
1.6Gbps
Throughput budget remaining
0.675Gbps
CPS budget remaining
5,500connections/s
Session budget remaining
250,000sessions
Firewall inspection and session sizing: detailed result
Constraint
Entered demand
Usable entered capacity
Check
Throughput (Gbps)
1.2
1.875
within
Connections/s
2000
7500
within
Sessions
500000
750000
within
Profile: TLS inspection + IPS + application control
Use the same TLS/IPS/application mix, packet sizes, logging and firmware profile. A checked evidence box is your attestation, not an independent benchmark; featureless firewall throughput is not inspection throughput.
From the catalog
Network Security & Firewalls
Explore related listings, then confirm the exact model requirements against your plan. These listings are not an automatic compatibility or capacity verdict.
Firewall specifications often list several throughput figures measured under different conditions. A result without inspection is not interchangeable with a TLS decryption and intrusion-prevention workload. Enter capacities from the profile closest to your real traffic and preserve that description beside the result. Each limit is checked independently so spare bandwidth cannot hide a full session table.
What to verify next
This worksheet does not benchmark a firewall or infer model capacity from its name. Certificate sizes, applications, packet mix, logging, firmware and policy changes can alter performance. Validate the final profile using documented evidence and representative tests. The evidence checkbox records your own attestation; it does not turn an entered datasheet value into an independently verified measurement.
Worked example
1,200 Mbps with 25% unused reserve requires 1.6 Gbps of matching-profile capacity. A 2.5 Gbps profile passes that check independently of CPS and sessions.
