NGFW or a conventional firewall: what to choose and what the law requires
Servix technical team · Updated
In brief. A conventional firewall is enough if the company has no public services, no remote employees and does not process personal data; an NGFW is needed when services are published externally, when there are branch offices, and when there are regulatory requirements. An NGFW identifies applications instead of ports and adds IPS, antivirus, user-based policies and TLS inspection, which reduces the performance of entry-level models many times over. The laws ZRU-547 “On Personal Data” and ZRU-764 “On Cybersecurity” require not an NGFW but segmentation and logging; since March 2026, localization has been mandatory only for biometric data, genetic data and data of telecom subscribers.
The classic firewall solved a problem formulated thirty years ago: passing traffic by addresses and ports. Today almost everything an employee does on the internet goes through a single port 443 and is encrypted — from work email to a personal messenger and a cloud file-sharing service. For an “allow tcp/443” rule, it is all the same stream. This is why the NGFW class appeared: a device that looks not at the port but at the application, the content and the reputation. Let’s look at how it differs in practice, what it costs, and how this relates to the requirements of Uzbekistan’s legislation.
Where the classic firewall ends
A packet filter and a stateful firewall operate at L3–L4: source address, destination address, protocol, port, connection state. This is enough to separate networks and close the external perimeter to direct connections. But this model has blind spots, and today they account for all of the real risk.
First, the application is not determined by the port. A corporate portal, an anonymous VPN client and a torrent client with encryption support all work over 443. Second, the content is not inspected: to an L4 filter, a malicious file downloaded over HTTPS is no different from a Windows update. Third, there is no user context — a rule is bound to an IP address rather than a domain account, so in an environment with DHCP and mobile devices, policies quickly lose their meaning.
What an NGFW adds
Application identification. The device identifies an application by signatures and traffic behavior rather than by port number. This makes it possible to write policies in business terms: allow corporate file sharing, block public file-sharing services, limit bandwidth for video services.
Intrusion prevention system (IPS). It inspects packet content for signs of exploitation of known vulnerabilities and blocks the attempt before it reaches the vulnerable server. This is critical for externally published services when an application update cannot be installed immediately — IPS works as a virtual patch.
Antivirus and web filtering. Scanning downloaded files at the gateway and blocking website categories and known malicious domains. This does not replace protection on workstations, but it removes the bulk of mass threats at the entry point.
User identification. Integration with Active Directory or LDAP: a policy is written for the “Accounting” group rather than a subnet, and the log shows the user account, not just the address.
Encrypted traffic inspection. Without it, all of the mechanisms listed above see only the outer shell of the connection. An NGFW decrypts the session, inspects the content and encrypts it again — for this, a dedicated certificate authority is deployed on the device, and its certificate is distributed to workstations through group policies.
The cost of inspection: the main practical nuance
This is where mistakes are most often made when choosing a model. Every manufacturer’s specifications list several throughput values, and they differ many times over: firewall throughput in “clean” mode, throughput with threat protection enabled, and, separately, throughput with TLS inspection. Decrypting traffic is the most resource-intensive operation, and on entry-level models it can reduce real performance several times compared to the rated firewall figure.
Hence the selection rule: go by the line with threat protection enabled, and if encrypted traffic inspection is planned, by the corresponding figure — and leave headroom. A device chosen by the attractive number in the first line hits its ceiling in the very first month after all subscriptions are enabled. We covered a detailed comparison of specific models by these parameters in a separate article — how to choose a FortiGate for the size of your office.
What Uzbekistan’s legislation requires
There is no direct requirement in the law to “install an NGFW” — the regulation speaks about the result, not the device model. But the set of requirements determines what exactly you will need to be able to demonstrate during an inspection. Below is the current state as of September 2026; it is a guideline, not a legal opinion, so check the exact wording in the primary sources.
Personal data. The basic document is the Law of the Republic of Uzbekistan “On Personal Data” No. ZRU-547 of July 2, 2019. It introduces the concepts of data owner and data operator, the obligation to process data in a registered database, and the requirement to ensure data protection at all stages of processing.
Localization: rules relaxed since March 2026. Previously, Article 27-1 required personal data of citizens of Uzbekistan to be stored on technical facilities physically located in the country. Law No. ZRU-1125 of March 26, 2026 set out this article in a new wording: mandatory storage within the republic has been retained for a closed list of categories — biometric and genetic data, as well as data of telecom operators’ subscribers. Other personal data may also be processed outside the country; the list of such countries is determined by the Cabinet of Ministers. For businesses, this means that cloud services and foreign platforms are no longer an automatic violation — but the obligation to protect data and register databases has not gone away.
Cybersecurity and critical infrastructure. The Law “On Cybersecurity” No. ZRU-764 of April 15, 2022 introduces the concept of critical information infrastructure facilities and obligations for their protection. If an organization falls into this category — a bank, a telecom operator, energy, the public sector — requirements for network segmentation, logging and incident response become subject to inspection rather than an internal matter for the IT department.
What this means in practice for network equipment: you need segmentation — separating the data segment from the general office network; you need controlled outbound access with logging; you need log retention for a period sufficient to investigate an incident; you need managed remote access instead of RDP exposed to the outside. All of these are exactly the functions for which NGFW firewallsare bought.
When a conventional firewall is enough
The honest answer: sometimes it is. If the company has no public services, all external access goes through the provider’s link with basic filtering, and the data does not leave a single server in the office, a router with a decent packet filter will do the job. Moving to an NGFW makes sense when at least one of these conditions appears: services published externally, remote employees, processing of customers’ personal data, requirements from a regulator or counterparty, branch offices with inter-office links.
A separate category is companies that need not so much security features as proper link management: two lines from different providers, automatic failover, priority for telephony and video conferencing. This task is handled by the SD-WAN built into modern NGFWs — and it is often the main argument for replacing an old router.
What is purchased together with the device
The cost of a project is not just the hardware. Almost all protection functions work by subscription: without active subscriptions to IPS signatures, antivirus databases and web filtering categories, the device continues to work as a conventional firewall but stops seeing new threats. The subscription is planned right away for the entire service life — three or five years.
Second, logging. The device’s internal storage is enough for days, while investigating an incident and meeting retention requirements needs an external log collector or a centralized management system. Third, redundancy: for organizations where link downtime is unacceptable, devices are installed in pairs in high availability mode, and this doubles the cost of the hardware.
Fourth, and remembered last, is training or ongoing support. An NGFW with incorrectly written policies gives a false sense of security: an “allow all outbound” rule on an expensive device works exactly the same way as on a cheap router.
Pre-purchase checklist
Calculate the real bandwidth: not the provider’s plan but the actual peak link utilization. Determine whether encrypted traffic inspection is needed, and choose the model by the corresponding line of the specification. Budget for subscriptions for the entire service life, not just the first year. Settle the question of log storage before deployment, not after the first incident. Check who will maintain the device and how: configuring policies is an ongoing process, not a one-time job during installation.
Available models with specifications are in the NGFW firewallssection, which also includes the FortiGate 60F for a small office and the FortiGate 200F for a heavily loaded perimeter. The network part of the project — switches and access points — is easier to select together with the firewall, so that segmentation policies work from the port all the way to the internet uplink. For configuration selection for your specific infrastructure, contact us.
Related collections and tools: FortiGate for the office.
Questions and answers
Is it mandatory to enable HTTPS inspection?
Technically, no: the device will work without it. But without decryption, the antivirus and web filter see only the destination address, and the content remains uninspected. The compromise used most often is to inspect the main web traffic but exclude categories where inspection is inappropriate or prohibited by company policy — banking services, medical and government portals.
Can rules be migrated from an old firewall?
Mechanically, partly: most vendors have configuration converters. But migrating the old rule set in full is usually harmful: it accumulates permissions whose reasons no one remembers anymore. Migration is a good occasion to rebuild the policy from scratch, starting from default deny, and keep only what is actually used.
What happens if the subscriptions expire?
The device does not shut down or block traffic — it continues to work as a firewall with the databases already loaded, which stop being updated. In practice, this means that protection against new threats stops working within a few weeks. It is better to plan the renewal in advance: with some vendors, reinstating expired subscriptions costs more than continuous renewal.
Related reading
FortiGate: how to choose a model and get the performance right
Which throughput to look at in the FortiGate specification, why SSL inspection is needed, what hardware acceleration provides, how to calculate licenses. Choosing a model for the task.
How to choose a FortiGate: comparing the 40F, 60F, 70F, 90G, 120G, 400F, 600F
Comparison of FortiGate 40F, 60F, 70F, 90G, 120G, 400F and 600F: throughput, SSL inspection, ports and choosing an NGFW for your network. Tashkent.
FortiGuard licenses for FortiGate: what is included, what happens without a subscription, how to renew
FortiGate license in 2026: what FortiGuard ATP, UTP and Enterprise include, what turns off without a subscription, how to renew for 1–5 years and what co-term is.
FortiGate F or G series: what to choose in 2026
How FortiGate G differs from F: SP5 processor, 1.6–2.8 times higher Threat Protection, faster SSL inspection, 10G ports. Comparison of pairs and prices as of November 2026.



