Organization Level Secrets & Encryption
Learn how HIPAA-compliant secrets, carrier credentials, and integration keys are encrypted at rest using AES-256 GCM and dynamically injected.
Overview
Intellectua AI enforces banking-grade envelope encryption rules on all organization-level credentials, ensuring carrier tokens (Sinch, RingCentral) and custom gateway parameters remain secure under strict HIPAA regulations.
Security Framework
- AES-256 GCM: Credentials are encrypted using a global master key combined with unique organization salts.
- Write-Only Parameters: Saved secret values can never be retrieved or viewed in plaintext from the UI once stored.
- Dynamic Injection: Integration keys are injected into memory only at the moment of carrier API execution.
Encryption & Dynamic Injection Pipeline
All organization-level environment credentials undergo an isolated encryption/decryption sequence during execution:
1. UI Input Verification
An administrator inputs a credential (e.g., Sinch API Token, RingCentral Secret). The plaintext is transferred securely via TLS 1.3.
2. AES-256-GCM Encryption
The backend immediately encrypts the plaintext using AES-256-GCM with a random 12-byte Initialization Vector (IV) and a 16-byte authentication tag.
3. Write-Only DB Storage
The compiled string (iv:tag:ciphertext) is stored in the database. The plaintext is garbage-collected instantly.
4. Dynamic In-Memory Decryption
During carrier API requests, the backend decrypts the secret in-memory, signs the outbound REST payload, and purges it immediately afterwards.
