Page History

...

Cache encryption key rotation required in case of it compromising or at the end of crypto period (key validity period). in addition, such feature is required to provide support for encrypt and descrypt existing caches in the future.

Security requirement

Payment card industry data security standard (PCI DSS) requires that key-management procedures include a defined cryptoperiod for each key type in use and define a process for key changes at the end of the defined cryptoperiod(s). An expired key should not be used to encrypt new data, but it can be used for archived data, such keys should be strongly protected (section 3.5 - 3.6) [1].
The maximum recommended key lifetime is 2 years [2], and on average it is supposed to be changed every few months [3].

Key rotation in other systems

Out of the box, Oracle and MySQL do not provide an automatic procedure for rotating tablespace keys, master key rotation is supported [4][5], MS SQL Server provide rotation of database encryption key with background re-encryption of existing data [6]. Currently, TDE is being developed for PostgreSQL, but support for tablespace key rotation is not planned [7].

...