How to Edit Firewall Settings | Access OS Security Interface

Editing firewall settings requires accessing the operating system’s security interface: Windows Security, macOS System Settings, or hardware management consoles.

Whether you need to unblock an app, open a port for a game server, or lock down a network, editing firewall settings controls what traffic passes through. The exact menu varies by platform, but the logic stays the same: choose which programs or ports to allow or block and which network profiles apply. Below we cover the actual interfaces on the most common systems, plus the mistakes that trip people up.

Where Do You Find Firewall Settings on Windows?

The firewall settings for Windows 10 and 11 live inside the Windows Security app under Firewall & network protection. From there you manage separate profiles for Domain, Private, and Public networks.

  1. Press Win + S, type “Windows Security,” and open the app.
  2. Select Firewall & network protection.
  3. Click the active network profile (Domain, Private, or Public) to see its current status.
  4. Toggle Microsoft Defender Firewall on or off.
  5. To allow an app through the firewall, click Allow an app through firewall, then Change settings and Allow another app.
  6. For advanced rule editing (ports, protocols, custom rules), click Advanced settings to open the Windows Defender Firewall with Advanced Security console. Then edit Inbound Rules or Outbound Rules.

Always use the Allow an app through firewall method rather than turning the firewall off. Microsoft’s official guidance on Windows Security Firewall explains each option in detail.

How to Edit Firewall Rules on macOS

On macOS 14 Sonoma and macOS 15 Sequoia, the built-in firewall is controlled through System Settings. You turn it on, then add or remove apps under the allowed list.

  1. Open System Settings (Apple Menu → System Settings).
  2. Go to NetworkFirewall.
  3. Toggle the firewall On.
  4. Click Edit to add or remove services and apps. Set each to Allow, Deny, or Block.
  5. Use Advanced to enable Stealth Mode, which stops the Mac from responding to unsolicited connection requests (ping, probing).

macOS does not have a separate advanced rules console like Windows — the built-in firewall handles app-level blocking only. For port control, you’ll need a third‑party tool or the command‑line pfctl utility.

Editing Firewall Settings on Windows Server 2025

Server administrators use the Windows Defender Firewall with Advanced Security snap‑in inside Server Manager. The process mirrors the desktop version but supports more granular rules for business environments.

  1. Log in as an Administrator.
  2. Open Server Manager.
  3. Go to ToolsWindows Defender Firewall with Advanced Security.
  4. Browse to Inbound Rules (or Outbound Rules). Right‑click and select New Rule to create a custom rule, or double‑click an existing rule to edit its properties.
  5. Define the program path (e.g., C:\Program Files\MyApp\app.exe), choose Allow or Block, select the profiles (Domain, Private, Public), and give the rule a name.

Windows Server 2025 also adds a simplified rule wizard, but the Advanced Security console remains the most reliable interface for complex configurations.

Third‑Party Hardware Firewalls (Check Point Example)

Enterprise hardware firewalls like Check Point and Cisco ASA use either a web‑based management page or a remote command‑line interface (SSH). The rule table is the core: you define source, destination, service (port), and action.

  1. Access the firewall’s management interface: open its IP address in a browser or connect via SSH (e.g., ssh admin@192.168.1.1).
  2. Navigate to the Rules Table or Policy Definitions section.
  3. Create or edit a rule by specifying Source, Destination, Service (ports like TCP/443 for HTTPS), and Action (Allow or Deny).
  4. Apply Stateful Inspection to track connection states, and assign Network Zones (Internal, External, DMZ) to segment traffic.
  5. Save and install the policy. The changes take effect immediately.

Many hardware firewalls also offer a “deny all” default rule at the bottom of the ACL – always verify that it exists before going live.

Platform Access Method Rule Editing Location
Windows 10 / 11 Windows Security app → Firewall & network protection Advanced settings → Inbound/Outbound Rules
Windows Server 2025 Server Manager → Tools → Windows Defender Firewall with Advanced Security Inbound/Outbound Rules
macOS 14 / 15 System Settings → Network → Firewall Edit button under allowed apps list; Advanced for Stealth Mode
Check Point hardware Browser (web management) or SSH CLI Rules Table / Policy Definitions
Cisco ASA SSH or ASDM (Adaptive Security Device Manager) Access‑lists (ACLs) under configuration mode
Linux – UFW Terminal: sudo ufw enable Commands: ufw allow 22/tcp, ufw deny out to any
Linux – firewalld Terminal: sudo firewall-cmd Zones and services (--add-service=http)

What Are the Most Common Firewall Editing Mistakes?

Even experienced admins make errors that weaken security or break applications. The table below shows the four most frequent pitfalls and how to avoid them.

Mistake Consequence Prevention
Leaving “Allow All” as the last ACL rule All unapproved traffic passes through Always add a Deny All rule after your specific allows
Using shared admin accounts Violates least‑privilege; unauthorized changes may occur Create individual accounts with role‑based permissions
Creating rules only for one network profile App works on Private but fails on Public networks Enable the rule for all profiles the device uses (Domain, Private, Public)
Disabling the firewall to unblock an app Whole device becomes vulnerable Use the “Allow an app through firewall” exception instead
Applying new rules without testing Misconfigurations can lock you out or expose services Test in a non‑production environment with vulnerability scanning before deploy

Quick Reference: Firewall Settings Edit Sequence

Follow this order every time you change a firewall rule to avoid locking yourself out or leaving a gap:

  1. Back up the current configuration (export the rule set if your firewall supports it).
  2. Identify the exact app or port you need to allow or block.
  3. Select the correct profile (Domain, Private, Public) that matches the network the device actually uses.
  4. Create the rule using the methods above – always name it clearly (e.g., “Allow Steam Port 27015 UDP”).
  5. Test that the app works while keeping the firewall active. Use a port scanner or “telnet” to verify.
  6. Add a “Deny All” rule at the end of the ACL if your firewall doesn’t have one already.
  7. Document the change: note the rule name, date, and reason in an internal log.

References & Sources