Files
MIKROTIK-RMM/docs
GustavoandClaude Sonnet 5 5b926d637b docs: record upstream security audit (Mission 01)
- docs/AUDITORIA_BASE_2GT.md: full audit of upstream 1a4b635 (v0.24.5-beta)
  - 0 critical, 1 high (SEC-002: no per-site RBAC), 4 medium, 5 low, 5 informational
  - Verdict: APROVADO COM CORREÇÕES OBRIGATÓRIAS
  - First read-only RB: authorized (SIM)
- test: add regression coverage proving SEC-001 (no JWT revocation) and
  SEC-002 (site scoping has no per-user authorization component)
- docs/SISTEMA_ATUAL.md: record confirmed facts (RBAC scope, Change Guard
  coverage, RouterOS TLS verification) surfaced by the audit

No production code changed — audit-only per mission scope.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-08 18:32:03 -03:00
..
2026-09-07 21:42:55 -07:00
2026-09-07 21:42:55 -07:00

MikroTik Manager documentation

Reference material for people already running the platform. If you are still deciding whether to try it, the project README is the better starting point.

Document Covers
Configuration Environment variables, secret management and key rotation
Sites Grouping devices into sites, switching between them, and what each site scopes
Change Guard and Config Health How the safety system works, its settings, and what to expect when it fires
Alerting Alert rules, delivery channels, webhooks, scheduled reports, maintenance windows
Single sign-on (OIDC) Identity provider setup, group-to-role mapping, break-glass behaviour
CAPsMAN How centrally provisioned access points are modelled, and current limits
Cellular (LTE) Signal, carriers, tower movement, and the data-cap reset SMS
SSH keys Per-device keypairs, rotation, and what installing one costs
Bulk commands Running one command across a fleet, in waves
Firmware rollouts Waves, the upgrade pipeline, and what upgrading several at once costs
Backups Finding, reading, comparing and deleting configuration backups
Polling and scaling Poller health, headroom, tuning, and clearing a backlog
API and automation Scoped tokens, authentication, and driving the platform from scripts
Architecture How the system is put together, for contributors

Conventions used here

  • Settings in the UI are stored in the database and apply without a restart.
  • Environment variables live in .env and require a container restart to change.
  • Anything described as read-only makes no writes to your devices.

Which version is this?

These pages describe a specific release, shown in the header. The platform ships frequently, so if something here does not match what you see, check that the version you are running matches the version you are reading.