MikroTik Router Security Hardening Checklist
A practical checklist to secure a MikroTik router: admin users, services, MAC and neighbor access, input firewall, DNS, SSH settings, updates and time sync.
Problem
Many MikroTik routers are hacked because they are left with default settings: open services, the default admin user, old firmware and no input firewall. This checklist closes the common holes.
Symptoms (signs of a compromised router)
- Unknown users, scripts, schedulers or proxy settings.
- High CPU and traffic you cannot explain.
- Log entries with many failed logins from foreign IPs.
Likely causes
Open management services on the WAN, weak or default passwords, outdated RouterOS, and a missing input firewall.
Prerequisites
- Access from the LAN and a fresh export:
/export file=before-hardening. - Use WinBox Safe Mode while you work.
Solution (WinBox / CLI)
1. Use your own admin account and disable admin:
/user add name=netadmin group=full password=Use-A-Long-Unique-Password
/user disable adminLog in again as netadmin before disabling admin.
2. Turn off services you do not use and limit the rest to the LAN:
/ip service disable telnet,ftp,www,api,api-ssl
/ip service set winbox address=192.168.88.0/24
/ip service set ssh address=192.168.88.0/243. Limit MAC access and discovery to the LAN:
/tool mac-server set allowed-interface-list=LAN
/tool mac-server mac-winbox set allowed-interface-list=LAN
/tool mac-server ping set enabled=no
/ip neighbor discovery-settings set discover-interface-list=LAN4. Turn off unused features:
/ip proxy set enabled=no
/ip socks set enabled=no
/tool bandwidth-server set enabled=no
/ip upnp set enabled=no5. Input firewall. Make sure the input chain ends with a drop for everything not from the LAN (see Basic internet setup) and that DNS is not open to the WAN.
6. Stronger SSH and up-to-date software:
/ip ssh set strong-crypto=yes
/system package update set channel=stable
/system package update check-for-updates7. Correct time (needed for logs and certificates). On RouterOS v7:
/system clock set time-zone-name=Asia/Dhaka
/system ntp client set enabled=yes servers=time.google.comVerification
- From outside (mobile data), WinBox and SSH to your public IP must fail.
/user print,/system script print,/system scheduler printand/ip proxy printshow only what you created./log print where topics~"account"shows logins.
Common errors
- Disabling
adminbefore testing the new user. - Limiting WinBox to an address list that does not include your own PC.
- Leaving UPnP on: devices can open ports on your router by themselves.
Rollback
Re-enable a service or user with enable, for example /ip service enable www or /user enable admin. Compare with before-hardening.rsc if something stops working.
This topic is covered hands-on in MTCSE — MikroTik Certified Security Engineer.
View MTCSE