2.3 KiB
Permissions and security
Roles
| Role | Access |
|---|---|
admin |
Spaces, Space-to-data_operator assignment, capability probe, exclusive-prefix confirmation, scoped client Key/Secret creation/rotation/revocation, force lease release, reconcile, and client rollout policy. Devices are registered automatically after Key/Secret verification. |
data_operator |
Read spaces assigned through operatorUserIds and their sessions/items. Management-side abort and force operations require admin; client operations use independently scoped device credentials. |
pipeline_engineer |
Read final sessions and create/view immutable release records. |
compliance_auditor |
Organization-wide read-only audit and CSV/NDJSON export. |
Device credentials are independently scoped to sync space, allowed relative prefixes, and actions. They remain valid until administrator revocation. The API rechecks credential and device state on every new control request.
Local boundaries
- The daemon owns SQLite writes.
- Unix IPC is mode
0600. - Windows has one selected installation/state namespace and the sole pipe
\\.\pipe\drosync, with no user/system endpoint fallback. Remote pipe clients are rejected. Target Windows acceptance must cover standard-user/admin/cross-user ACL tests; a macOS source build does not certify those permissions. - User credentials are stored in Keychain, Credential Manager, or Secret Service.
- Headless secret files must be
0600; environment injection is accepted for orchestrated services. unsafeRust is forbidden in workspace crates.
Accepted residual risk
Existing BOS AK/SK records remain stored in MongoDB using the project's current storage representation. API responses mask secrets and organization/role checks isolate access, but no new at-rest application encryption is introduced in v1. This is an explicitly accepted, not eliminated, production security risk. Compensating controls are database encryption at rest, secret-aware backups, least-privilege BOS accounts, rotation, access logging, and restricted Mongo administration.
Prefix exclusivity
Do not enable update mode if any non-drosync writer can mutate the prefix. x-bce-forbid-overwrite is not a substitute, especially when bucket versioning is enabled. A drift observation immediately disables the space; reconciliation does not reopen it automatically.