Do You Still Need a Firewall if Your Staff Work from Phones?
Key takeaways
- Cloud services and mobile devices have dissolved the single network edge that perimeter firewalls were designed to defend.
- Egress filtering matters more than ingress filtering now, because malware and command-and-control traffic leave the network rather than arriving at it.
- CERT-In requires 180 days of log retention, and firewall logs are usually the first evidence set an investigator requests.
- The 'internal' network for most Indian SMEs includes home routers and hotspots, so segmentation must be defined by device role rather than by physical location.
- A firewall rule review at AAVETech is fixed-price at roughly Rs 12,000 to Rs 30,000 per tester-day plus 18% GST, with a retest included.
As of 24 October 2026: the service descriptions, prices and turnaround figures on this page are current.
What is the firewall actually protecting now?
Less than it used to, and the honest scope is three things. First, it constrains inbound exposure: a rule that exposes a management interface or an old line-of-business application to the internet is the kind of mistake that shows up in a penetration test every year. Second, and increasingly more valuable, it constrains egress, so that a compromised workstation cannot reach arbitrary destinations, and command-and-control traffic is visible rather than invisible. Third, it produces the log trail that a forensic investigation and a CERT-In report depend on. Anything else, such as assuming the firewall stops an attacker who has credentials, is a category error: the firewall enforces a network policy, and identity now carries most of the access decision.
How did cloud and mobile break the perimeter?
Three changes did it. SaaS moved the server side off your network, so the office firewall no longer sits between your data and the internet. BYOD and mobile hotspots put staff devices on networks you do not control, and mobile operating systems update themselves outside your patch window. And SaaS providers now publish their own allowed-IP ranges, which turns the edge firewall into a set of narrow, changeable rules rather than a perimeter. The practical consequence is that an 'internal' address range now includes a home router and a 5G hotspot. Any segmentation design that depends on an IP range meaning 'trusted' is already broken, and it should be rewritten in terms of device identity, role and managed status.
Which firewall rules should a business review first?
Work down a priority list. Any inbound rule open to 0.0.0.0/0 on a management, database or file-sharing port is a candidate for immediate closure. Any inbound rule that has been there since a migration and no longer has a matching business owner is a candidate for deletion, because unowned rules are how old exposures survive. Then look at outbound: unrestricted outbound on user subnets lets a compromised endpoint reach anywhere, which is what makes malware resale and command-and-control traffic possible. Then check logging: is traffic being recorded, is it retained for 180 days as CERT-In requires, and is it shipped to a central place the firewall administrator cannot delete? A rule that is not logged is a rule you cannot investigate.
Is a next-generation firewall worth it for a small Indian business?
Sometimes, and the deciding question is not throughput, it is what else you will have. A branch office appliance with good application visibility and a managed rule review can be worth it. But for a 20-person firm the higher-leverage purchases are a cloud-native firewall with identity-aware policies, endpoint detection and response on every laptop, and a small segmentation design that separates staff devices from servers and finance systems. AAVETech scopes that as a network penetration test plus a segmentation design, delivered as a fixed-price engagement in 5 to 10 working days, with a written report and a retest after your fixes.
| Layer | What it now protects | Common failure |
|---|---|---|
| Identity layer | Who the request is from | Shared accounts and stale sessions |
| Cloud firewall | Traffic into and out of cloud estates | Default-allow rules left untouched |
| Edge firewall | Physical office ingress and egress | Unowned legacy rules open to the internet |
| Network segmentation | Lateral reach after a compromise | Trust by IP range rather than device role |
| Endpoint controls | What runs on the device | No EDR, unknown executables allowed |
What are the common questions about F?
Get a straight answer on this
Send us your current firewall rule export and we will return a fixed-price rule review, a segmentation design and a written scope.
Send us the details See pricing