Crypto-shredding
Deleting data by destroying the key that encrypts it, so every copy, including backups, becomes unreadable.
Crypto-shredding encrypts each subject's data (a user, a tenant) under its own key. To erase, you delete the key; the ciphertext can stay in immutable backups, logs and replicas because nobody can decrypt it any more. It is the practical answer to GDPR Article 17 erasure in systems where finding and rewriting every copy is impossible.
It only works if the key really is the single point of access. It fails when plaintext leaked into search indexes, analytics tables, caches or ML features; when the key was itself backed up somewhere without a deletion path; or when derived data (aggregates, embeddings) still identifies the person.
Design questions to expect: key granularity (per user or per tenant), how key deletion is made irreversible yet protected from accidental or malicious triggering (delay windows, dual control), and how you prove deletion to an auditor.
Learn it properly
Also used in
- Cryptography you actually needSecEng · Foundations of Security EngineeringFree
- Queues and streamsHLD · Security design building blocksFree
- Caches and storage choicesHLD · Security design building blocksFree
- Multi-tenant isolationSecEng · Advanced: Security Architecture at ScalePro
- Design a SIEM pipelineHLD · Design problems: Telemetry & detectionPro
- Design a key management serviceHLD · Design problems: Infrastructure & dataPro
- Design a CSPM platformHLD · Design problems: cloud & runtime securityPro
- Design an envelope encryption libraryLLD · Problems: policy and crypto enginesPro