Release v15.38.4
Summary
Enables GDPR right-to-erasure (crypto-shredding) from a Chronicle client application. Deleting a person's PII encryption key makes every PII value encrypted under that subject permanently unreadable — everywhere it appears. Previously the client IPIIManager only threw NotImplementedException, so there was no way to trigger erasure from application or ops code.
Added
- Chronicle clients can delete a subject's PII encryption key to satisfy GDPR right-to-erasure (crypto-shredding), via
IPIIManager.DeleteEncryptionKeyForandIEventStore.PII.IPIIManagercan also be injected directly.
Changed
- Reading a PII value whose encryption key has been deleted now returns an empty value instead of throwing, so read models and queries for an erased subject keep working.
Removed
- Removed the non-functional
CreateAndRegisterKeyForfromIPIIManager; it only ever threwNotImplementedException, and encryption keys are already registered automatically on first use.