sodcalculator

10 Tech How-To

Firewall & VPN Settings for Pending Patches

Guide 10-53768 · Updated · Step by step

When emergency patches are pending, tightening your firewall and VPN settings can meaningfully reduce your exposure to attacks that exploit the unpatched vulnerability. This article explains which specific settings to adjust, why they work, and how to apply them without breaking your network.

Why Emergency Patches Create a Window of Risk

Emergency patches are released when a vulnerability is actively exploited or has a high chance of being exploited. Between the moment a patch is announced and the moment it is applied to every device, your systems are exposed. Attackers know this window exists and often ramp up scanning and exploitation attempts immediately after a patch is published, because they can reverse-engineer the vulnerability from the patch itself.

During this window, your firewall and VPN are your primary defensive layers. They can block the specific network paths and protocols that the vulnerability uses, even if the underlying software is still vulnerable. The goal is not to replace patching, but to buy time and reduce the attack surface until the patch can be deployed.

Firewall Settings That Reduce Exposure

Firewalls control what traffic can enter and leave your network. During a patch window, you want to be more restrictive than usual. The following settings are the most effective:

  • Block inbound traffic on the affected port(s): If the vulnerability involves a specific service, such as RDP (port 3389), SMB (port 445), or a web application (port 80/443), block inbound connections to that port from the internet. If the service is only needed internally, block it from external IPs entirely.
  • Restrict source IPs: If the service must remain accessible, allow connections only from known, trusted IP ranges. Use a specific allowlist rather than a broad range.
  • Enable stateful packet inspection: Ensure your firewall is tracking connection states and only allowing responses to outbound requests, not unsolicited inbound traffic.
  • Disable port forwarding: If you have port forwarding rules set up for remote access, disable them temporarily unless absolutely necessary.
  • Increase logging: Turn on logging for blocked traffic and firewall denials. This helps you spot scanning attempts and identify compromised hosts early.
  • Update firewall rules automatically: If your firewall supports automation, push a temporary rule set that applies these restrictions across all devices at once, rather than manually editing each rule.

Remember to document every change you make so you can revert them after the patch is applied. A temporary block that becomes permanent can cause more problems than the vulnerability itself.

VPN Settings That Reduce Exposure

VPNs create encrypted tunnels for remote access. When a patch is pending, you want to make sure that tunnel is as tight as possible and that only authorized users can use it.

  • Disable split tunneling: Split tunneling lets remote users access the internet directly while also connected to the VPN. This can expose the VPN client to attacks from the internet. Force all traffic through the VPN tunnel so that the client is protected by your network’s firewall and security policies.
  • Require multi-factor authentication (MFA): If you haven’t already, enforce MFA for all VPN logins. This adds a critical layer of protection against credential theft, which is a common attack vector during patch windows.
  • Restrict VPN access to specific users or groups: Temporarily limit VPN access to only those who absolutely need it. Disable accounts for users who are on leave or no longer require remote access.
  • Update VPN client software: Ensure all VPN clients are running the latest version. Outdated clients may have their own vulnerabilities that can be exploited.
  • Set shorter session timeouts: Reduce the idle timeout and maximum session duration so that connections are dropped more frequently, reducing the window for session hijacking.
  • Disable unused VPN protocols: If your VPN server supports multiple protocols (e.g., PPTP, L2TP, IPsec, OpenVPN, WireGuard), disable any that you don’t use. Each enabled protocol is a potential attack surface.

After the patch is applied, re-enable split tunneling if it was a legitimate business need, but consider keeping MFA and the restricted access list in place as a security best practice.

How to Choose Which Settings to Apply

Not every vulnerability requires the same response. The key is to understand the vulnerability and your own network. Follow these steps:

  1. Read the advisory: The security advisory for the vulnerability will state which ports, protocols, and services are affected. Use that information to target your firewall rules.
  2. Assess your exposure: Determine if the affected service is exposed to the internet. If it is, apply inbound restrictions immediately. If it’s only on your internal network, focus on VPN access and internal segmentation.
  3. Prioritize critical systems: Apply the strictest settings to systems that hold sensitive data or are essential to operations. You may be able to leave less critical systems with standard settings.
  4. Test the changes: Before applying rules broadly, test them on a small subset of devices to ensure you don’t lock out legitimate users or break essential services.
  5. Have a rollback plan: Save a copy of your current firewall and VPN configurations so you can quickly revert if the temporary settings cause problems.

If you are unsure which settings to apply, err on the side of stricter restrictions. You can always loosen them later, but a breach is much harder to undo.

Common Mistakes and Pitfalls

Even with good intentions, mistakes happen. Here are the most common ones to avoid:

  • Forgetting to revert: The most common mistake is leaving temporary rules in place after the patch is applied. This can cause service outages and user frustration. Set a reminder to review and remove temporary rules.
  • Blocking the wrong port: Some vulnerabilities affect multiple ports or use dynamic ports. Read the advisory carefully and block all relevant ports, not just the obvious one.
  • Overlooking internal traffic: Attackers can move laterally within your network. Apply firewall rules not just at the perimeter, but also between internal segments if possible.
  • Disabling the VPN entirely: If you turn off the VPN completely, you may prevent remote administrators from accessing the network to apply the patch. Keep the VPN up but restrict access.
  • Ignoring IPv6: Many firewalls have separate rules for IPv6. If you block IPv4 but not IPv6, you may still be exposed. Apply the same restrictions to both address families.

Comparing Firewall vs. VPN Mitigations

Firewall and VPN settings address different parts of the attack surface. Firewalls primarily block network-level access, while VPNs control remote access and the security of the tunnel itself. In many cases, you need both.

For example, if a vulnerability affects a web server, a firewall rule blocking inbound traffic to port 443 would stop external attacks. But if an attacker compromises a VPN user’s credentials, they could tunnel into the network and reach the web server from the inside. That’s why you also need to enforce MFA and restrict VPN access.

The two work best together: the firewall blocks the direct path, and the VPN prevents indirect access through remote users. Use both as complementary layers, not as alternatives.

Frequently Asked Questions

Will these settings break my remote access?

They can, if applied too broadly. To avoid this, test the settings on a non-critical system first, and make sure you have a way to access the network (e.g., through a management console on a different port) in case the VPN is accidentally blocked. Always keep a backup of your configuration.

How long should I keep these temporary settings in place?

Only until the patch is applied and verified on all affected systems. Once the patch is installed, test that the service works, then remove the temporary firewall and VPN restrictions. Leaving them in place longer than necessary can cause operational issues.

What if I can’t block the affected port because it’s critical for business?

If you cannot block the port, restrict access to a specific allowlist of IP addresses and enforce MFA for any related remote access. You can also use an intrusion prevention system (IPS) to detect and block exploit attempts on that port. This is a less effective mitigation, so prioritize patching as soon as possible.

Do these settings work for zero-day vulnerabilities?

They help, but zero-days are unknown, so you may not know which port or service to block. In that case, focus on general hardening: disable unnecessary services, apply the principle of least privilege, and ensure your VPN requires MFA. Also, monitor your firewall logs for unusual traffic patterns.

Should I disable the VPN entirely during a patch window?

Usually no. If you disable the VPN, remote administrators may not be able to access the network to apply the patch, which prolongs the exposure. Instead, restrict VPN access to essential personnel and require MFA. Only disable it if you have an alternative secure remote access method.

Can I automate these temporary settings?

Yes, many enterprise firewalls and VPNs support automation via APIs or configuration management tools. You can create a script that applies the temporary rules, and a second script that reverts them after a specified time or after the patch is confirmed. This reduces the risk of human error.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →