One static IP for a remote team
An IP allowlist accepts connections only from the addresses on a list. A remote team has a different address for each person, and the addresses change. This guide shows four methods to give the team a fixed address, and the limits of each one.
A Policy permits the person
Only the people in a named Group can use the route to the SaaS app.
Traffic for the app uses a tunnel
The Client sends the traffic for that one app to the Gateway. All other traffic uses the normal path.
The app sees one fixed address
The traffic leaves from the public IP of the Gateway. That address is on the allowlist of the app.
All other addresses are refused
A person with a stolen password, at a different address, cannot connect to the app.
What an IP allowlist is
An IP allowlist is a list of IP addresses that a system accepts. The system refuses a connection from an address that is not on the list. Some products use the older term IP whitelist for the same feature.
An entry in the list is one address, such as 203.0.113.10, or a range in CIDR notation, such as 203.0.113.0/28.
The check occurs before the sign-in page or the API. A person at an address that is not on the list cannot try a password.
IP allowlisting works only if the address is static. A static IP is a public address that stays the same. The address of a home connection or a mobile connection is dynamic, and the internet provider can change it at any time.
Why SaaS apps, databases, and partners use an allowlist
An allowlist is simple to understand and simple to audit. Three types of system use one frequently.
- SaaS apps. Many business apps let an administrator limit sign-ins to trusted addresses. Typical examples are a code host, a CRM, a data warehouse, and a payments dashboard.
- Databases and cloud services. A managed database frequently has a firewall rule that names the permitted source addresses. The rule keeps scanners and password attacks away from the database port.
- Partners and vendors. A bank, a supplier, or a customer can ask for your address before it opens an API or an SFTP server to you.
The allowlist decreases the number of places from which an attack can start. A stolen password is of no use from an address that is not on the list.
The problem for a remote team
An allowlist was easy when all people worked in one office. The office had one public address, and one entry was sufficient.
A remote team breaks that model in three ways:
- Each person has a different address. Ten people at home have ten addresses, and one entry cannot cover them.
- The addresses change. A home router gets a new address after a restart. A phone on a mobile network changes address during the day.
- Some addresses are shared. A cafe, a hotel, or a mobile carrier puts many strangers behind one address. If you add that address, you permit all of them.
Some teams add each home address by hand. The list then becomes long and out of date, and it soon contains addresses that belong to other people.
Four methods to get a static IP for a remote team
1. The shared office IP
Remote people connect to the office VPN, and their traffic leaves from the office address. This method uses equipment that you own. It sends all traffic through one site, so it is slow for people far away. If the office connection fails, nobody can reach the SaaS apps.
2. A cloud NAT gateway with a fixed IP
A NAT gateway in a cloud account gives a fixed public address to the traffic that leaves a private subnet. It works well for servers in that subnet. A laptop is not in the subnet, so you must add a VPN or a tunnel to bring the laptop traffic there.
3. A consumer dedicated IP VPN
Some consumer VPN services sell a dedicated IP, an address that only your account uses. Setup is fast. The provider owns the address and the server, and it can read the metadata of your traffic. Most services have no groups, no rules for each app, and no logs for an audit.
4. An egress gateway with access policies
An egress gateway is a server that you run, with a fixed public address. A client on each device sends only the selected traffic to it. A policy decides who can use the gateway, and for which apps. This method needs a small server, and it gives you the address, the rules, and the logs.
An allowlist is one layer, not the full defense
A static IP allowlist does not replace authentication. The address tells the app where a connection comes from. It does not tell the app who the person is.
- Keep single sign-on and multi-factor authentication on. Each person behind the address must still prove their identity.
- Control who can use the address. If any person can route through the fixed address, the allowlist protects nothing.
- Use two or more addresses. One gateway is one point of failure. Add the address of each gateway to the list.
- Keep the list short. Remove an address when you stop the server that used it. A cloud provider can give an old address to a different customer.
- Test before you enforce. Add the new address, check that it works, and then turn on enforcement. An error here can lock out the administrators.
Some apps do not apply the allowlist to each access path. Read the documentation of the app to learn if the list covers API tokens and integrations.
How Firezone gives a team a static IP
Firezone uses the fourth method. A Firezone Gateway with a public IP works as an egress gateway, and a Policy controls who can use it. The documentation calls this setup a NAT gateway.
- Deploy a Gateway with a fixed public IP. Put it in a Site that you keep for this purpose, in your own cloud account.
- Add a DNS Resource for each app. Use the name of the SaaS app, with a wildcard for its subdomains if necessary. You can limit the Resource to TCP port 443.
- Write a Policy. The Policy names the Group that can reach the Resource. People outside the Group get no route.
- Add the Gateway IP to the allowlist of the app. The SaaS access guide gives each step.
Only the traffic for the selected Resources goes through the Gateway. Video calls and personal traffic use the normal path of each device. Each session is logged, so an audit can show who used the route.
A Gateway in each region
Put a Gateway near each group of people, all in one Site, and add each address to the allowlist. Firezone sends each person through the closest healthy Gateway. If one Gateway fails, the Client moves to a different one.
An office IP, a dedicated IP VPN, and Firezone
The three approaches all give a remote team a fixed address. They are different in who controls the address and who can use it.
| Office IP | Dedicated IP VPN | Firezone | |
|---|---|---|---|
| Fixed address on the allowlist | Yes | Yes | YesThe public IP of each Gateway |
| You own the address and the server | Yes | NoThe provider owns them | YesIn your cloud account |
| Rules for each group and each app | PartialDepends on the VPN | No | YesOne Policy for each Resource |
| Only the selected apps use the route | PartialOnly with split tunnel | PartialDepends on the service | YesEach DNS Resource |
| An exit near each person | NoOne office | PartialThe locations the provider sells | YesA Gateway in each region |
| Sign-in with your identity provider | PartialDepends on the VPN | No | Yes |
| Log of each session | PartialDepends on the VPN | No | Yes |
The table describes the usual design of each category. A specific product can be different. Read the documentation of the product before you decide.
Common questions
What is a static IP allowlist?
A static IP allowlist is a list of fixed public addresses that a system accepts. The system refuses connections from all other addresses. Companies use it to limit access to SaaS apps, databases, and partner systems.
How do I get a static IP for a remote team?
Send the traffic of the team through a server that has a fixed public address. The server can be the office VPN, a consumer dedicated IP VPN, or an egress gateway that you run. Then add the address of that server to the allowlist.
Is IP allowlisting sufficient for security?
No. An IP allowlist is one layer. It shows where a connection comes from, not who the person is. Keep single sign-on and multi-factor authentication on, and control who can use the permitted address.
Is a cloud NAT gateway sufficient for remote workers?
Not by itself. A cloud NAT gateway gives a fixed address to servers in a private subnet. A laptop at home is not in that subnet. You need a tunnel that brings the laptop traffic to the cloud first.
Does all my traffic go through the Gateway?
No. With Firezone, only traffic for the Resources that you add goes through the Gateway. All other traffic uses the normal internet connection of the device.