docs: document the host access model
State the privilege ranking on the Agentic Systems page: bots have no sudo, the steward can act only inside bot accounts, and root belongs to a separate key-only operator account. Update the Infrastructure page's least-privilege and backup statements to match.
This commit is contained in:
1 parent
a9df31b287
commit
cb270e51b9
2 files changed
+32
-5
No files matched your search
@@ -38,13 +38,19 @@ and deliberately kept apart from the member-facing applications. The steward bot
|
||||
— the automation behind the digests and the newsletter drafts — and the co-op's
|
||||
other agents live there. Keeping them on their own host means an agent problem
|
||||
stays an agent problem: it cannot reach the chat, the gateway or member data.
|
||||
Access to that host is SSH-key only — no agent or bot account has a password.
|
||||
The steward can act inside the bot accounts it maintains but cannot take root;
|
||||
root is a separate human operator account, so host-level changes stay with a
|
||||
person.
|
||||
|
||||
### Backups
|
||||
|
||||
Cloudron writes **encrypted** backups to Infomaniak's object storage in
|
||||
Switzerland every night and keeps the last **seven days**, so a failed upgrade
|
||||
or a lost server can be restored. The automation host keeps its own encrypted
|
||||
backup as well, with credentials kept apart from the agent's environment.
|
||||
backup as well, with credentials kept apart from the agent's environment. That
|
||||
backup runs as root from a root-owned script, so the agent can trigger it but
|
||||
cannot alter the backup code or read the backup keys.
|
||||
|
||||
### Domain and DNS
|
||||
|
||||
@@ -215,8 +221,10 @@ private, loopback, and internal addresses. The
|
||||
independent and independently rotatable, so a leak has bounded scope.
|
||||
- **No secrets in version control.** Credentials live in the hosting platform's
|
||||
environment, never in the repos.
|
||||
- **Least-privilege automation.** The steward agent runs as its own Unix user;
|
||||
host-level actions that need root are operator-controlled.
|
||||
- **Least-privilege automation.** Every agent runs as its own Unix user; bots have
|
||||
no `sudo`, the steward can act only within the bot accounts it maintains, and
|
||||
root belongs to a separate key-only operator account. Host-level changes are
|
||||
therefore deliberate human actions, not automation.
|
||||
- **Accepted trade-offs** (documented, not hidden): member keys are stored in
|
||||
the portal database so the co-op can serve them, and the API gateway must stay
|
||||
publicly reachable. Its admin surfaces are disabled; only the public API is
|
||||
|
||||
Reference in new issue
Block a user