Files
HealthLog/prisma/migrations/0411_encrypt_insights_cached_text/migration.sql
T
Marc-André Bombeck 00dfc5a0c0 feat(insights): seal the cached AI insights payload at rest
users.insights_cached_text held the model's briefing, readings and
recommendations about the account in the clear. Migration 0411 adds
insights_cached_text_encrypted (AES-256-GCM, binary layout, purpose-bound
label) and a partial discovery index; the free-text encryption backfill
seals the existing rows one at a time, fail-closed, carrying updatedAt and
guarded on the value it read. Every reader, writer and clear goes through
cached-text-cipher.ts, and a guard keeps the column names there. The
column joins the encrypted-column registry and the key-rotation script,
stays out of backups as operational, and is reset by the data wipe.
2026-10-20 07:30:00 +02:00

27 lines
1.4 KiB
SQL

-- The cached AI insights payload moves to AES-256-GCM at rest.
--
-- `users.insights_cached_text` held the model's last full reading of the
-- account in the clear: the daily briefing, the per-domain status text and the
-- recommendations. It was the last readable column of that kind on the user
-- row. From this release every write goes to `insights_cached_text_encrypted`
-- (binary layout, purpose-bound label) and leaves the readable column NULL.
--
-- SQL cannot encrypt, so this migration only adds the ciphertext column and
-- the discovery index. The boot-time `free-text-encryption-backfill` job seals
-- the existing rows one at a time and nulls the readable value in the same
-- transaction; it is fail-closed, so a missing or malformed key leaves the row
-- untouched and the job retries. Readers fall back to the readable column until
-- the backfill has reached a row. The readable column is dropped in a later
-- release, once the backfill reports nothing left on every instance.
--
-- Additive only: no table rewrite, no data change.
ALTER TABLE "users" ADD COLUMN "insights_cached_text_encrypted" BYTEA;
-- Partial index on exactly the backfill's discovery predicate, so the boot
-- scan is index-only and shrinks to nothing as the backfill converges (the
-- 0357 precedent).
CREATE INDEX IF NOT EXISTS "users_insights_cached_text_backfill_idx"
ON "users" ("id")
WHERE "insights_cached_text" IS NOT NULL;