No cache version.
Caching disabled. Default setting for this page:enabled (code DEF204)
If the display is too slow, you can disable the user mode to view the cached version.
Rechercher dans le manuel MySQL
A.16 MySQL 8.0 FAQ: InnoDB Data-at-Rest Encryption
- A.16.1. Is data decrypted for users who are authorized to see it?
- A.16.2. What is the overhead associated with InnoDB data-at-rest encryption?
- A.16.3. What are the encryption algorithms used with InnoDB data-at-rest encryption?
- A.16.4. Is it possible to use 3rd party encryption algorithms in place of the one provided by the InnoDB data-at-rest encryption feature?
- A.16.5. Can indexed columns be encrypted?
- A.16.6. What data types and data lengths does InnoDB data-at-rest encryption support?
- A.16.7. Does data remain encrypted on the network?
- A.16.8. Does database memory contain cleartext or encrypted data?
- A.16.9. How do I know which data to encrypt?
- A.16.10. How is InnoDB data-at-rest encryption different from encryption functions MySQL already provides?
- A.16.11. Does the transportable tablespaces feature work with InnoDB data-at-rest encryption?
- A.16.12. Does compression work with InnoDB data-at-rest encryption?
- A.16.13. Can I use mysqlpump or mysqldump with encrypted tables?
- A.16.14. How do I change (rotate, re-key) the master encryption key?
- A.16.15. How do I migrate data from a cleartext InnoDB tablespace to an encrypted InnoDB tablespace?
A.16.1. | Is data decrypted for users who are authorized to see it? |
Yes. | |
A.16.2. |
What is the overhead associated with |
There is no additional storage overhead. According to internal benchmarks, performance overhead amounts to a single digit percentage difference. | |
A.16.3. |
What are the encryption algorithms used with
|
| |
A.16.4. |
Is it possible to use 3rd party encryption algorithms in place
of the one provided by the |
No, it is not possible to use other encryption algorithms. The provided encryption algorithm is broadly accepted. | |
A.16.5. | Can indexed columns be encrypted? |
| |
A.16.6. |
What data types and data lengths does |
| |
A.16.7. | Does data remain encrypted on the network? |
Data encrypted by the | |
A.16.8. | Does database memory contain cleartext or encrypted data? |
With | |
A.16.9. | How do I know which data to encrypt? |
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. | |
A.16.10. |
How is |
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. | |
A.16.11. |
Does the transportable tablespaces feature work with
|
Yes. It is supported for encrypted file-per-table tablespaces. For more information, see Exporting Encrypted Tablespaces. | |
A.16.12. |
Does compression work with |
Customers using | |
A.16.13. |
Can I use mysqlpump or
|
Yes. Because these utilities create logical backups, the data dumped from encrypted tables is not encrypted. | |
A.16.14. | How do I change (rotate, re-key) the master encryption key? |
| |
A.16.15. |
How do I migrate data from a cleartext |
Transferring data from one tablespace to another is not
required. To encrypt data in an |
Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-faqs-tablespace-encryption.html
The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.
References
These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.