FIREWALL (FWAAS)
Firewall as a Service (FWaaS) based on pf
Every VM has its own firewall, applied on its interface by pf, OpenBSD’s firewall. You get the fine-grained control of pf without configuring a server.
OpenBSD’s firewall, for every VM
pf is one of the most highly regarded firewalls in the open source world. The platform applies it to every VM, on the server that runs it: filtering happens as close as possible to the VM, including between two VMs in the same organization.
A rule uses the pf parameters that make sense for a VM: action (pass, block, reject), direction, protocol, ports, addresses, state tracking, and many other options.
Per-VM rules and security groups
Each VM has its own rules, and can belong to shared security groups, for example “web” or “admin”. A rule can allow the members of a group, or a set of addresses that you maintain just once for all your VMs.
Egress control
By default, a VM can send outbound traffic freely. You can reverse this policy to allow only the listed destinations: a database that only talks to your servers, or a compromised VM that cannot reach anyone.
Counters and logging
Each rule has its own counters, and packets can be logged: you can see in the portal what your firewall lets through and what it stops.
Included in your VDC
The firewall is not charged: only the resources (VMs, public IPs, storage…) are. You create the rules and groups you need, within the limits of your VDC’s quotas.
FIREWALL (FWAAS)
At a glance
🛡️
The pf firewall
pf’s options, applied to every VM.
🖧
As close as possible to the VM
Filtering on the VM’s own server, even between neighboring VMs.
🗂️
Groups and sets
Shared security groups and reusable address lists.
↗️
Egress policy
Unrestricted outbound traffic, or limited to the listed destinations.
📊
Counters and logging
What gets through and what is blocked, visible in the portal.
💶
No extra cost
Rules and groups included in your VDC.
PROCESS
How it works
Step 1 · Open only what you need
Only allow the ports your services need, for example 80 and 443 for a website.
Step 2 · Restrict administration
Limit SSH (22) and remote desktop (3389) to your known IP addresses.
Step 3 · Separate roles
Put the database in a group that only accepts connections from your web servers, and limit its outbound traffic.
FREQUENTLY ASKED QUESTIONS
Good to know
What is a security group?
A set of firewall rules applied to one or more instances. Each rule allows a flow based on its direction, its protocol (TCP, UDP, ICMP), its port and its source. Inbound traffic that is not allowed is blocked.
Is the firewall charged?
No. Security groups are included: only the resources of your VDC (instances, public IPs, storage…) are charged.
How do I allow SSH access to my instance?
Add an inbound TCP rule on port 22 to the instance’s security group, with your public IP address as the source (for example 203.0.113.10/32) rather than 0.0.0.0/0, which would open access to the entire Internet.
What does the firewall block by default?
Inbound connections that your rules do not allow are blocked. Outbound traffic is allowed, unless you choose the restrictive egress policy.
What is FWaaS (Firewall as a Service)?
A firewall provided as a cloud service: you describe your rules from the portal or the API, and the platform applies them. At Gridale, FWaaS is built on pf, OpenBSD’s firewall, applied to every VM.
GRIDALE CLOUD
The other services in your VDC
How the Gridale cloud works
The Gridale cloud combines proven building blocks (OpenBSD, KVM, etcd, pf, relayd) around simple, auditable code. …
Your virtual data center (VDC) in France
A VDC brings your entire infrastructure together in an isolated space: servers, networks, firewall, VPN, storage …
Virtual servers hosted in France
Choose a predefined configuration or build your VM by the vCPU, by the GB of RAM and by the GB of disk. Linux and …
Encrypted VMs, from disk to memory
Encrypt each VM’s disk with AES-256 using a key unique to that VM, and its memory with the AMD processor. A …
Appstore: your applications ready in minutes
Choose an application and a VM size: the platform takes care of the rest, from installation to HTTPS, including …
Autoscaling: your servers follow the load
An instance group adds VMs when the load goes up and removes them when it goes back down. You pay for the capacity …
Routed SDN network: private networks and public IPs
Each organization has its own network, isolated from the others at the routing level. Your VMs communicate with …
VPN as a Service: IPsec and WireGuard
Connect your offices and your team members to your private network in the cloud, without exposing your servers to …
Ready to launch your project?
Estimate your infrastructure in two minutes or talk it over with an engineer.
