Storing email addresses, dates of birth or national identity numbers in plain text is a serious risk the day your database leaks. Application-side encryption makes that data unreadable to the database itself. It also makes WHERE email = :value impossible, which is usually where the project quietly stops.

This talk shows how to keep both. Client-side field encryption with Doctrine and a key management system: which algorithms to choose, how deterministic encryption enables equality lookups, how keys are stored, rotated and revoked, and what you give up in exchange. We'll also look at Symfony's new KMS component and where it fits.

You'll leave knowing how to turn your database into a safe you can still search.