Security Guide

API Secrets & Credentials

Securely manage and inject sensitive credentials into your carrier integrations (Sinch, RingCentral) and webhook endpoints without exposing them in plain text. For authenticating your requests to Intellectua, see API Keys.

AES-256 GCM Storage

Secrets and tokens are encrypted at rest with random 12-byte IVs and 16-byte auth tags.

Write-Only Parameters

Once saved, secret values can never be retrieved or viewed again in plaintext.

Dynamic Injection

Secrets are decrypted in-memory only at the millisecond of carrier transmission.

1Configuring Carrier Secrets

Secrets are managed in the Integrations section of your Intellectua Dashboard.

  • Click Settings in the sidebar.
  • Navigate to the Integrations tab.
  • Select your carrier (Sinch or RingCentral).
  • Paste your API Secret / JWT Assertion Key.
  • Click Test & Save Connection.

2Why use this approach?

The Vulnerability

"I will paste raw carrier keys directly into client configurations or plaintext environment files."

DANGEROUS

Storing raw credentials in plaintext means anyone with database access can compromise carrier transmission lines and intercept clinical faxes.

The Intellectua Solution

"I store credentials in the encrypted vault and rely on AES-256 GCM in-memory decryption."

SECURE & HIPAA COMPLIANT

Encrypted ciphertext is stored in the database. The secret is decrypted in-memory only during carrier API requests and immediately wiped from memory.