docs(security): document hive-priv privilege separation model
This commit is contained in:
parent
b33b3f315c
commit
28df69286d
2 changed files with 55 additions and 2 deletions
|
|
@ -51,9 +51,12 @@ Suggested sequencing of the `area:ops` issues:
|
|||
|
||||
1. **Gateway** first — pure ergonomics win, unblocks same-origin
|
||||
(lets the cross-origin CORS shim on `/answer-question/{id}` go
|
||||
away), no behavioural risk.
|
||||
away), no behavioural risk. ✅ **Done** — nginx gateway in front of
|
||||
all surfaces; per-agent UIs proxied under `/agent/<name>/`.
|
||||
2. **Network isolation** next — the step that makes the boundary
|
||||
real. Everything before it is honour-system.
|
||||
3. **Privsep** last — defence in depth on the core process
|
||||
itself; valuable independent of the other two, but the
|
||||
biggest refactor.
|
||||
biggest refactor. ✅ **Done** — `hive-c0re` dropped from root to
|
||||
`hive-core` user; `hive-priv` is the narrow root helper.
|
||||
See [`docs/security.md`](security.md) for the privilege boundary table.
|
||||
|
|
|
|||
Loading…
Reference in a new issue