4 of 18 controls in place
Socratic Labs builds software for medical practices. These are the security controls our policies promise, each checked against evidence from our code, our servers and our recurring reviews.
- Last access review
- Not yet recorded
- Last restore test
- Not yet recorded
- Checked
Access
Who can sign in, and how we keep that list short.
- In place
Allowlisted sign-in
Staff sign in through one identity provider, and each app admits only the people on its allowlist.
- Attention
Quarterly access review
Every account, key and allowlist is reviewed each quarter. Multi-factor sign-in is on wherever it is offered.
- Attention
Append-only audit log
Every app keeps an append-only record of who did what, reviewed each quarter.
Data protection
Encryption and browser protections on every connection.
- In place
Encryption in transit
Every connection to our apps is encrypted with current TLS.
- In place
Browser security headers
Our apps tell browsers to use HTTPS only and to load nothing from untrusted places.
- Attention
No secrets in code
Every code change is scanned for leaked secrets.
Change management
How code reaches production: reviewed, tested and scanned.
- Attention
Every change passes CI
Every change is tested and scanned before it reaches production.
- Attention
Main is protected
Nobody, including the owner, can push to production without a reviewed, passing pull request.
- Attention
Dependencies patched
Dependencies are audited on every change and patched as advisories land.
- Being set up
Repo baseline in sync
Every app runs the same reviewed CI and scanner setup.
Backups and availability
Nightly encrypted backups, tested restores, health checks.
- Being set up
Nightly encrypted backups
Every production database is backed up nightly, encrypted, and kept off the host.
- Attention
Quarterly restore test
Each quarter we restore every app from its backup and check it works.
- In place
Apps up and answering
Each app's health is checked around the clock.
Incident response
A written plan, a 24-hour notice, a yearly rehearsal.
- Attention
Incident response, rehearsed
Incidents are logged the same day and clients hear from us within 24 hours. The plan is rehearsed yearly.
Vendors
Every service we rely on, and what it may touch.
- Attention
Vendor register and BAAs
Every service we use is registered and reviewed, and none holds patient data without a signed BAA.
People and policy
Training, risk assessments and policy reviews.
- Attention
Security training
Everyone with access is trained on HIPAA and security every year.
- Attention
Yearly risk assessment
Each app's risks are assessed before it takes real data and every year after.
- Attention
Policies reviewed yearly
Our written policies are reviewed every year and kept for six years.
Policies
Reviewed every year. Confidential policies are shared with practices on request.
- SL-POL-001Operating Principlesv1.0, November 18, 2026Read
- SL-POL-002Information Security Policyv1.0, November 18, 2026Available on request
- SL-POL-003Access Controlv1.0, November 18, 2026Available on request
- SL-POL-004Change Managementv1.0, November 18, 2026Available on request
- SL-POL-005Backup and Recoveryv1.0, November 18, 2026Available on request
- SL-POL-006Incident Responsev1.0, November 18, 2026Available on request
- SL-POL-007Data Retention and Disposalv1.0, November 18, 2026Available on request
- SL-POL-008Vendor Managementv1.0, November 18, 2026Available on request
- SL-POL-009Risk Assessmentv1.0, November 18, 2026Available on request
- SL-POL-010Acceptable Usev1.0, November 18, 2026Available on request
- SL-POL-011Security Awarenessv1.0, November 18, 2026Available on request
Subprocessors
Services that can touch customer data.
- Oracle CloudApplication hosting
- SupabaseStaff sign-in
- CloudflareDNS and encrypted backup storage
- Google WorkspaceEmail and documents
Frameworks
Each control maps to requirements in:
- HIPAA Security Rule
- SOC 2 Trust Services Criteria
This is our own record, kept to these frameworks. It is not a certification or an audit report.