Advanced Security Guide Using Transparent Data Encryption Part I Using Transparent Data Encryption Part I describes how to use Transparent Data Encryption. Introduction to Transparent Data EncryptionTransparent Data Encryption enables you to encrypt sensitive data, such as credit card numbers or Social Security numbers. Configuring Transparent Data EncryptionYou can configure software or external keystores, for use on both individual table columns or entire tablespaces. Managing the Keystore and the Master Encryption KeyYou can modify settings for the keystore and TDE master encryption key, and store Oracle Database and store Oracle GoldenGate secrets in a keystore. Managing Keystores and TDE Master Encryption Keys in United ModeUnited mode enables you to create a common keystore for the CDB and the PDBs for which the keystore is in united mode. Managing Keystores and TDE Master Encryption Keys in Isolated ModeIn an Oracle Cloud database (but not an on-premises database), isolated mode enables you to create a keystore for each pluggable database (PDB). General Considerations of Using Transparent Data EncryptionWhen you use Transparent Data Encryption, you should consider factors such as security, performance, and storage overheads. Using Transparent Data Encryption with Other Oracle FeaturesYou can use Oracle Data Encryption with other Oracle features, such as Oracle Data Guard or Oracle Real Application Clusters. Using sqlnet.ora to Configure Transparent Data Encryption KeystoresIf you do not want to use the WALLET_ROOT and TDE_CONFIGURATION parameters to configure the keystore location, then you can use the sqlnet.ora file. Frequently Asked Questions About Transparent Data EncryptionUsers frequently have questions about transparency and performance issues with Transparent Data Encryption.