You're trusting us with your customers' cloud. Here's how we treat that.
rugged.sh reaches every customer tenant through a single, scoped, least-privilege connection, never a standing admin account. This page describes the real mechanisms behind that, not marketing language.
Least-privilege access, not standing admin
We never ask for Global Administrator on your tenant and never see your customers' passwords. Onboarding a customer grants one scoped app registration Graph permissions via admin consent, plus Owner role on their Azure subscription, exactly what's needed to deploy and govern, nothing more.
Hard tenant isolation, enforced in one place
Every row and every operation carries a partner and customer-tenant scope, checked at the data-access layer, not scattered across call sites. One MSP can never see another MSP's data, and a scoped staff login can be restricted to a subset of customer tenants.
Secrets in Key Vault, credentials never in our database
Production secrets (app credentials, signing keys, API tokens) live in Azure Key Vault behind managed identity, not in application config or source control. The one credential chokepoint in the codebase is the only thing that ever touches a token.
Every action is audited and attributable
Operator and MSP actions are written to an append-only audit trail. Requests carry a correlation id from the API call through to the background job that executes it, so any action can be traced back to who did it and when.
Backups that are actually tested
Postgres runs automated backups with point-in-time restore. We don't just take that on faith: we periodically run a real restore drill onto a throwaway server and verify every row count matches the live system before tearing it down.
MFA and email verification on every account
Self-serve signup requires email verification and multi-factor authentication (TOTP or email code) before console access, not as an opt-in extra. Sessions run over HSTS with secure cookies, and every mutating request is checked against its origin.
On formal certification
We are not SOC 2 certified today. The practices above are the same control categories a SOC 2 audit examines, and formal certification is on our roadmap as we grow. If your own compliance program needs a security questionnaire answered before you connect a customer tenant, reach out and we'll fill it out directly rather than pointing you back at this page.
Questions before you connect a customer?
Email [email protected] or open a ticket and a real person answers.