Define the service
Name the traffic you want to permit and set its protocol and port or port range. Reuse that service in your firewall rules.
Control every connection. Allow only what matters.
Set firewall rules between people, devices, sites, applications, and the internet. Permit only the services each connection needs, all from one console.
What is Firewall as a Service (FWaaS)?
A firewall policy for every connection that matters.
Jimber FWaaS lets you decide which source can reach which destination and over which service. That includes traffic between your own users, devices, sites, and applications, as well as traffic to the internet. Rules are managed in the cloud as part of Jimber SASE.
How FWaaS works
Every rule answers three simple questions: what service, who connects, and where it can go.
Choose who can connect
Set a source and destination, from people and groups to devices, networks, applications, and the internet.
Allow only that connection
The rule permits the selected service between those entities. Other services need their own explicit permission.
Only the services needed for safe browsing.
Allow name resolution and secure web traffic for the people who need it. Add other services, such as email or remote access, only for the relevant group and destination.
The screenshot shows how each service is defined by a protocol and port, so the rule is specific and easy to review.
Why you should choose Firewall as a Service (FWaaS)
Less unnecessary access
Keep unused ports and protocols closed while giving people the services their work requires.
Protection beyond the internet
Control connections between users, devices, sites, and applications, including traffic inside your organisation.
One policy across locations
Manage rules centrally for office, branch, and remote connections as your network changes.
Rules people can understand
Use named services and clear sources and destinations instead of relying on a list of unexplained ports.
Key Capabilities
Control the service and the path it is allowed to take.
Service level rules
Permit exactly the network services a connection needs.
- TCP, UDP, and other protocol definitions
- Named ports and port ranges
Identity based policy
Decide who or what may reach each destination.
- Rules for people, groups, and devices
- Source and destination in every policy
Internal segmentation
Apply firewall controls between connected entities, not just at the internet edge.
- Limit access between sites and networks
- Keep sensitive services available only where needed
Cloud managed changes
Review and update firewall policy from the Jimber console.
- Reusable service definitions
- One place to manage connected locations
Why Jimber for FWaaS
Firewall rules work alongside Jimber’s ZTNA, Secure Web Gateway, and SD-WAN controls. You can define who connects, which service they use, and the destination they may reach in one place.
- Policies for internal and internet connections
- Named services that make rules easier to maintain
- Cloud management across connected locations
Give every connection a clear rule.
Try the Jimber console and see how service definitions become firewall policies.
FAQs about Firewall as a Service
Does FWaaS only control internet traffic?
No. Jimber firewall policies can control permitted services between connected users, devices, networks, applications, and sites, as well as connections to the internet.
What is a firewall service?
A service is a named definition of the protocol and ports a connection uses. You can create a service for secure web traffic, DNS, email, or a specific application, then use it in a firewall policy.
How do we allow only what safe browsing needs?
Start with the services your environment needs for name resolution and web traffic, such as DNS and HTTPS. Add other services only for the people or devices that need them. The exact set depends on your applications and network.
How is FWaaS different from a Secure Web Gateway?
A Secure Web Gateway applies policy to websites and web apps. FWaaS controls network connections and services, including traffic between internal entities and traffic that is not web browsing. Jimber manages both in its SASE platform.
Can different groups have different firewall access?
Yes. A policy can use an identity or group as its source and permit only the services that group needs to reach an approved destination.
Do I need to define every port separately?
No. A named service can include the protocol and port range you need. You can reuse that definition in policies instead of repeating the same settings.