Role-based access control
Permissions are evaluated server-side; the interface only mirrors them.
- Roles stored separately from profiles
- Server-evaluated permissions
Security
Controls enforced by the database, not by the interface.
Steritrack states only what is implemented. Access rules, tenant isolation and audit immutability are enforced server-side, so hiding a button is never the security mechanism.
Row-level tenant isolation
Every operational table is scoped to an organization by database policy.
- Cross-organization reads denied
- Cross-organization writes denied
Immutable audit
Audit and traceability events are append-only, including for privileged roles.
- No update or delete path
- Explainable state transitions
Human release control
No automatic release. A qualified human validates before a set returns to use.
- Hard stops on missing evidence
- Recorded human decisions
No patient data
The data model has no patient identity fields; cases use opaque references only.
- No name, MRN or date of birth
- Opaque case references
Read-only public review
The public review environment is isolated and has zero write capability.
- Demo organization only
- Mutations denied at database level
Steritrack does not claim ISO 27001, SOC 2 or HDS certification, and does not currently advertise MFA or SSO. Only the controls listed above are implemented.