Encryption in transit and at rest
Connections are encrypted in transit. Documents are stored for encryption at rest in private object storage, not in a public bucket.
Security
Security and controlled access
IbrahimOS is designed with security and controlled access as core product requirements. Compliance requirements vary by jurisdiction and deployment context. Organizations should evaluate IbrahimOS against their applicable healthcare, privacy, and data-protection requirements before production deployment.
Role-based access
Workspace roles are Administrator, Clinician, Reviewer, and Staff. A signup cannot grant access outside the organization it creates.
Organization isolation
Cases, documents, and knowledge stay inside the organization that owns them. One workspace cannot read another’s records.
Least privilege and audit logging
Server-side jobs use separate credentials from the browser. Access and review actions are written as audit events without copying record contents into logs.
Controlled AI context
Models receive the authorized case and the organization’s approved material. They do not become a medical authority, and their output stays in review until a professional acts on it.
Retention and monitoring
Retention is configurable per deployment. Processing failures and access are monitored. Patient names, record text, and secrets are not written to application logs.