Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A next-generation firewall writes policy in terms of applications and users rather than ports and addresses, and adds intrusion prevention and decryption to the same device.

What Is a Next-Generation Firewall?
A stateful firewall decides on addresses, ports, and connection state. That model stopped describing reality once almost everything moved to ports 80 and 443: allowing TCP 443 to the internet permits a web application, a file sharing service, a remote access tool, and a tunnelling client equally. A next-generation firewall identifies the application regardless of port, identifies the user rather than the address, and applies intrusion prevention and content inspection in the same pass.
Application identification. The device classifies traffic by examining protocol behaviour, patterns, and decoders rather than trusting the port. This lets policy say that the finance team may use a specific SaaS application while generic web browsing is restricted, and that remote access tools are denied to everyone outside IT.
User identification. Integration with Active Directory, an identity provider, or a captive portal maps addresses to accounts, so rules reference groups. This also transforms the logs: an alert naming a user is actionable in a way that an alert naming 10.4.18.77 at a time when DHCP leases have since rotated is not.
Integrated intrusion prevention. Signature and behavioural detection applied inline, so exploit traffic against your published services is blocked rather than logged. This is particularly valuable as virtual patching while a vulnerability waits for a maintenance window.
TLS inspection. Decrypting outbound traffic to inspect it, which is the only way the other three capabilities keep working as encryption becomes universal, and which brings its own cost.
Most platforms add URL filtering, sandboxing of files, DNS security, and threat intelligence feeds on top.
Datasheet throughput figures describe the device with everything switched off. Enabling application identification, intrusion prevention, and deep inspection commonly reduces usable throughput by half or more; adding TLS decryption can halve it again. Buy against the inspected throughput for the features you intend to enable, with headroom for growth, and insist that the vendor quotes the figure for your intended configuration. Undersized firewalls do not fail cleanly — they are quietly reconfigured to bypass inspection for the traffic causing the load, which defeats the purchase.
Decryption restores visibility and creates obligations. The device holds plaintext for everything it inspects, so it becomes one of the most sensitive systems you operate. Certificate pinning in mobile applications, software update clients, and many APIs breaks under interception, requiring a growing exclusion list. QUIC traffic is frequently blocked outright to force a fallback to inspectable TCP.
For UK organisations there is also a data protection dimension. Inspecting staff traffic is monitoring under UK GDPR: it needs a lawful basis, usually a data protection impact assessment, and transparency with employees. ICO guidance on monitoring at work is clear that covert monitoring is rarely justifiable. Excluding categories such as banking, health, and legal advice from decryption is standard practice and should be documented as a safeguard.
CVE-2024-3400, exploited from March 2024, and the series of Fortinet and Ivanti vulnerabilities before it, all gave unauthenticated attackers control of the device guarding the network. Patch these on an emergency schedule, restrict management interfaces to an administrative network, and never expose administration to the internet.An NGFW is a perimeter and segmentation control. It does not see traffic that stays inside a segment, which is why it pairs with microsegmentation internally, and it does not follow users who work from home, which is what SSE addresses. Our Network Security Services test whether the policy on the device matches the policy on paper.
Four things beyond stateful filtering: identifying applications regardless of the port they use, identifying users through directory integration, running intrusion prevention inline, and decrypting TLS so the other capabilities still work. A device that only adds URL filtering to port-based rules is not meaningfully next-generation, whatever the marketing says.
Size against inspected throughput with the features you will enable, not the headline figure. Application identification and intrusion prevention typically halve usable capacity, and TLS decryption can halve it again. Ask the vendor for a figure matching your intended configuration, add headroom for growth, and remember that an undersized device ends up with inspection disabled for the heaviest traffic.
It restores most of the inspection value, and it is a significant decision. The device holds plaintext for everything it decrypts, certificate pinning will break for some applications, and inspecting staff traffic requires a lawful basis and transparency under UK GDPR. Many organisations decrypt selectively, excluding banking, health, and legal categories, and document those exclusions as safeguards.
No. An NGFW protects the network perimeter and inspects traffic broadly, with generic intrusion prevention signatures. A web application firewall sits in front of specific applications and understands their request structure, parameters, and sessions, which is what detects injection and logic abuse. Organisations publishing web applications generally need both.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.