Preparing the sample workspace…
Security posture
Ekvidu is designed so identity, tenant data, provider execution and operator access remain separate, least-privileged surfaces with auditable transitions.
02 / Deliverables
Implemented OIDC state checks, opaque application sessions and protected route boundaries
Implemented organisation-scoped foundations for current brand and collection resources
Planned isolated workers, encrypted evidence storage and scoped support grants
Planned backup, restore, incident response and key-rotation proof before beta
03 / How it works
The current application uses provider-neutral account entry, server-managed opaque sessions and request-integrity protections. Existing protected resources are designed around organisation and resource ownership, while browser-facing auth failures remain bounded and avoid returning provider secrets.
Production beta requires isolated provider and arbitrary-URL workers, encrypted external evidence storage, tested deletion and backup expiry, independently verified restore and rollback, monitored cost kill switches, MFA and device-session journeys, and audited time-bounded support access.
Architecture and tests are evidence for specific controls, not proof of universal security. A formal security contact, disclosure process, subprocessor list and customer security documents remain pre-launch owner and legal gates.
04 / Limitations
05 / Next step