Security and keys
Here you manage the post-quantum keys goPrevina encrypts and signs with: you see their status, decide when they rotate, check the backups and test that they could be restored. Only the platform administrator sees it.
1. Key status
At the top you see the active encryption and signing keys, the root key fingerprint and the last copy verified in every destination. The “Keys” table lists all of them with their status: “Active”, “Retiring”, “Retired” or “Destroyed”. A retired signing key keeps its public part to verify old signatures; its private part is deleted when it is retired. If the notice says the root key is missing, the keys are read from the configuration and cannot be managed here.
2. Rotate and rotation policy
“Rotate now” creates a new key (encryption, signing or both) and activates it. Anything encrypted with the previous one still opens and each company’s data keys are wrapped again with the new one. In “Rotation policy” you set the months for each key (12, 24 and 12 by default), the days of the session keys (90) and whether rotation is automatic. Every day administrators are emailed before the due date. Rotating, changing destinations and testing a restore ask for a new code from your authenticator app.
3. Backups
Every day an encrypted copy of the keys is made and uploaded to two places: Azure (another region) and Scaleway in the Netherlands. “Generate the backup key” creates the key pair: the server keeps only the public key and gives you the private one once, to download or print with a QR code. Keep it offline and apart from the backups. The destinations table shows the last copy, its size and whether it was downloaded again and matched. “Configure destinations” changes the credentials without touching the server.
4. Test the restore
“Test restore” asks for a backup file and the backup private key. The server opens them in memory, checks that every key opens the check sealed when the backup was made and shows what it contains. It stores nothing and activates no key. Run it at least every quarter. A real restore is done with a command and two people, as the operations documentation describes.
5. Root key and activity log
The private keys are in the database sealed with a root key that lives only in the secret manager. “Change the root key” (under “More”) seals them again with a new key that is shown once: store it in the secret manager before restarting. Below, the “Activity log” records every rotation, backup, test and policy change, with who did it.