[Decision] Define encryption threat model, deployment profiles, and disable semantics #1

Open
opened 2026-07-30 17:34:18 +02:00 by zemion · 0 comments
Owner

Define the boundary before implementing cryptography. The module may provide key vaults and E2EE capabilities, but business ownership, access control, and key custody must remain distinct.

Acceptance criteria

  • Threat actors, protected assets, metadata leakage, server trust, client trust, and backup/recovery assumptions are documented.
  • Deployment profiles distinguish server-side envelope encryption, tenant-held keys, and true end-to-end encryption.
  • Disable/uninstall behavior is explicit: encrypted content must be migrated/decrypted by an authorized workflow or remain unavailable; disabling never silently destroys keys or data.
  • Recovery, legal hold, export, rotation, revocation, and ownership-transfer consequences are decided per profile.
  • Approved algorithms/libraries and cryptographic-agility/versioning rules are recorded.
  • No implementation claims E2EE before the selected profile satisfies the threat model.
Define the boundary before implementing cryptography. The module may provide key vaults and E2EE capabilities, but business ownership, access control, and key custody must remain distinct. ## Acceptance criteria - Threat actors, protected assets, metadata leakage, server trust, client trust, and backup/recovery assumptions are documented. - Deployment profiles distinguish server-side envelope encryption, tenant-held keys, and true end-to-end encryption. - Disable/uninstall behavior is explicit: encrypted content must be migrated/decrypted by an authorized workflow or remain unavailable; disabling never silently destroys keys or data. - Recovery, legal hold, export, rotation, revocation, and ownership-transfer consequences are decided per profile. - Approved algorithms/libraries and cryptographic-agility/versioning rules are recorded. - No implementation claims E2EE before the selected profile satisfies the threat model.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-encryption#1
No description provided.