A Digital Signature Certificate is, at the file level, a pairing of a public key with an identity. The security comes from what happens to the matching private key. If the private key sits in a file on a laptop, it can be copied, and a copy can sign documents in your name. That is the entire reason the USB crypto token exists.

FIPS 140-3 is the current standard for cryptographic modules, and it is what the tokens we supply are validated against.

What the token actually does

  • Generates the private key inside the device, so it is never exposed to the operating system
  • Marks the key as non-exportable, which means it cannot be copied off
  • Performs the signing operation inside the chip, so the key never enters RAM
  • Requires a PIN to authorise each signature

The result is that possessing the token is as meaningful as possessing the PIN, and losing one without the other does not hand over your identity.

Why software certificates fail on portals

Tendering and procurement portals need to trust that the signature came from a specific person or firm and cannot be repudiated later. A key held in a portable file undermines that: anyone with a copy of the file and the password could have signed.

When a portal shows a certificate as invalid or refuses to sign, the cause is frequently a certificate that was issued in a software or file-based profile instead of a hardware-token profile.

What FIPS 140-3 means in practice

FIPS is a US federal standard published by NIST, and 140-3 is the current revision. A validated module has been tested for:

  • the strength and correct implementation of its cryptography
  • tamper evidence, so physical probing is detectable
  • documented key generation, storage and destruction

For a DSC holder, the practical benefit is that the portal, the Certifying Authority and the token all rely on an independently tested cryptographic boundary. It is not a marketing label; it is a test report.

The certificate and the token are separate products

This trips people up constantly. A certificate is issued by a Certifying Authority. A token is a physical device. Buying a certificate does not include a token unless the listing says so, and a token bought separately arrives un-initialised until a certificate is loaded onto it.

Our price list keeps the two as separate lines so the split is visible before you pay.

Tokens we supply

We issue onto standard USB crypto tokens, including ProxKey, Hyp2003 and mToken. All three work with the common portal signing utilities. The right choice depends on the operating system you file from, whether you need a driver for older portal components, and whether the device will live on a shared office machine.

Looking after the token

  • Treat it as you would a debit card: the device plus the PIN is the credential.
  • Never share the PIN, including with a colleague who is filing on your behalf. Use a separate certificate for a shared role instead.
  • Keep the token in a dry place. USB contacts corrode.
  • Put the expiry date in a calendar at least 30 days before it lapses. A token that still works is reusable across renewals, so the hardware cost does not repeat.

Does a renewal need a new token

No. The token is reusable. A renewal loads a new certificate onto the existing device, provided the device is functional and supports the required key length. Most tokens in use today do.

Next steps

Compare token options, then order a Class 3 DSC. If you already own a token, we can issue onto it and you pay for the certificate only.