|
|
|
|
|
|
by zaroth
1404 days ago
|
|
|
Thank you for the quick reply! I’m not a Supabase customer so apologies if the questions don’t make sense in your context. But I think it would help to understand if Supabase is fully managing key backup and recovery internally, how exactly is that working? Ultimately the whole value of TDE at the database layer comes down to two things IMO which are flip sides of the same coin; 1) Being able to store your database backups in less trusted locations, 2) actually keeping the secret data secret, which amounts to keeping that encryption key secured at a much higher level than the database backup itself. In the end it’s just key vaults all the way down, isn’t it! |
|
|
Supabase persists and protects your key and we will provide API and CLI access to retrieve it securely. This is a pre-release so we haven't worked out all the use cases yet but those are the basics for MVP.
> 1) Being able to store your database backups in less trusted locations,
Yes. Using Transparent Column Encryption you control on a column by column basis how your data is stored encrypted so you have more fine grained control over your data.
> 2) actually keeping the secret data secret, which amounts to keeping that encryption key secured at a much higher level than the database backup itself.
Yep, we don't have all the answers there, keeping the root key out of SQL is a big one. Maybe requiring MFA to access the key even with the API, there are a lot of possibilities. Thanks for your feedback these are all going into my notes for an upcoming release.