Join our Newsletter — 33% off our NHI Course
Home› Guides› SOHO and SMB Router Hardening Guide: Admin Access,…
Guide Network Security

SOHO and SMB Router Hardening Guide: Admin Access, Lifecycle and Botnet Defence

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 8 November 2026 12 min read
On this page

Small office routers from D-Link, TP-Link, NETGEAR and DrayTek sit on the internet edge of thousands of businesses, and attackers keep turning them into botnet nodes and proxy relays. Each vendor publishes firmware updates, security advisories and support periods, and the settings in this guide are the owner's side of that shared responsibility. This guide is for IT managers, managed service providers and security teams who run these devices in branch offices, shops, clinics and small firms. It covers how admin access works, the credentials and integrations that matter, logging, a hardening baseline, end-of-life replacement and the misconfigurations behind most compromises. Consumer home setups are covered separately in the Securing Your Home Router Guide.

Key takeaways

  • End of life is the main risk. Vendors generally deliver security updates only within a product's support period, and the botnets disrupted by the FBI were built mostly on end-of-life routers.
  • Remote management off by default. The FBI's May 2025 warning links a newer TheMoon variant to end-of-life routers with remote administration enabled; management should be reachable only from the LAN or a VPN.
  • Admin credentials are shared machine secrets. One admin password often covers every branch router, sits in an MSP spreadsheet and never rotates. Give each device unique credentials stored in a vault, and add 2FA where the firmware supports it.
  • Logs leave the box or they do not exist. Small routers keep little local history; send syslog to a central collector and alert on admin logins, configuration changes and firmware events.
  • Track every model against vendor advisories. Keep an inventory with model, hardware revision, firmware and support end date, and check it against each vendor's security advisories and the CISA catalogue every week.

How identity and access work in SOHO and SMB routers

These routers have a much simpler identity model than enterprise firewalls, which is why they are easy to take over. Most have:

  • A local admin account: usually one built-in administrator, sometimes with optional extra admin users. Business ranges such as DrayTek Vigor let you create separate admin users; on DrayOS 5 this is under IAM / Users & Groups, and DrayTek suggests disabling the default admin account for WAN access.
  • A web management interface: HTTP or HTTPS on the LAN, often also reachable from the WAN when remote management is switched on. DrayTek notes that its routers use TCP port 80 for both the HTTP management page and the firewall block page.
  • Command line access: Telnet or SSH on many business models. DrayTek recommends HTTPS instead of HTTP and SSH instead of Telnet when remote access is needed.
  • VPN user accounts: remote access and site-to-site VPN credentials (pre-shared keys, local VPN users), which are a second door into the network.
  • Vendor cloud and app management: many models can be managed from a vendor cloud portal or mobile app, which ties the router to a vendor account that becomes an admin credential in its own right.

Few SOHO models support central authentication such as RADIUS or TACACS+ for admin logins, and role-based admin rights are limited or absent. That makes credential hygiene and network restriction the main controls.

Admin roles and privileged access

ControlWhat to setVendor documentation example
Unique admin per deviceRandom password of at least 16 characters, unique per router, stored in a vault; change at first loginFBI PSA I-050725-PSA advises unique, random passwords of 16 to 64 characters; DrayOS 5 forces a change at first login
Named admin accountsSeparate accounts for each engineer or MSP, default admin disabled for WAN accessDrayOS 5 IAM / Users & Groups
Two-factor authenticationTOTP on admin login where available; use mOTP, SMS or email codes as fallbacksDrayTek Vigor2960, Vigor3900 and Vigor300B firmware 1.5.0 or later: System Maintenance >> Administrator Password >> Administrator Advanced Authentication, per admin account
Management access listOnly management subnets or a jump host may reach the admin interfaceDrayTek Access List using IP Objects, IP Groups or Hostnames
Brute force protectionLock out source IPs after repeated failuresDrayOS 5 Brute Force Protection under System Maintenance >> Management (Fail to Ban on legacy firmware)
Management ports and protocolsHTTPS and SSH only; disable HTTP and Telnet; non-default ports reduce noise but are not a control on their ownDrayTek System Maintenance >> Management >> Management Port Setup

