DuoKey EKM for SQL
Extensible Key Management product sheet. 4 pages.
How to keep the master key for SQL Server Transparent Data Encryption outside the database server. The sheet shows the key hierarchy from master key to database encryption key, cloud and on-premises deployment, and examples for finance, healthcare, and retail. Get it if a stolen server image or backup today would carry both your data and the key that opens it.
Get the download
Tell us where to send the link. A business email is required.
Transparent Data Encryption is only as strong as where the master key lives. If it sits on the same server as the data, anyone with a copy of that server or its backups has both the lock and the key.
DuoKey's Extensible Key Management module moves the master key out of SQL Server and splits it into parts stored in different locations. A stolen backup on its own is useless.
The sheet covers the full key lifecycle, from creation through rotation and revocation to retirement, in the cloud and on premises, with examples for finance, healthcare, and retail. Download it before your next PCI-DSS or HIPAA review.
FAQ
Who is this for?
Database administrators and security teams who use, or plan to use, Transparent Data Encryption on SQL Server.
Why move the master key?
If the master key is on the same server as the data, a copy of that server contains both. Keeping it in DuoKey separates them.
Does it change SQL Server configuration much?
Integration needs minimal configuration changes on Microsoft SQL Server and other SQL-based databases.
Which regulations does it reference?
PCI-DSS and GDPR for finance, HIPAA for healthcare.