Information Security Policy

Alphiniti's comprehensive encryption architecture protecting patient data across all services

Encryption Architecture Diagram
🔑 ALPHINITI KEY (Central Key Management)
1. Generate Encryption Key (AES-256-GCM)
2. Encrypt key material with master key
3. Store in EncryptionKey entity
↓ Sync Key to all services via POST /api/sync-key
CONTINUUM
✓ Receive Key
✓ Store Locally
✓ Encrypt/Decrypt Data
HEALTH FLOW
✓ Receive Key
✓ Store Locally
✓ Encrypt/Decrypt Data
PATH
✓ Receive Key
✓ Store Locally
✓ Encrypt/Decrypt Data
Encryption Process

1. Key Generation (Alphiniti Key)

User Request
→
Generate Key
→
Encrypt with Master Key
→
Store
→
Sync to Services

2. Data Encryption (Any Service)

Plain Data
→
Get Active Key
→
Decrypt Key Material
→
Encrypt Data
→
Store Encrypted

3. Data Decryption (Any Service)

Encrypted Data
→
Get Key by ID
→
Decrypt Key Material
→
Decrypt Data
→
Return Plain

4. Inter-Service Data Transfer

Service A: Get Encrypted Data
→
Send to Service B (Still Encrypted)
→
Service B: Store/Decrypt
Service Endpoints

Alphiniti Key (Central)

POST /api/generate-key - Generate new encryption key
POST /api/sync-key - Sync key to all services
POST /api/rotate-key - Rotate existing key

Distributed Services (Continuum, Health Flow, Path)

POST /api/sync-key - Receive key from Alphiniti Key
Local encryption/decryption using synced keys