Integration overview

integrating oracle database 12c transparent data encryption (tde) with the {{vectera}} requires the {{futurex}} pkcs #11 ( fxpkcs11 ) library after configuring it, you can store the master encryption key (mek) used for tde within the confines of a fips 140 2 level 3 validated hsm (such as the {{vectera}} ), adding a layer of protection for data at rest the master encryption key encrypts the oracle table keys, which encrypt or decrypt columns or tablespaces locally in the database each table has its own table key from the client application perspective, the encryption and decryption process is transparent, so you don't need to change the existing application we recommend that the connection between the {{futurex}} pkcs #11 library and the {{vectera}} be a mutually authenticated tls connection, but we aslo support server side authentication the instructions for configuring the {{futurex}} pkcs #11 library with oracle database running in a docker container cover mutual authentication using only tls certificates this guide provides the required information to configure {{futurex}} pkcs #11 with oracle database so that you can generate the tde master encryption key and store it on the {{vectera}} for encrypting the oracle table keys