Access review.
Who has access to Hydrate's production systems, how that access is maintained, and what happens when someone leaves.
Version 1.0 · Effective: 2026-04-24 · Owner: Seamus Waldron · Covers: SOC2 CC5 · Cadence: Quarterly
Resources in scope
| Resource | Access method | Authorised users |
|---|---|---|
| Mac Mini production server | SSH via Tailscale | Seamus Waldron |
| GitHub sedasoft organisation | GitHub account | Seamus Waldron, David Bosdet |
| Cloudflare account (gethydrate.dev) | Cloudflare web UI | Seamus Waldron |
| 1Password (secrets) | 1Password account | Seamus Waldron, David Bosdet |
| GitHub Actions secrets (signing certs, VSCE_PAT) | Via GitHub Actions | Seamus Waldron |
| OpenAI API key (production extraction) | Environment variable on Mac Mini | Seamus Waldron |
Quarterly review procedure
Conducted at the end of each quarter, target same week as post-market surveillance review.
Offboarding trigger
When a contributor leaves, the following steps are taken immediately, not deferred to the next quarterly review:
Enterprise
For Enterprise deployments, customers are responsible for their own access review on the infrastructure they manage. Sedasoft does not hold administrative access to customer-managed infrastructure.
For team features (Hydrate team sync), the team manifest defines manager emails. Managers are reviewed quarterly by the Enterprise account holder and can be updated via the manifest.