From smart card to cloud.
How signing devices evolved: tokens, cards, chip IDs, server modules and remote signing.
Certificate based signing rests on one idea: the private key must be under the signer's sole control. For two decades, that idea took the form of physical objects: a protected file, a token on a key ring, a card with its reader. Today, more and more signatures are produced with keys that never leave a secure server. The goal has not changed; the way of achieving it has.
Five stages
| Device | How it works | Strength and limitation |
|---|---|---|
| Key file | The key lives in a password protected file on the computer. | Convenient, but it can be copied without the holder noticing. |
| USB token and smart card | The key is generated and stays inside a chip that never releases it; the software simply asks the chip to sign. | Much more secure; requires readers and drivers that fail. |
| Chip based identity document | The State includes a signing certificate in the national ID card. Estonia has done so since 2002; Uruguay, since 2015. | Universal and at no extra cost; still needs a reader or a compatible phone. |
| Phone | The phone's secure element or an app protects the key or authorizes its use. | It is in every pocket; security depends on the device. |
| Remote signing | The key lives in a provider's cryptographic module (HSM); the signer authorizes each signature with their own factors. | Works from any device; requires trusting the custody and auditing it. |
How sole control is maintained remotely
When the key sits on a server, the obvious question is how to guarantee that only its holder uses it. The answer combines three elements: a certified cryptographic module that stores the key and does not export it, a component that activates the key only when it receives valid authorization from the signer, and strong authentication of the signer to produce that authorization. CEN standards such as EN 419 241 describe these requirements, and frameworks such as eIDAS allow remote qualified electronic signatures when they are met.
What it gained and what it demands
- It gained reach. Without readers or drivers, high level signatures reach anyone with a phone.
- It gained integration. Applications can request signatures through standard interfaces, such as the one from the Cloud Signature Consortium.
- It demands trust in custody. The provider holding the keys must be certified, audited and supervised.
- It demands good authentication. If the second factor is weak, remote signing inherits that weakness.
Signing devices have evolved from key files to tokens, smart cards, chip based identity documents, phones and remote signing. The principle is still sole control of the key; in the cloud it is guaranteed by certified modules, signer authorization and strong authentication.