Independent home-network planning tools
GUIDE / SECURITY

Firewall, port forwarding and secure remote access

Minimize public exposure and keep NAS and management interfaces behind a VPN.

Block unsolicited inbound traffic by default

A stateful firewall normally allows replies to outbound sessions and blocks unsolicited inbound sessions. Do not expose router administration, SSH or NAS administration directly to the public Internet.

Preferred order

  1. VPN: Authenticate into the home network with a protocol such as WireGuard.
  2. Vendor relay: Use only maintained services with MFA and scoped accounts.
  3. Port forwarding: Use only when unavoidable and limit it to one service and host.

Review these features

  • Automatic UPnP port mapping
  • Router administration from WAN
  • Unused WPS
  • Default administrator credentials
  • Unsupported or stale firmware

If forwarding is unavoidable

Patch the service, require strong authentication and MFA, log access and rate-limit failures. Restrict source IPs where possible. Never expose a NAS management port or SMB 445/TCP directly to the Internet.

Monthly security check

  • Update router, AP and NAS firmware
  • Review listening ports and UPnP mappings
  • Review administrator and VPN accounts plus MFA
  • Investigate unknown DHCP clients
  • Verify configuration backup and restore

Field case

Assume a NAS administration port was forwarded for remote files. Remove the public administration path and require a maintained VPN plus MFA before reaching only the required service.

Step-by-step verification

1. Record public mappings. 2. Disable UPnP mappings and WAN administration. 3. From mobile data, authenticate to the VPN and test NAS access, failure logs and lockout.

Interpretation

An administration page reachable without VPN means exposure remains. VPN-only internal access with closed public probes is closer to the target state.

Applicability limits

VPNs still require patching, key protection and account revocation. Review CGNAT, IPv6, relay services and local rules separately.

Completion criteria

  • Decisions and assumptions are written down.
  • Capacity, security and rollback checks are complete.
  • The design was tested against actual device, ISP and local requirements.

Open related worksheet/tool