Part I Using Transparent Data Encryption

Part I describes how to use Transparent Data Encryption.

• Introduction to Transparent Data Encryption
  Transparent Data Encryption enables you to encrypt sensitive data, such as credit card numbers or Social Security numbers.
• Configuring Transparent Data Encryption
  You can configure software or external keystores, for use on both individual table columns or entire tablespaces.
• Managing the Keystore and the Master Encryption Key
  You 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 Mode
  United 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 Mode
  In 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 Encryption
  When you use Transparent Data Encryption, you should consider factors such as security, performance, and storage overheads.
• Using Transparent Data Encryption with Other Oracle Features
  You 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 Keystores
  If you do not want to use the WALLET_ROOT parameter to configure keystores, then you can use the sqlnet.ora file.
• Frequently Asked Questions About Transparent Data Encryption
  Users frequently have questions about transparency and performance issues with Transparent Data Encryption.