Version: 2.1
Published: April 28, 2026
Audience: Security Professionals, Healthcare IT Managers, Technical Stakeholders
1. Executive Summary
REMEDIO is a pharmaceutical inventory and family health management app built with privacy-first and security-by-design principles.
This whitepaper summarizes the technical foundations of REMEDIO’s multi-layered security model, cryptography, and compliance posture.
Security Highlights
- ✅ Zero-Knowledge End-to-End Encryption (AES-256-GCM)
- ✅ scrypt Password Hashing (N=2¹⁹ = 524,288 iterations)
- ✅ ECDH P-256 for family sharing (zero-knowledge)
- ✅ TLS 1.3 + Certificate Pinning
- ✅ Defense-in-Depth Architecture
- ✅ GDPR & CCPA Compliant
- ✅ Native iOS/Android secure storage
2. Security Architecture Overview
2.1 Defense-in-Depth Model
Each system layer provides independent, redundant protection:
| Layer | Description |
|---|---|
| L7 | User Education – password hygiene, phishing awareness |
| L6 | Application Security – validation, anti-XSS, anti-CSRF |
| L5 | End-to-End Encryption – AES-256-GCM client-side |
| L4 | Authentication – scrypt hashing, session control |
| L3 | Network Security – TLS 1.3, certificate pinning |
| L2 | Database Security – access control, RLS (planned) |
| L1 | Infrastructure – OVH firewall, Fail2Ban intrusion prevention |
Principle: Compromise of one layer never exposes the others.
2.2 Trust Model
- Zero-Trust Approach – No implicit trust between components
- Zero-Knowledge Encryption – Servers cannot decrypt user health data
- Client-Side Custody – User holds the encryption keys
- Strict Validation – All inputs sanitized and verified
Trust Boundaries
- Client → Encryption/decryption, key management
- Server → Authentication, ciphertext storage, business logic
- Third Parties → Firebase (notifications), Neon (database), OVHcloud (hosting)
2.3 Attack Surface Minimization
REMEDIO reduces its exposure to attacks through strict minimization of externally accessible services and continuous hardening of all infrastructure layers.
Core principles include:
- Only essential services are reachable from the public internet
- All external communication is encrypted end-to-end
- Internal system components remain isolated behind multiple layers of protection
- Administrative access requires strong authentication and is tightly monitored
- Automated intrusion detection and blocking systems are always active
No legacy, insecure, or plaintext protocols are permitted anywhere in the environment.
3. Cryptographic Foundations
| Function | Algorithm | Standard | Key Size |
|---|---|---|---|
| Symmetric Encryption | AES-256-GCM | FIPS 197 / NIST SP 800-38D | 256-bit |
| Key Derivation | PBKDF2-HMAC-SHA-256 | NIST SP 800-132 | 256-bit |
| Password Hashing | scrypt | RFC 7914 | 512-bit |
| Asymmetric Exchange | ECDH P-256 | FIPS 186-4 | 256-bit |
| Integrity Check | HMAC-SHA-256 | FIPS 198-1 | 256-bit |
| RNG | Web Crypto API (CSPRNG) | NIST SP 800-90A | — |
All primitives are FIPS-validated and OWASP 2024–recommended.
3.1 End-to-End Encryption (E2E)
- Client-side encryption using AES-256-GCM
- Master key generated locally; never leaves device
- Wrapped key stored server-side, encrypted with password-derived key
- Recovery Kit (24 words) allows recovery if password is lost
- Family Sharing via ECDH P-256 key exchange — server never sees private keys
Outcome: Even with full server access, health data remains unreadable.
3.2 Password and Key Management
- Password hashing: scrypt (N=2¹⁹, r=8, p=1)
- Password-derived key: PBKDF2 (600k iterations)
- Recovery mechanism: 24-word offline kit (user-held)
- Keys: Never transmitted in plaintext; regenerated per device session
4. Authentication & Authorization
- Primary Authentication: Email + password
- Session Control: 365-day inactivity expiry
- Secure Cookies:
httpOnly,Secure,SameSite=Strict - RBAC Model:
- Master → Full access
- Relative → Shared read/write limited scope
- Planned 2027 Enhancements:
- Two-Factor Authentication (TOTP)
- Biometric unlock (Face ID / Touch ID)
5. Database & Data Security
- Encrypted Tables: Health Tracker, Medical Diary, Family Vault
- Plaintext (non-sensitive): Product metadata, profile info
- Backups: 30-day retention, AES-256 full-disk encryption
- Inactive Accounts: Deleted after 730 days
- Immediate Wipe: User-initiated deletion fully removes data
Result: Even backup data remains unreadable (ciphertext-only).
6. Network & Infrastructure Security
- TLS 1.3 enforced across all APIs
- HSTS + OCSP stapling enabled
- Certificate Pinning on both mobile clients
- Firewall: OVHcloud + Fail2Ban (SSH & API rate limiting)
- Server OS: Hardened VPS (EU region only)
- Monitoring: Automated log anomaly detection
All network traffic is encrypted in transit.
7. Mobile App Security
| Platform | Security Measures |
|---|---|
| iOS | Certificate pinning, Secure Enclave (Keychain) |
| Android | Certificate pinning, Keystore-backed AES encryption |
| Both | HTTPS-only transport, no cleartext endpoints |
| Code Security | Obfuscation & signed release builds |
No sensitive data ever stored outside encrypted device storage.
8. Threat Modeling (Public Summary)
| Threat | Mitigation |
|---|---|
| Brute-force login | scrypt, Fail2Ban, password complexity |
| SQL Injection | ORM + validation |
| XSS / CSRF | React auto-escaping, strict cookies |
| MITM | TLS 1.3 + certificate pinning |
| Data Breach | E2E encryption (unreadable ciphertext) |
| Session Hijacking | Secure cookies, short expiry |
| DDoS | Rate limiting + IP blocking |
9. Privacy & Compliance Summary
Frameworks Supported
- GDPR (EU)
- CCPA (California)
- COPPA (Children’s data limits)
- HIPAA-equivalent controls (though not a covered entity)
Data Subject Rights
- Export (JSON/PDF format)
- Deletion (irreversible)
- Correction & Portability (in-app)
- Opt-out (push, imports, family sharing)
Legal Bases (GDPR)
- Contractual necessity (Art. 6)
- Explicit consent for encrypted health data (Art. 9)
10. Incident Response & Breach Policy
Timeline
- Detection → within 24h
- Containment → within 48h
- Notification → within 72h (GDPR Arts. 33–34)
Process
- Immediate investigation
- Notify users & authorities if high risk
- Patch, restore, and publish post-mortem
User Safety:
Encrypted health data remains secure even in breach scenarios.
11. Security Governance
| Area | Measure |
|---|---|
| Audits | Annual third-party penetration test (next: Q1 2027) |
| Training | OWASP Top 10, GDPR privacy principles |
| Logging | Access + admin actions monitored |
| Future | ISO 27001 certification target (2027) |
Responsible Disclosure
Email: reportfraud@remedio-app.com (response within 48h, fix window: 90 days)
12. Conclusion
REMEDIO delivers enterprise-grade security in a consumer health context:
- AES-256-GCM encryption and scrypt password protection
- Zero-knowledge design (no server-side decryption)
- Multi-layer defense-in-depth
- Full GDPR/CCPA transparency
- Certified EU infrastructure (OVH, Neon, Firebase SCC)
Your health data stays private, encrypted, and under your control.
End of Security Whitepaper (Public Snapshot)
Version 2.1 – April 28, 2026
Next Review: October 28, 2026 (semi-annual)