Microsoft SQL Server TDE

this document provides information about configuring {{futurex}} hsms with microsoft sql server transparent data encryption (tde) by using extensible key management (ekm) libraries for additional questions related to your hsm, see the relevant administrator’s guide about microsoft sql server microsoft sql server is a relational database management system (rdbms) used for large scale online transaction processing (oltp), data warehousing, and e commerce applications it is also a business intelligence platform for data integration, analysis, and reporting solutions about transparent data encryption (tde) from microsoft's documentation website transparent data encryption (tde) encrypts sql server data files this encryption is known as encrypting data at rest to help secure a database, you can take precautions like designing a secure system encrypting confidential assets building a firewall around the database servers but a malicious party who steals physical media like drives or backup tapes can restore or attach the database and browse its data one solution is to encrypt sensitive data in a database and use a certificate to protect the keys that encrypt the data this solution prevents anyone without the keys from using the data but you must plan this kind of protection in advance tde does real time i/o encryption and decryption of data and log files the encryption uses a database encryption key (dek) the database boot record stores the key for availability during recovery the dek is a symmetric key it's secured by a certificate that the server's master database stores or by an asymmetric key that an ekm module protects tde protects data at rest, which is the data and log files it lets you follow many laws, regulations, and guidelines established in various industries this ability lets software developers encrypt data by using aes and 3des encryption algorithms without changing existing applications encryption hierarchy and integration with the vectera plus through ekm, microsoft sql server can use our {{vectera}} hsm for key management and encryption acceleration in this configuration, you can encrypt data by using encryption keys that only the database user can access on the external ekm hsm module only the database level items (such as the database encryption key) are user configurable when you use tde on sql database guardian integration the {{guard}} introduces mission critical viability to core cryptographic infrastructure, including centralization of device management elimination of points of failure distribution of transaction loads group specific function blocking user defined grouping systems see the applicable guide in the {{futurex}} portal for configuring hsms with the {{guard}} , including pkcs #11 and cng configuration