For D-Link, TP-Link and NETGEAR business models, the equivalent settings exist on many but not all models and firmware versions, under names that vary by range. Check the model manual for the hardware revision you run, and record where each control lives in your build standard. If a model cannot restrict management to the LAN or a VPN, treat it as unsuitable for business use.

Integrations, API tokens and service accounts

A small router holds more non-human credentials than most teams realise. Each one should have an owner, a storage location and a rotation trigger.

CredentialWhere it livesRisk if exposedHandling
Admin passwordRouter config, MSP documentation, backupsFull device takeover, traffic redirection, proxy installationUnique per device, vaulted, rotated on staff or MSP change
VPN pre-shared keys and VPN usersRouter config and every clientNetwork access from anywherePer-user accounts with TOTP where supported; disable unused VPN services, as DrayTek advises
Vendor cloud or app accountVendor portal, phone appsRemote admin of every router bound to the accountCompany-owned account, MFA, no personal email addresses
Dynamic DNS credentialsRouter configHijack of the hostname used for VPN or remote accessUnique password, review when staff leave
SNMP community stringsRouter and monitoring toolConfiguration disclosure; write access if read-write strings are setSNMPv3 where supported, read-only, restricted to the monitoring host
ISP management (TR-069/CWMP)ISP-supplied routersRemote configuration by whoever controls the management serverKnow whether it is enabled; ask the ISP what it is used for
Configuration backupsFile shares, laptops, emailContain every secret above, often weakly protectedEncrypted store, access-controlled, never emailed

For MSPs, the router admin credential is a privileged non-human identity shared across clients. Store it in a privileged access tool, check it out per session and log who used it. See the Edge Device Security Guide for the wider edge credential picture.

Logging and detection

Most SOHO routers keep a small rolling log in memory that is lost at reboot. Plan for that:

  • Send syslog off the device: configure syslog (traditionally UDP 514) to a collector at each site or across a VPN. DrayTek legacy firmware can also write syslog continuously to a USB disk.
  • Events to capture: admin login success and failure, configuration changes, firmware upgrades, VPN connections, WAN IP changes, reboots and firewall blocks against the management service.
  • Network signals: outbound connections from the router's own WAN address to unusual destinations, new listening services on the WAN interface, and traffic volumes that do not match office hours. These are the signs of proxy or botnet use, which the FBI ties to TheMoon variants on end-of-life routers.
  • Physical and user signals: the FBI lists overheating, connectivity problems and settings the administrator does not recognise as indicators of compromise.
  • External view: scan your own WAN addresses from outside every month to confirm no management, Telnet, UPnP or unused VPN service is exposed.

Metrics that show it is working

  • Share of routers within vendor support (target 100%, with a dated plan for the rest).
  • Share of routers with no WAN-reachable management interface, confirmed by external scan.
  • Median days from a vendor advisory for a model you own to patch or replacement.
  • Share of routers sending syslog to a central collector, checked weekly by last-seen time.
  • Share of routers with unique, vaulted admin credentials.

Hardening baseline

  1. Inventory: record vendor, model, hardware revision, firmware, serial, site, owner and vendor support status for every device. Check each against the vendor advisory pages and the CISA catalogue of exploited flaws.
  2. Replace end-of-life units: vendor end-of-life notices recommend moving to a current device, and the Justice Department warned after the KV botnet operation that remediated end-of-life routers remain vulnerable. Budget replacement before the support end date, not after.
  3. Update firmware: enable automatic updates where offered (CISA asks manufacturers to make this the default), or schedule monthly checks. NETGEAR publishes fixes in a monthly security patch update; TP-Link states remediation can take up to 90 days or longer.
  4. Lock down management: disable WAN-side management, restrict LAN management to an admin subnet, enforce HTTPS and SSH, and disable HTTP and Telnet.
  5. Set credentials: unique admin password per router, named admin accounts, 2FA where supported, brute force protection on.
  6. Reduce attack surface: disable UPnP, WPS, unused VPN protocols, unused port forwards and any cloud management feature you do not use.
  7. Segment: separate guest, staff, payment and device networks with VLANs; use WPA3 or WPA2 and 802.1X for staff Wi-Fi where the router supports it.
  8. Log and back up: syslog to a collector, NTP set, encrypted configuration backup after every change.
  9. Test and roll back: apply the baseline to one pilot site first, confirm VPN, VoIP and payment terminals work, keep the previous configuration backup, and roll forward to other sites in waves.

