Firewall as a Service

What is FWaaS?

FWaaS (Firewall as a Service) delivers the firewall (the mechanism that controls inbound and outbound traffic) — traditionally installed at each location — as a cloud service. Without placing appliances at each site, it protects all traffic centrally in the cloud. It is one of the building blocks of SASE.

Basics

FWaaS Basics

A firewall is a "protective barrier" that blocks unauthorized traffic from outside and controls outbound traffic from inside. Traditionally, physical appliances were installed at headquarters and each branch, which posed the following challenges.

  • An appliance is needed at each location, adding deployment and maintenance cost and effort.
  • Settings tend to diverge, making it hard to keep rules consistent across locations.
  • Remote workers are out of scope. Traffic from home and similar settings is not protected.

FWaaS consolidates all of this in the cloud. Traffic from any location and any employee passes through the same firewall and is protected by the same rules. Because the service provider handles appliance maintenance and updates, the operational burden is reduced.

Image

A Visual Overview

By eliminating per-location appliances, traffic from all locations and employees is consolidated into a firewall in the cloud.

HQ Branch Remote FWaaS Cloud Internet All site and remote traffic is consolidated into FWaaS and inspected by the same rules
Visual Guide

Understanding FWaaS with Diagrams

For those new to the jargon, here are three diagrams that explain the idea behind FWaaS.

Diagram

Analogy: Consolidating per-site guards into the cloud

HQ Branch Remote Cloud FW FWaaS Internet
← swipe horizontally →

Firewalls (guards) once placed at each location are consolidated into a single place in the cloud, protecting all locations and remote workers with the same rules.

Diagram

Before / After: From scattered appliances to cloud consolidation

Traditional (per-location) FWaaS HQ Branch Remote Firewall A Firewall B Remote: out of scope Appliances and settings differ; remote is unprotected. HQ Branch Remote Cloud FW Consolidated into one; everyone protected by the same rules.
← swipe horizontally →

Traditionally, each location had its own firewall appliance with divergent settings, and remote workers were out of scope. FWaaS consolidates everything into a single cloud firewall, protecting everyone with the same rules.

Diagram

Step by step: How traffic is protected

1 Sites & remote traffic from anywhere 2 Consolidated in FW brought to one place 3 Inspect by same rules allow / block 4 Only safe traffic passes Allow
← swipe horizontally →

Traffic from all locations and remote workers is gathered into the cloud firewall, inspected by the same rules, and only safe traffic is allowed through.

Pros

Benefits

  • No per-location appliances are required, reducing deployment and maintenance burden.
  • Unified rules can be applied to all locations and all employees.
  • Remote-work traffic can be protected to the same standard.
  • Appliance updates and maintenance are handled by the service provider.
  • It can scale flexibly with the size of usage.
Cons

Drawbacks and Considerations

  • !It depends on the quality and stability of the internet connection.
  • !Migration from existing physical appliances requires planning.
  • !Specialized internal traffic may require individual design.
  • !A monthly cost based on usage and scale applies.
How to Start

Adoption Process (a typical approach)

A practical approach is to migrate in stages while running in parallel with your existing firewall.

STEP 1PROCESS
Inventory current traffic rules Organize the settings (allow/deny rules) of your existing firewall and your location structure.
Rule inventory
STEP 2PROCESS
Design cloud-side rules Rebuild existing rules on FWaaS and organize them into a form that can be unified across locations.
Rule design
STEP 3PROCESS
Pilot at a few locations Start switching over at low-impact locations and verify the effect on operations. Run in parallel with existing appliances.
PilotParallel operation
STEP 4PROCESS
Roll out to all locations If there are no issues, expand to all locations and remote workers, and decommission existing appliances in sequence.
Full rollout
STEP 5PROCESS
Operation and monitoring Monitor traffic logs and periodically review whether rules are excessive or insufficient.
MonitoringPeriodic review
Model Case

An Adoption Scenario at a Mid-sized Company

This is a hypothetical model case based on inquiries we frequently receive. The actual approach and results vary depending on the environment.

Case

A wholesale business with ~800 employees and multiple locations

Challenge: Headquarters and numerous locations each have their own firewall appliance, with inconsistent maintenance and settings. Aging appliances are all approaching update at once, and with so many units the cost adds up. Remote workers are out of scope for protection.

Existing environment: Physical firewalls from different vendors at each location.

Before HQ Branch Remote Firewall A Firewall B Firewall C Appliances differ per location; maintenance and settings are complex After HQ Branch Remote FWaaS Internet Consolidated into FWaaS, protecting all locations with the same rules
  • 1Inventory each location's traffic rules and organize them into common rules.
  • 2Consolidate rules into FWaaS and first pilot at a low-impact location.
  • 3After confirming there are no issues, roll out to all locations and remote workers.
  • 4Decommission the many aging physical appliances in sequence.

Result: Maintaining appliances across many locations became unnecessary, greatly lightening operations. The same rules apply across all locations and remote workers, and the appliance-renewal cost expected from a simultaneous refresh was also reduced.

* The above is a hypothetical model case. The actual configuration and results vary depending on your environment.

FAQ

Frequently Asked Questions

  • QWhat is FWaaS?
    FWaaS (Firewall as a Service) delivers the firewall — traditionally installed at each location — as a cloud service. Without placing appliances at each site, it protects all traffic centrally in the cloud. It is one of the building blocks of SASE.
  • QHow does it differ from a traditional on-premises firewall?
    Traditionally, physical appliances were installed at headquarters and each branch, adding deployment and maintenance cost while settings tended to diverge. FWaaS consolidates these in the cloud, so traffic from any location and any employee passes through the same firewall and is protected by the same rules.
  • QCan it support multiple locations and remote workers?
    Yes. Unified rules can be applied to all locations and all employees, and remote-work traffic — often out of scope before — can be protected to the same standard. Because the service provider handles appliance maintenance and updates, the operational burden is reduced.
  • QCan mid-sized companies adopt it?
    They can. A practical approach is to migrate in stages, starting with low-impact locations while running in parallel with your existing firewall. It can scale flexibly with the size of usage.
  • QAre there any drawbacks or considerations?
    Because traffic is consolidated in the cloud, it depends on the quality and stability of the internet connection. Migration from existing physical appliances requires planning, and a monthly cost based on usage and scale applies.

Talk to us about consolidating and updating your firewalls

From challenges such as "maintaining per-location appliances is hard," "appliance update timing is approaching," or "we want to protect remote-work traffic too," we support a review that includes FWaaS.

Contact us