Free operator worksheet

Router access audit checklist

Find who can reach your routers, what they can change and how you would recover access. Copy or print this worksheet; no email or account is required.

Tick items here or print a blank copy. Ticks stay on this page until you reload; they are not saved or sent. Use Print / save PDF to keep your progress.

Set the audit boundary

Review one site or router group at a time with its network owner. For each item record pass, needs work or not applicable, an owner, and a restricted evidence reference. Do not paste passwords, private keys, tokens, raw configuration exports or subscriber details into this worksheet.

This is an operator audit, not an automated security scan or a claim that ISPAgents enforces every control. Verify changes on an isolated lab router first. Keep an approved recovery access path before changing accounts or firewall rules.

Review recordFill in
InventorySite, router model, firmware and business owner
ReachabilityApproved management networks, VPN/jump host and recovery route
People and systemsStaff roles, service-account owners and external maintainers
FindingsEvidence date, risk, remediation owner and retest date

1. Shared and default administrator passwords

Use MikroTik's router security guidance alongside your vendor's supported-release guidance.

2. Per-staff accounts and service identities

RouterOS user documentation describes group policies and their limits. Do not assume a router role can express every desired per-command restriction.

3. API, REST, Winbox and other services

Check RouterOS Services and REST API requirements for the exact version. Service address restrictions complement firewall controls.

4. Management VLAN and access rules

MikroTik's security guidance includes MAC access and discovery restrictions. Check switch-port and bridge membership as part of the same review.

5. Backup, export and recovery

Read RouterOS Backup and Configuration Management for version and restore limitations. Record what was actually restored, not just whether the file opened.

6. Audit trail and change ownership

For RouterOS, consult the logging documentation when selecting topics and remote logging options supported by your release.

7. Leavers, contractors and lost devices

Review findings and ISPAgents scope

Prioritize exposed management interfaces, unowned administrator access and untested recovery. Give every finding an owner and retest date; do not report the audit as complete while a material access gap remains unexplained. Use the FreeRADIUS readiness checklist for AAA dependencies and the migration checklist when changing systems.

ISPAgents' MikroTik RouterOS REST operations are a guided pilot. REST client and backup-export foundations exist, but guarded writes, packaging, reachability UX and RouterOS 6 fallback remain product work. Private Access/WireGuard peer, gateway, session and lease surfaces are implemented but launch-gated; fresh remote-session and transport proof is not established. Site reachability is guided pilot only. This checklist does not establish that ISPAgents supplies or enforces your management access controls.

For the ISPAgents REST backup-export pilot, confirm RouterOS version, HTTPS management access with certificate validation and a restricted account. SNMP observations are not configuration backups; an export does not prove full recovery.

Optional: discuss your checklist findings with an operator.