Encryption key (BYOK)
This screen lets your company protect its data keys with a key you control in your Azure Key Vault, on top of the platform post-quantum key. It is off by default. Only company administrators see it.
1. Who holds the key
By default goPrevina holds the key. With “My key in Azure Key Vault”, each data key is split in two parts: one protected by the platform ML-KEM key and one by your vault key. Both are needed to read your data. Your key uses RSA-OAEP-256, which is not post-quantum; the platform part keeps the post-quantum protection.
2. Setting up your vault
Create an RSA key in your Azure Key Vault and give an application (or the platform managed identity) permission to wrap and unwrap keys with it. Then enter the vault address, the key name and, if you use an application, the directory ID, application ID and client secret. The secret is stored encrypted and is never shown again.
3. Test and save
“Test the key” protects and recovers a random value to prove the settings work, without changing anything. “Save” tests the key again, protects every data key of your company with it and turns the mode on. “Seconds a key is kept in memory” sets how long goPrevina reuses a key before asking your vault again (five minutes by default).
4. Disabling, rotating and recovering
If you disable or delete the key in your vault, your company data cannot be read: screens show an error and the state becomes “Your key is not available”, with an entry in the activity log. Data already in use can stay readable for the seconds set above. When you enable the key again, everything works again without further steps. After you create a new key version in your vault, press “Protect again with the latest key version”. Going back to the platform key needs your key to be available. Platform administrators can see the state and the activity log.