URMSSecurity
A management server can reach every router it manages, so we treat it like critical infrastructure. This page describes what is in place today. Nothing here is aspirational.
Isolation between customers
One ACS instance per sandbox
Each sandbox runs its own ACS processes, on its own private network, with its own database and database user. One customer's instance can't read another's data.
A login for every router
Each router gets its own ACS username and a random 20-character password. Logins are checked per sandbox, so a login from one sandbox is refused by every other. Regenerating a password revokes the old one at once.
No shared management interface
The ACS engine's own admin interface isn't deployed. Your team works only through the URMS console, which checks your role on every request.
Hosted in Canada
The platform and its backups run on servers in Quebec, Canada.
Encryption
TLS in transit
The website, the console and the ACS endpoint use HTTPS with publicly trusted certificates. The website and console tell browsers to use HTTPS only (HSTS).
Router secrets encrypted at rest
Router passwords are stored encrypted with AES-256-GCM so they can be shown again to authorised staff. The key is kept apart from the database and is readable only by the service.
Account passwords hashed
Console passwords are hashed with Argon2id. We never send passwords by email: new accounts get a single-use setup link that expires after 24 hours.
Plain HTTP, only if you need it
Some routers can't do HTTPS. For them a plain-HTTP ACS port exists, which still requires the router's own login. We recommend HTTPS wherever the router supports it.
Access and accountability
Roles
Viewer, operator, admin and owner, enforced on the server for every action. Buttons a role can't use aren't shown.
Audit log
Changes, commands and every reveal of a password are recorded with the person and the time.
Session protection
Secure, HTTP-only session cookies, CSRF tokens and origin checks on every form, and rate limits on sign-in attempts.
Safe webhooks
Webhooks are signed with HMAC-SHA256. URMS only delivers to public addresses and doesn't follow redirects, so a webhook can't be used to reach internal systems.
Operations
Hardened servers
Key-only SSH, a firewall that opens only the ports the service needs, automatic security updates, and services running as unprivileged users in sandboxed units. Databases aren't reachable from the internet.
Backups
Daily backups of every sandbox and the console, kept for seven days, with checksums. Restores are tested. Off-site copies are being added.
No trackers
This website loads no third-party scripts, fonts or analytics, and sets no cookies.
Report a vulnerability
Found a problem? Email info@urms.cloud with "Security" in the subject. Please give us a reasonable time to fix it before disclosure. See also security.txt.