SEC-3: secrets threat model + reviewer FAQ (docs only) #54
No reviewers
Labels
No labels
bug
discussion
duplicate
enhancement
goal
help wanted
horizon:backlog
horizon:governance
horizon:mvp
invalid
operator-decision
question
roadmap
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
open-platform/mitosis!54
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/sec-3-secrets-threat-model"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
SEC-3 (roadmap #45): secrets threat model + reviewer FAQ
Doc-only. Adds
docs/security/secrets-threat-model.mdso a reviewer can state what decrypts what, who sees plaintext & when, how rotation/backup work, and why Vault is deferred — without reading source.Covers (all anchored to real code):
clusters/**sops value sealed to the one fork key; enforced empirically byfork_verify_all_sealed(bin/lib.sh:338). Includes a "what decrypts what" table.bin/lib.sh:180/207), the transient admin-runsync-envCI job (_app-template/.forgejo/workflows/sync-env.yml:100,mcp/src/secrets-cli.ts→syncAppEnvmcp/src/server.ts:1829), and the running app pod. Nowhere else (Forgejo secrets are write-only).mcp/src/secrets-cli.ts:141,mcp/src/server.ts:1892/1911).fork_backup_key(bin/lib.sh:681), lock-out-saferotate_age_key(bin/lib.sh:809).Closes #45.
🤖 Generated with Claude Code