Security updates and advisories

Each vendor publishes security advisories: DrayTek, D-Link, NETGEAR and TP-Link. Apply each vendor's security updates promptly. As an NHI Mgmt Group recommendation, subscribe the device owner to each vendor's advisory feed and set a patch target in days for internet-facing routers.

Decision guidance

  • Consumer versus business models: for any site handling payments or personal data, choose a business range that supports named admin users, management access lists, syslog and a published support period. Confirm all four with the vendor before buying.
  • ISP-supplied routers: the ISP may control firmware and remote management. Either get written commitments on patching and management access, or put your own firewall behind it and treat the ISP router as untrusted.
  • Small single-site firms: the minimum is a supported model, remote management off, a unique vaulted password, automatic updates and a yearly external scan.
  • Multi-site estates and MSPs: standardise on one or two models, manage them centrally with MFA on the management platform, collect syslog centrally and track the fleet against vendor advisories automatically. Consider moving branches to a managed SD-WAN or firewall platform once the fleet passes a few dozen sites.

Framework mapping

FrameworkReferenceRouter control
NIST CSF 2.0ID.AM-08, PR.PS-02, PR.PS-03, PR.AA-05, DE.CM-01Lifecycle management, software and hardware replacement, least-privilege admin, network monitoring
NIST SP 800-53 Rev. 5SA-22, SI-2, CM-6, CM-7, AC-17, IA-2, AU-9Unsupported components, flaw remediation, secure configuration, least functionality, remote access, admin authentication, protected logs
CIS Controls v8.1Controls 1, 4, 7, 8 and 12Asset inventory, secure configuration, vulnerability management, audit logs, network infrastructure management
ISO/IEC 27001:2022Annex A 8.8, 8.9, 8.15, 8.20Technical vulnerabilities, configuration management, logging, network security
MITRE ATT&CK v20T1190, T1133, T1110, T1078, T1584.008, T1090.002Exploitation of the management interface, remote services, brute force, valid accounts, compromised network devices used as external proxies

Common misconfigurations

  • Remote management left on for convenience: an MSP enables WAN management to avoid site visits. This is the exposure the FBI links to TheMoon infections. Use a VPN or the vendor's authenticated cloud management with MFA instead.
  • One password everywhere: every branch router shares the same admin password, so one leaked backup or departed engineer compromises the estate.
  • Running past end of life: routers keep working long after updates stop. The KV botnet, attributed to the PRC-sponsored group profiled in the Volt Typhoon Threat Actor Profile, was built mostly on end-of-life routers. Reboot-only clean-up is not enough: the Justice Department notes a restart reverses its mitigation.
  • Unused VPN services listening: PPTP, L2TP or SSL VPN enabled at setup and never used, each an extra exposed service.
  • No logs off the device: after an incident there is no record of who logged in or what changed, because the router log was cleared at reboot.
  • Treating advisories for cameras and NAS as irrelevant: vendor advisories also cover cameras and network video recorders on the same small networks. Inventory every device class, not just the router.

When a router is suspected to be compromised, follow the Edge Device Compromise Investigation Playbook, and plan replacements with the Edge Device End of Life Replacement Playbook.

Practitioner checklist

  • Inventory every router with model, hardware revision, firmware and support end date.
  • Check the inventory against vendor advisories and the CISA catalogue weekly.
  • Replace end-of-life routers on a dated plan; do not rely on reboot or clean-up.
  • Disable WAN-side management; allow admin access only from an admin subnet or VPN.
  • Set a unique random admin password per device, stored in a vault, with named admin users and 2FA where supported.
  • Disable HTTP, Telnet, UPnP, WPS and unused VPN services.
  • Send syslog to a central collector and alert on admin logins and configuration changes.
  • Scan your own WAN addresses externally every month.
  • Keep encrypted configuration backups and treat them as secrets.
  • Pilot every baseline or firmware change at one site before rolling out.

Standards and references

Related NHI Mgmt Group resources: Securing Your Home Router Guide · Edge Device Security Guide · MikroTik RouterOS Hardening Guide · Botnets Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 8 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.