Within SAP HANA Cloud Integration, certain data is encrypted to ensure privacy, keep it free from corruption, and maintain access control. Cryptographic keys are used to encrypt and decrypt this sensitive data.
Two cryptographic keys are generated, one each for the sandbox and production environments. Cryptographic keys need to be replaced regularly to minimize the risk of being compromised. The security officer manages the keys based on the organization's security guidelines and procedures.
At any given time, only one cryptographic key can be designated as active. Each cryptographic
key moves through a lifecycle illustrated in the following diagram: 
| Status | Definition |
|---|---|
| Active | The active key is used to encrypt current sensitive data. The key is also used to decrypt all sensitive data. When a new cryptographic key is created, the current active key moves to a deactivated state. An active key cannot be deleted from the system. |
| Deactivated | A deactivated key can no longer be used to encrypt data. It can however be used to decrypt all data encrypted when the key was active. You cannot reactivate a key once it has been deactivated. A deactivated key cannot be deleted directly from the system. Its status must first be changed to revoked before it can be deleted. |
| Revoked | When a cryptographic key is revoked, a process is launched in which all data encrypted with the key is decrypted and then re-encrypted with the current active cryptographic key. This process may take some time. Once a key is revoked it can safely be deleted from the system. The revocation mechanism ensures that encrypted data can always be decrypted. There is no way to reactivate a key once it has been revoked. |
| Deleted | The deleted key is no longer displayed and can be safely removed from the database or file system. |