Security and privacy
What is protected, from whom, and what to keep out.
Your data is sealed with your passkey
Your saved configurations, the specification of each instance and its secrets (admin token, keys, database password) are encrypted with a key that only your passkey can unlock. The unlocking happens in your browser, and the passkey's secret never leaves it. The service holds your key in memory while you are signed in, and drops it after at most 24 hours or when the service restarts.
So a stolen database or backup, or an administrator who reads the stored data, learns nothing you put into a configuration or an instance. The one exposure is the running service itself while you are signed in, since it holds your key in memory then.
What the operators can see
- Who has an account, their name and email, and which capabilities they were given.
- That an instance exists, its label, status, expiry and public addresses.
- An audit log of who did what and when (not the content).
That is deliberate: it lets expired instances be removed and stopped instances be managed while nobody is signed in.
No recovery
If you lose every passkey, your sealed data cannot be recovered by anyone. Add a second passkey on a different device or key as soon as you register. These are throwaway test environments, so losing one costs a few minutes, not an incident.
Instances are separate from the console
The console runs on its own address and its passkeys work only there. Instances run on separate addresses of their own, and an instance cannot ask for, or use, the console's passkeys. Instances run what you configure, including images you name if you were given permission, so treat an instance as untrusted from the console's point of view.
Keep out
- Real personal data, real credentials, and anything you would not want a test system to lose.
- Long-lived secrets. Instance credentials are for the instance's lifetime.
Found a security problem? Tell your SIROS contact, or write to info@siros.org, before telling anyone else.
