MySQL 8.0 FAQ: InnoDB Data-at-Rest Encryption No, it is not possible to use other encryption algorithms. The provided encryption algorithm is broadly accepted. InnoDB  data-at-rest encryption supports all indexes transparently. InnoDB  data-at-rest encryption supports all supported data types. There is no data length limitation. Data encrypted by the  InnoDB  data-at-rest feature is decrypted when it is read from the tablespace file. Thus, if the data is on the network, it is in cleartext form. However, data on the network can be encrypted using MySQL network encryption, which encrypts data traveling to and from a database using SSL/TLS. With  InnoDB  data-at-rest encryption, in-memory data is decrypted, which provides complete transparency. Compliance with the PCI-DSS standard requires that credit card numbers (Primary Account Number, or ’PAN’) be stored in encrypted form. Breach Notification Laws (for example, CA SB 1386, CA AB 1950, and similar laws in 43+ more US states) require encryption of first name, last name, driver license number, and other PII data. In early 2008, CA AB 1298 added medical and health insurance information to PII data. Additionally, industry specific privacy and security standards may require encryption of certain assets. For example, assets such as pharmaceutical research results, oil field exploration results, financial contracts, or personal data of law enforcement informants may require encryption. In the health care industry, the privacy of patient data, health records and X-ray images is of the highest importance. There are symmetric and asymmetric encryption APIs in MySQL that can be used to manually encrypt data within the database. However, the application must manage encryption keys and perform required encryption and decryption operations by calling API functions.  InnoDB  data-at-rest encryption requires no application changes, is transparent to end users, and provides automated, built-in key management. Customers using  InnoDB  data-at-rest encryption receive the full benefit of compression because compression is applied before data blocks are encrypted. Yes. It is supported for encrypted file-per-table tablespaces. For more information, see Exporting Encrypted Tablespaces. Yes. Because these utilities create logical backups, the data dumped from encrypted tables is not encrypted. 5278 A.17.5. Can indexed columns be encrypted? A.17.6. What data types and data lengths does  InnoDB  data-at-rest encryption support? A.17.7. Does data remain encrypted on the network? A.17.8. Does database memory contain cleartext or encrypted data? A.17.9. How do I know which data to encrypt? A.17.10. How is  InnoDB  data-at-rest encryption different from encryption functions MySQL already provides? A.17.11. Does the transportable tablespaces feature work with  InnoDB  data-at-rest encryption? A.17.12. Does compression work with  InnoDB  data-at-rest encryption? A.17.13. Can I use  mysqlpump  or  mysqldump  with encrypted tables?