Skip to content

security(integrations): encrypt credential payloads - #29

Closed
darwin67 wants to merge 2 commits into
mainfrom
rfd-5-phase-1a-encryption
Closed

security(integrations): encrypt credential payloads#29
darwin67 wants to merge 2 commits into
mainfrom
rfd-5-phase-1a-encryption

Conversation

@darwin67

@darwin67 darwin67 commented Sep 3, 2026

Copy link
Copy Markdown
Member

Summary

  • encrypt versioned credential payloads with AES-256-GCM and a unique nonce per write
  • bind ciphertext to integration, user, provider, authentication type, and payload format through AEAD associated data
  • require a dedicated production key ring and block startup before readiness when configured or referenced keys are missing
  • filter provider secrets and credential-derived identifiers from Phoenix and LiveView parameter logs
  • document key distribution and rotation and update the release smoke environment

Verification

  • focused integration security suite: 20 passed
  • production-mode runtime key-ring configuration check passed
  • mix precommit: 343 passed, 5 live-provider tests excluded

Stack

Depends on #28.

Base automatically changed from rfd-5-phase-1a-schema to main September 3, 2026 23:17
@darwin67
darwin67 force-pushed the rfd-5-phase-1a-encryption branch from 537aebf to 55cc2a1 Compare September 3, 2026 23:19
@darwin67 darwin67 closed this Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant