Guide

The Ultimate 2026 Guide to Securing Your Home Router for Remote Work

The transition to permanent remote and hybrid work models has radically altered the cybersecurity perimeter. Your company's multi-million dollar enterprise firewall is practically useless if you are accessing…

By SecureBusinessHub Editorial, International cybersecurity desk — · 10 min read

The shift to remote and hybrid work changed the security perimeter. Your company's enterprise firewall doesn't protect data that flows through a consumer-grade router sitting next to someone's television.

Attackers scanning for corporate access no longer target enterprise perimeters directly. They scan residential IP blocks for vulnerable home routers belonging to remote employees. Once in, they can intercept VPN credentials or pivot into the corporate environment.

Securing your home router is mandatory if you're working remotely with anything sensitive. Here's what to do.

Step 1: Change the default credentials

Every router ships with a default admin username and password, usually something like admin/password, and those defaults are in public databases. First thing when setting up or resetting a router: access the admin panel (typically 192.168.1.1 or 10.0.0.1) and change both to something randomly generated.

If your router supports 2FA for the admin panel, enable it. Most leading brands added this as standard in 2026.

Step 2: Enforce WPA3 encryption

If your router is still using WPA2, or worse, your wireless traffic is vulnerable to straightforward decryption attacks. Set the security mode to WPA3 Personal.

If you have older devices that can't connect to WPA3, WPA2/WPA3 Transitional (mixed mode) is an acceptable compromise. It uses WPA2 AES while prioritizing WPA3 for capable devices.

Step 3: Disable WPS and UPnP

Two features built for convenience that you should turn off:

  • Wi-Fi Protected Setup (WPS): The button that lets devices connect without a password is brute-forceable. Disable WPS entirely in your admin settings.
  • Universal Plug and Play (UPnP): UPnP lets devices automatically open ports on your router's firewall to communicate with the internet. Malware abuses this to give attackers external access. Turn it off. If something legitimately needs a port open, configure it manually via port forwarding.

Step 4: Create a dedicated IoT and guest network

Your work laptop shouldn't share a network with your smart thermostat, security cameras, or anyone's personal phone. IoT devices rarely get security updates and are common initial targets.

Use your router's guest network feature to create a second SSID for all non-work devices. Put it on the 2.4GHz band, and make sure the option that allows guest devices to see your main network is turned off. A compromised smart bulb should have no path to your laptop.

Step 5: Disable remote management

Remote management lets someone configure your router from outside your home network. Unless you have a specific reason to need that, turn it off. Router administration should only be possible from inside the local network.

Step 6: Automate firmware updates

Router firmware has bugs that manufacturers find and patch over time. Running outdated firmware is the same as skipping operating system security updates. Enable automatic firmware updates in your admin panel. If your router is more than five years old and no longer receiving patches, replace the hardware.

NIS2 requirements: the second regime to know about

Data protection law is not the only European regime a business gets asked about. The NIS2 directive sets baseline cybersecurity and incident-reporting obligations for organisations in a defined list of sectors, and it is the source of most of the security questions that now arrive attached to contracts. The two regimes cover different ground: data protection law governs personal data and what people can ask you to do with it, while the NIS2 requirements govern the security and resilience of network and information systems, whether or not personal data is involved. A single incident can engage both, on separate clocks, to separate authorities.

The directive applies to organisations in its listed sectors that are at least medium-sized, meaning broadly fifty or more employees or turnover and balance sheet above ten million euros. That size rule puts most small businesses outside its direct scope, and the honest answer for a ten-person company is usually that the directive does not regulate it. What the size rule does not do is keep the requirements away, because one of them is supply chain security: organisations inside scope are expected to consider the security practices of their direct suppliers, and the way that expectation shows up in the world is as a questionnaire in your inbox.

The measures the directive names are a reasonable checklist for any business, which is why they are worth knowing even when they do not apply to you directly. They cover risk analysis and written security policies, incident handling, business continuity and backups, supply chain security, secure development and vulnerability handling, basic cyber hygiene and training including for management, encryption and access control policies, and multi-factor authentication. Reporting is staged and fast for the organisations it covers: an early warning within twenty-four hours of becoming aware of a significant incident, a fuller notification within seventy-two hours, and a final report within one month.

Because the directive is national law in each member state rather than a single rulebook, the details of scope, thresholds and reporting differ by country. For a fuller explanation of the instrument itself, see our guide to what the NIS2 directive is, and for the supplier side of the supply chain obligation, our walkthrough of vendor risk assessment. The reporting clocks that run alongside data protection deadlines are covered in data breach notification requirements.

Frequently asked questions

Does NIS2 apply to a small business?

NIS2 generally applies to organisations in its listed sectors that are at least medium-sized, meaning broadly fifty or more employees or turnover and balance sheet total above ten million euros. Most smaller businesses fall outside its direct scope, unless a member state has specifically designated them or they sit in one of the size-independent categories such as DNS service providers or trust service providers. Being outside scope does not stop the directive reaching you through customers who are inside it.

What is the difference between GDPR and NIS2?

GDPR governs personal data: what you may collect, why you may hold it, and what rights people have over it. NIS2 governs the security and resilience of network and information systems in specific sectors, whether or not personal data is involved. One incident can engage both regimes at once, on separate reporting clocks and to separate authorities.

How long do you have to report a data breach?

Under the European model, a personal data breach is reported to the supervisory authority without undue delay and, where feasible, within seventy-two hours of becoming aware of it, and affected individuals are told without undue delay where the risk to them is high. Organisations in scope of NIS2 carry a separate obligation: an early warning within twenty-four hours, a fuller notification within seventy-two hours, and a final report within one month.

Does a small business need a data protection officer?

Under GDPR a data protection officer is required where the organisation is a public authority, where its core activities involve regular and systematic monitoring of people on a large scale, or where its core activities involve large-scale processing of special category or criminal offence data. Most small businesses meet none of those tests and are not required to appoint one, though naming someone internally as the contact for privacy questions is worth doing regardless.

What should a small business do when a client's security questionnaire asks about NIS2?

Answer what you actually do rather than what you think the client wants to hear. The questions usually cover written security policies, incident handling and how fast you would notify them, multi-factor authentication, access control when staff join and leave, backup and recovery arrangements, and which of your own subprocessors touch their data. Gaps are common, and disclosing one with a date for closing it lands far better than an answer that does not survive the follow-up question.

Do these rules reach a business based outside the EU?

They can. GDPR reaches organisations outside the EU that offer goods or services to people in the EU or monitor their behaviour, and other regions have their own regimes with their own triggers. NIS2 obligations follow the sectors and the member states that transpose it, but its supply chain expectations travel through contracts, which is how they reach suppliers anywhere in the world.

Related reading