Next-Generation Firewall (NGFW)
A firewall that knows which app and which user, with IPS, web filtering, HTTPS inspection and VPN, sized on real all-features-on numbers.

What we usually find on site
A basic router or old firewall only sees IPs and ports. It misses web-borne malware and anything hiding inside HTTPS. When something does happen, there are no logs to show how it got in.
An NGFW stacks several layers of protection in one box: stateful firewalling, application control, IPS, anti-malware/sandboxing, web/DNS filtering, SSL/TLS inspection and VPN (IPsec, SSL or ZTNA). Rules can be written per user and group (via Active Directory/Entra ID), not just per IP. "Finance can't use Facebook during work hours" becomes one rule.
Sizing it properly
Datasheets put "firewall throughput" in big type. Ignore it. The numbers that matter are threat protection throughput (IPS + anti-malware + app control on) and SSL inspection throughput, which are often several times lower. We size to your internet bandwidth, headcount and 3–5 years of growth.
A warning when buying through Thailand: confirm the security licence can be registered and the warranty honoured for use in Laos. A cheap box you can't renew is the most expensive one you can buy.
Can't stop? Buy two
Banks, hospitals and anyone who can't go offline should run an active-passive HA pair with two ISPs. All logs go to a reporting platform or SIEM, so you can investigate when something happens and spot trends before they turn into incidents.
What it does
Application control
Identifies and controls thousands of apps, whatever port they use.
IPS and anti-malware
Stops exploits and malicious files, with sandboxing.
Web and DNS filtering
Blocks phishing, gambling and malicious domains.
SSL/TLS inspection
Looks inside HTTPS, with exemptions for banking and health sites.
VPN and ZTNA
IPsec between sites, MFA for remote users.
High availability
Active-passive pair that fails over on its own.
Logs and reports
For incident investigation and management reporting.
Design and rollout
- 1
Review network, bandwidth and existing rules
- 2
Size on threat-protection throughput and design zones
- 3
Migrate and clean up old rules; connect AD/Entra ID
- 4
Turn on security profiles in stages: monitor first, then block
- 5
Set up HA, VPN and log forwarding
- 6
Review rules and update firmware regularly
Where it fits
- Banks and insurers separating core systems and keeping logs
- Government agencies running online public services
- Factories keeping OT networks away from the internet
- Schools filtering content for students
Typical system sizes
Small Business
Fits: Up to 50 users, up to 300 Mbps internet
- Desktop NGFW with security subscription
- Web filtering, IPS and remote-access VPN
- Monthly report
Mid-size
Fits: 50–500 users, several sites
- HA NGFW pair at head office
- SSL inspection and identity-based rules
- Branch VPN and central logging
Enterprise / Data Center
Fits: 500+ users or a data center
- Edge plus internal segmentation firewalls
- Central management and SIEM integration
- Quarterly rule-base review
Brands we supply & install
All brand names and trademarks belong to their respective owners. Mention does not imply official partnership unless explicitly stated. Products are sourced through legitimate distribution channels.
FAQ
What's the difference between UTM and NGFW?
Today the two terms mostly overlap and depend on each vendor's marketing. Ask three questions instead: does it know applications, does it know users, and is it still fast enough with everything turned on?
Does the licence need renewing every year?
Yes. Without the security subscription the IPS, anti-malware and web-filter databases stop updating. The box keeps running but protects very little. We remind you 60 days before expiry.
Does SSL inspection slow the internet?
It uses a lot of firewall CPU, so size for it from the start. Sized correctly, users won't notice. Undersized, they'll notice on day one.
Is a firewall on its own enough?
No. It's the front door. You still need EDR on devices, MFA, backups in more than one location, an incident response plan and staff training. Firewall logs help a lot when investigating.
Related guides
Sizing a Firewall: What Really Separates UTM from NGFW
Why the internet slows down after a new firewall goes in, which datasheet number to size against, and what to check before paying when the unit ships from Thailand to…
Ransomware Checklist: Breaking the Attack at Each Stage
Ransomware is not a one-minute event. A checklist organized around the stages attackers actually go through, plus what to do in the first hour.
Secure Remote Access: When VPN Is Enough and When to Move to ZTNA
How remote-access VPN and Zero Trust Network Access differ in practice, what to fix in your current VPN first, and how to handle vendors who want remote access.
Hotel Wi-Fi Design Guide: From Guest Rooms to Ballrooms and Garden Villas
In-room AP placement, a captive portal tied to the PMS, keeping guests away from hotel systems, a worked bandwidth example, and what is specific to hotels in Laos.
Designing an Office Network: What to Decide Before You Buy Anything
The order of decisions an engineer follows when designing LAN, Wi-Fi, firewall and power for a 20–300 person office in Laos, with a checklist and a phased budget.
Internet Redundancy with Dual ISPs: When the Fiber Gets Cut
Failover or load balancing, how to pick two providers that won't fail together, the equipment you need, and how to test failover so you know it really works.
Related solutions
Cybersecurity
Send us a floor plan or a few photos of the site
We’ll come back with a few questions, then a first design. The first consultation is free, in Lao, Thai or English, on WhatsApp or our Facebook page.