How VSX KMS/i keeps your keys
Encryption is only as good as the care of its keys. Most shops end up with keys scattered across the systems that use them: a storage array holds its own, a backup product holds its own, a database holds its own, and nobody can say in one place which keys exist, who has them, or when they were last changed. A key server fixes that: systems ask it for their keys, and it keeps every key, every rule about who may have one, and a record of every request.
VSX KMS/i is a key server that runs on IBM i. This page explains what it does, in plain terms, and where its limits are.
A bank's vault, with a front desk
Picture a bank's vault with a front desk in front of it.
The vault is an IBM i key store, sealed by the system's own master key. Every key the server keeps is made inside it and stays there, sealed. A copy of the system's disks without the master key opens nothing.
The front desk answers the systems that need keys. It speaks the industry's standard language for this, KMIP, which storage systems, virtualization platforms, backup products and databases use to ask a key server for keys. Before it answers, it checks who is asking: every system shows a certificate, and the desk only serves systems it has been told about.
Each key belongs to the system that asked for it. Other systems can't use it, or even find out that it exists, unless you give them the right to. A system that asks about a key it may not have hears "no such key", so it can't go looking for other systems' keys.
Keys leave the vault sealed. A key handed to a system goes out sealed for that system, so that only it can open it. Some systems can only take a key unsealed; you can allow that, one system at a time, and every such handover is recorded.
Every request goes in the ledger: which system, what it asked for, which key, and the answer. Every change people make through the server's screens or commands goes there too, with their name.
A second vault in another city
A key server that's down can stop everything that depends on it, so VSX KMS/i can keep standbys: second (and third) servers, on other IBM i systems, that copy every change from the primary within seconds. Each has its own vault and its own master key; the servers pass keys between them sealed, never in the clear. VSX DAR/i lists every server and tries the next when one doesn't answer; check that your other systems can too.
If the primary is lost, you promote a standby to take its place, by hand, so two servers can never both believe they are in charge. The ledger is copied too, so the new primary has the whole history.
The screens
Besides the commands, the server has its own web pages, served by the server itself, with nothing else to install. You sign on with your IBM i user profile and password, and see and do exactly what that profile's authority allows:
- the server's state, and whether it's the primary or a standby;
- the systems it serves, their certificates, and adding or removing them;
- the keys, their state, who may use each, and each key's history;
- the standbys, how far behind each one is, and promoting one;
- the ledger, searchable.
A group for auditors can sign on and see everything, and change nothing.
VSX DAR/i and VSX KMS/i
VSX DAR/i, our encryption product for database columns and backups, can take its keys from any KMIP key server, VSX KMS/i or another vendor's. Keys arrive sealed and go into DAR/i's own vault on each system, so a key server that's down never stops a database read or a backup. VSX KMS/i is sold on its own: it doesn't need VSX DAR/i, and DAR/i doesn't need it.
If your license runs out
Nothing stops. A key server that refused to serve keys would stop everything that depends on it, and we won't do that. Instead the system operator gets a message every day, from 30 days before the end, the screens show a banner, and the ledger records it.
The sharp edges, honestly
- The master key is the vault's door. Lose a server's master key, on the system and in your disaster recovery plan, and the keys in its vault are gone with it. A standby, with its own master key, is your protection against losing one server; keep both servers' passphrase parts with your custodians.
- The server is a target. It holds every key it serves. Keep it on a network only the systems that need keys can reach, keep its certificates current, and give its screens and commands only to the people who administer keys.
- Unsealed handovers are a real exposure. A key handed over unsealed is in the clear, briefly, in the server's memory and on the wire inside the encrypted connection. It's off by default; allow it only for systems that can't take a sealed key.
- Promotion is by hand. If the primary fails, keys can still be read from a standby, but new keys and changes wait until someone promotes one. That's deliberate: an automatic switch can leave two primaries.
- Check your products against it. KMIP has many versions and options, and products use different parts of it. VSX KMS/i speaks KMIP 1.0 to 1.4. We've tested it with our own client and with open-source KMIP tools; try each product you'll connect during a trial before you depend on it.
- Quantum computing. Keys are often sealed for the systems that take them with RSA, which standards bodies plan to retire after 2030. The keys themselves, AES-256, are not affected.