Greetings,
There are two questions I have to address regularly:
1. Why can't I just turn on database encryption and call it a day?
2. Our engineers can call "encrypt" just fine, why do we need you?
The good news is that I hear the first question much less often these days as Application-layer Encryption gains mindshare among security teams. If you're getting this email, you probably already understand why it's important and why infrastructure-layer encryption like transparent database encryption is useless at protecting data in the cloud.
The second question doesn't come up as often. Generally if we're talking to someone, they've already realized that it isn't as easy as just calling "encrypt" on some data. Crypto-systems are complex and difficult to build and get right, which is something we've spent years perfecting. Our new blog goes much deeper on what it takes to build an ALE system and the many potential pitfalls. It's geared towards engineers and walks through hypothetical design decisions.
And speaking of issues, we also put out a blog on why you shouldn't use the native encryption functions in MySQL. Really. Don't.
Lastly, the talk we gave at Defcon in August about Cloaked AI is now up on YouTube. It's a technical one. We had tons of people come up to talk to us afterwards and are flattered by the great response. AI security is really critical today as companies adopt GenAI at record rates.
I truly hope this is useful for you. As always, I'm happy to answer any questions.
