IT Infrastructure & Cloud
Office VPN for Remote Work: Firewalls and Secure Setup
A VPN that is switched on is not necessarily secure. This guide covers how firewall and VPN duties divide, the full or split tunnel choice, hardening the VPN gateway, and access rules so remote work does not open the whole office network.
SEO and Content Specialist
8 min read
Short answer: an office VPN for remote work is secure when three things are in place. The VPN gateway is updated quickly and uses two-step authentication, the firewall limits what each user group can reach once connected, and the devices and accounts that connect are managed. A VPN only creates an encrypted path. How far that path reaches into the network is decided by the firewall rules.
Many offices set up an office VPN for remote work in a single afternoon and then never touch it again until something goes wrong. Yet the VPN gateway sits on the boundary between the internet and the internal network, the place attackers try most often. This article covers how firewall and VPN duties divide, the choice of traffic direction, how to harden the gateway, and the access rules that limit the damage if one account or one laptop is compromised. It is a decision guide for IT teams and management, not configuration steps for a specific brand.
Firewall and VPN: what does each one do?
A firewall is a device or software that filters network traffic according to set rules. A VPN (Virtual Private Network) is an encrypted tunnel that connects devices outside the office to the office network. They often live on one device, but their jobs differ.
| Aspect | Firewall | VPN |
|---|---|---|
| Main job | Decides which traffic may pass | Carries traffic from outside the office over an encrypted path |
| Question it answers | “Who may reach what?” | “How does a laptop at home connect securely?” |
| If configured loosely | Every VPN user can reach every server | Traffic is unprotected, or access is open to people who should not have it |
| Often forgotten | Rules between user groups | Updates and authentication for the gateway |
NIST SP 800-41 Revision 1 contains guidance on writing a firewall policy and on selecting, installing, testing, and running firewall products, so a firewall is treated as a policy that is maintained, not just a device that is switched on. The principle matches the network separation in Office VLANs: separation only means something when there are tested rules between the parts.
Full tunnel or split tunnel: choose by risk
The first decision when setting up a VPN is whether all of a user’s traffic is sent through the office or only part of it. Microsoft’s documentation for the Windows VPN calls these two approaches force tunnel and split tunnel, and states that the choice affects configuration, capacity planning, and security expectations.
| Full tunnel (force tunnel) | Split tunnel | |
|---|---|---|
| Traffic through the VPN | All of it | Only the registered destination addresses, such as internal servers |
| Inspection at the office | All traffic can be filtered by the office firewall | Internet traffic goes straight from the home, outside office filtering |
| Load on the office connection | Heavy, because every video call and download goes through too | Light |
| Suits when | The office must inspect all traffic, or user devices are not managed | Devices are managed and have their own protection, and office bandwidth is limited |
In a Windows configuration, according to the same documentation, full tunnel is the default when no routes are specified. Start with full tunnel if in doubt, then loosen it for specific services once it is measured that the load is a real problem. Tightening after users are used to the setup is much harder.
Secure the VPN gateway itself
A VPN gateway connected to the internet is a target. CISA states that remote access VPN servers are entry points into protected networks, and that attackers who exploit them can harvest credentials, execute code on devices, weaken encryption, hijack sessions, and read sensitive data such as configurations and keys. A real example: in January 2024, CISA issued Emergency Directive 24-01 because two flaws in Ivanti Connect Secure and Ivanti Policy Secure VPN products were being exploited widely and actively. US federal agencies were told to apply available updates and, later, to disconnect the affected products so they could be rebuilt.
Practical lessons for an office:
- Choose a standards-based, maintained product. The NSA and CISA guidance on selecting VPNs recommends standards-based solutions over proprietary ones, from vendors that routinely patch their flaws.
- Assign an owner for updates. The VPN gateway belongs on the update schedule like a server, with a named person responsible and an agreed installation window.
- Require two-step authentication. CISA states that users who enable MFA are significantly less likely to be hacked, because an attacker who steals one factor, such as a password, is still stopped by the second. For an overview of the methods, see What Is Two-Step Authentication.
- Restrict management interfaces. The admin pages of the firewall and VPN should open only from the management network or admin addresses, never from the internet. The broader principles of admin access are covered in Securing Server Admin Access.
- Turn on logs and read them. Failed VPN logins, logins from unusual countries or hours, and sessions that run too long are early signs of account misuse.
Set access per group, not “everyone can reach everything”
The most expensive VPN mistake is giving every user an address on the same network as the servers. Once one user’s laptop is infected, the attacker holds a way into the whole office. Put firewall rules between the VPN address pool and the internal network:
| Group | Example access opened | What stays closed |
|---|---|---|
| General staff | Internal applications, shared files | Servers, network device interfaces |
| Finance or HR | The application servers they actually use | Servers and data of other departments |
| IT team | The management network, through a separate admin account | Used only when needed and logged |
| Vendors or partners | One server and one agreed port, time-limited | Everything else |
The principle is the same as VLAN separation: deny everything, then open only what is needed. Each rule also gets an owner and a review date, so a finished vendor’s access does not linger. Accounts of departing employees must also be removed from the VPN, see When Should a Departing Employee’s Account Be Disabled.
Connected devices: company-owned or personal
NIST SP 800-46 Revision 2 covers telework and remote access for employees, contractors, partners, and vendors, with both organization-issued and personally owned (BYOD) devices. It stresses that all components should be secured against the threats identified through threat modeling. For an office, this means deciding up front:
- Which devices may connect. A company laptop with updates and protection installed is easier to trust than a personal device of unknown condition.
- Whether personal devices are allowed, and on what terms, for example only for certain applications.
- Who keeps the device records. The list can be built the way Asset and Software License Inventory describes.
When a VPN alone is not enough
A VPN gives access to a network, while many offices actually need access to one or two applications. NIST SP 800-207 on zero trust describes an approach that grants no automatic trust based on network location or device ownership, and that moves defenses from static perimeters toward users, assets, and resources. For a mid-sized office, the realistic path is gradual: limit the VPN with per-group rules as above, add two-step authentication, then consider per-application access for the most sensitive systems.
Checklist before opening the VPN for remote work
- List who needs remote access and to which systems.
- Choose full tunnel or split tunnel, and note why.
- Confirm the VPN gateway is standards-based, the vendor still releases updates, and there is a schedule for installing them.
- Require two-step authentication for all VPN accounts.
- Set firewall rules per user group; test with an account from each group that what should be closed really is closed.
- Restrict access to the firewall and VPN management interfaces.
- Turn on logs, and decide who reads them and how often.
- Decide which devices may connect and who keeps the records.
- Link VPN account removal to the departing-employee procedure.
- Document everything, including addresses, rules, and the owner of each rule.
How Legia does it
In the Office Network Installation service, installing and configuring the firewall and the VPN for access from outside the office is part of the work, together with a guest network separated from the office network. The rules are agreed in advance, and the configuration is handed over in the documentation. The network equipment used includes Cisco, MikroTik, and Ubiquiti, with the network divided using VLANs. Ongoing monitoring of network equipment and incident handling after installation is available through the IT Support & Infrastructure Management service, which is priced separately. For an overview of the stages of network work as a whole, see Office Network Installation Checklist. Other services in this pillar are on the IT Infrastructure & Cloud page.
Frequently asked questions
Is a VPN enough to secure working from home?
No. A VPN secures the path between the device and the office, but it does not check the device’s condition or limit what is reachable once connected. Two-step authentication, per-group firewall rules, and managed devices complete it.
Do we need a VPN if our office applications are already web-based?
It depends on the application. A web application opened over the internet with login and strong two-step authentication may not need a VPN, but internal systems such as file servers, databases, and admin interfaces should not be opened directly to the internet.
Which is safer, full tunnel or split tunnel?
Full tunnel gives the office a chance to inspect all traffic, but loads the office connection. Split tunnel is lighter, with the consequence that internet traffic does not pass through office filtering. Choose based on whether user devices are managed and how much bandwidth the office has.
How often should the VPN gateway be updated?
Follow the vendor’s security update releases and install them as fast as the installation window allows. The Ivanti example above shows that flaws in VPN products can be actively exploited before all users have had time to update, so updates need an owner and a clear schedule.
Sources
- NIST SP 800-41 Rev. 1, Guidelines on Firewalls and Firewall Policycsrc.nist.gov
- NIST SP 800-46 Rev. 2, Guide to Enterprise Telework, Remote Access, and BYOD Securitycsrc.nist.gov
- NIST SP 800-207, Zero Trust Architecturecsrc.nist.gov
- Microsoft Learn, VPN routing decisionslearn.microsoft.com
- CISA, CISA and NSA Release Guidance on Selecting and Hardening VPNscisa.gov
- CISA, Emergency Directive 24-01: Mitigate Ivanti Connect Secure and Ivanti Policy Secure Vulnerabilitiescisa.gov
- CISA, Multifactor Authentication (MFA)cisa.gov


