Transparent data encryption: Difference between revisions

Content deleted Content added
Citation bot (talk | contribs)
Add: website. | Use this bot. Report bugs. | Suggested by Whoop whoop pull up | #UCB_webform 159/489
Broken reference updated. Author repulished "The Anatomy and (In)Security of Microsoft SQL Server Transparent Data Encryption (TDE), or How to Break TDE" to Medium. Original reference directs to a ___domain squatter.
Line 22:
During database backups, [[Data compression|compression]] occurs after encryption. Due to the fact that strongly encrypted data cannot be significantly compressed, backups of TDE encrypted databases require additional resources.
 
To enable automatic booting, SQL Server stores the lowest level encryption keys in persistent storage (using the [[Data Protection API|DPAPI]] store). This presents a potential security issue because the stored keys can be directly recovered from a live system or from backups and used to decrypt the databases.<ref>Simon McAuliffe, [httphttps://simonmcauliffemedium.com/technology@s.mcauliffe_17464/the-anatomy-and-in-security-of-microsoft-sql-server-transparent-data-encryption-tde/-or-how-to-d164eb08564 "The Anatomy and (In)Security of Microsoft SQL Server Transparent Data Encryption (TDE)"], 19-Mar-2016</ref>
 
== See also ==