Security

Security is foundational to a healthcare platform. This page summarises the controls in place; the deeper internal documentation, threat model, and incident-response runbook are available to enterprise customers under NDA.

Infrastructure

• Application: Vercel (web app) and Render (API), served over HTTPS only.
• Database: Neon managed Postgres with point-in-time recovery (7-day window).
• File storage: AWS S3 with default encryption + bucket-level deny on unencrypted uploads.

Authentication

• JWT access + refresh tokens; refresh tokens stored as bcrypt hashes.
• MFA (TOTP) optional for any user, recommended for clinicians + administrators.
• Failed-login lockout (5 attempts → 15 minute lockout); events audited with IP + user agent.
• Password reset via single-use, time-limited tokens (1-hour expiry).

Data protection

• TLS 1.2+ in transit; AES-256 at rest; AES-256-GCM field-level encryption on highly sensitive PHI columns.
• Audit log is append-only at the database layer via a Postgres trigger — even a compromised service role cannot tamper with the trail.

Operational

• Required CI gate (typecheck + lint + tests + build) before any merge to main.
• Idempotent boot-time env validation refuses to start with weak or placeholder secrets in production.
• Per-tenant pagination and rate-limit caps on every list endpoint to limit blast radius.
• Quarterly PITR drills against the staging branch with documented RTO/RPO targets.

Responsible disclosure

Found something? Report to security@aarogentix.com. We acknowledge within 24 hours, triage within 5 business days, and credit researchers in our hall of fame on resolution.