TDE BYOK and Geo-Replication in Azure SQL DB

Recently a customer asked me for help with setting up a test of an Azure SQL Database in the single database tier with Geo-Replication to work with Transparent Data Encryption (TDE) with a customer-managed key, also known as Bring Your Own Key (BYOK). It is very simple to do it when you use service-managed keys, […]

Configure Extensible Key Management Using Azure Key Vault - Level 3 of the Stairway to TDE

In this third level of the Stairway, we examine how to store your encryption certificate in the Azure Key Vault.

Encryption Gets Broken All the Time

There are contests to break encryption algorithms taking place all the time. Another one was completed recently.

Mongodb Encryption

MongoDB adds encryption to protect data from the DBA.

Protecting the DMK

Encryption Libraries

There is an encryption library that Microsoft has released as open source.

Secure Enclave Concerns

A new security flaw in Intel SGX is found by researchers. This may or may not be a problem, but you should be aware.

Changing Algorithms

SQL Server Transparent Data Encryption vs. NetLib Encryptionizer

Between the legislation over the years (HIPAA, GLBA, GDPR, CCPA, etc.) and data breaches from large organizations that seem to pop-up in the news on a monthly basis, SQL Server database encryption is critical for our industry. SQL Server ships with a few options for a native encryption implementation (Column Level Encryption, Transparent Data Encryption, Data Masking, Always Encrypted), that all provide value in particular situations, but none of the options all seem to address all of the needs. What is the best way to encrypt our SQL Server data?

Moving Encrypted Data to Azure SQL Database

Learn how you can move encrypted data from on premises SQL Server to Azure SQL Database.