Security
Security as architecture, not as a badge.
higeia is built on five control domains applied from the first commit. This document describes the principles, controls and technical commitments that sustain the platform's security posture.
1. Security principles
Defense in depth. No single control is sufficient. Each layer assumes the previous one may fail.
Least privilege. Every component, user and process receives only the permissions necessary for its function.
Secure by default. Secure configurations are the initial state, not an option.
Auditable transparency. Every security decision is documented, versioned and accessible to the client.
2. Isolation architecture
higeia operates in a multi-tenant architecture with logical isolation via database schema (schema-per-tenant). Each client organization has its own schema with no shared tables.
On Private and Regulated plans, isolation is physical: dedicated VPC, exclusive database instances and customer-managed encryption keys (BYO-KMS).
3. Encryption
Data at rest is encrypted with AES-256. Sensitive fields receive additional envelope encryption with keys rotated every 90 days. Data in transit uses TLS 1.3 on all external connections and mTLS internally.
4. Logging and audit
The audit log is append-only with chained hashing for tamper detection, retained for a minimum of five years. Every material decision is recorded with named user, source IP, timestamp, previous state and new state.
5. Sub-processors
| Sub-processor | Purpose | Location |
|---|---|---|
| AWS | Hosting and database infrastructure | sa-east-1 (São Paulo) |
| Anthropic | LLM provider (Claude, all plans) | USA |
| LLM provider (Gemini, all plans) | USA | |
| Airtable | Contact form lead persistence | USA |
| Resend | Transactional email | USA |
| Cloudflare | CDN, DNS and DDoS protection | Global (edge) |
Full list with contractual basis at/subprocessadores.
6. Regulatory compliance
higeia is designed to operate in compliance with LGPD (Law 13,709/2018), with particular attention to sensitive health data treatment under art. 11. Controls are aligned to ISO 27001, ISO 27701, ISO 27799, NIST CSF 2.0 and CIS Controls v8. For international operations, the product is designed for HIPAA and GDPR compliance.
Formal certifications (ISO 27001 at month 18, SOC 2 Type I in Phase 3, Type II at month 24) are on the roadmap. Healthcare accreditations (ONA, HIMSS) are supported by the Certifications & Frameworks module.
7. Security contact
To report vulnerabilities or security incidents: higeia@saude.dev. We respond within 24 business hours.
PGP public key will be published on this page and at/.well-known/security.txtafter generation. Use the email above for initial communication.
8. Incident history
No security incidents reported since platform inauguration.