eIDAS & Trust Services

What Is Qualified Signature Creation Device (QSCD)?

A Qualified Signature Creation Device (QSCD) is a device certified to meet Annex II of the eIDAS Regulation, in which the private key for a qualified electronic signature is generated, kept and used. The same rules apply to qualified seal creation devices. A signature is only qualified if it is created by a QSCD, so the device is the third element next to the advanced signature and the qualified certificate.

What Annex II requires

The device must keep the signature creation data confidential, ensure it can practically occur only once, protect it against derivation and forgery, and let the legitimate signatory protect it against use by others. It must not alter the data to be signed or prevent the signatory from seeing it before signing.

Meeting those requirements is not self-declared. Conformity is certified by bodies that the Member States designate (Article 30), normally through a Common Criteria evaluation against a recognised protection profile, and the Commission publishes a list of certified devices based on the Member States' notifications (Article 31). A device certified in one Member State is recognised in all others.

Local devices: cards and tokens

The classic QSCD is a smart card or USB token in the hands of the signatory. Commission Implementing Decision (EU) 2016/650 names the evaluation standards: Common Criteria (ISO/IEC 15408) and the EN 419 211 series of protection profiles for secure signature creation devices. Sole control is easy to argue here, because the person holds the device and knows the PIN.

Remote QSCD and server signing

Most qualified signatures are now created remotely. The key sits in a hardware security module (HSM) at a provider, and the signatory authorises each signature from a phone or browser. The difficulty is sole control: the signatory must be the only one who can trigger use of the key, even though the provider operates the hardware.

The CEN standards for this split the problem in two. EN 419 221-5 is the protection profile for the cryptographic module, the HSM itself. EN 419 241-2 is the protection profile for the signature activation module, the component that verifies the signatory's authorisation and binds it to one specific signing operation before the key can be used. EN 419 241-1 sets the general security requirements for the server signing system around them.

eIDAS 2 gave this model a firm legal footing. Generating or managing signature creation data on behalf of a signatory may only be done by a qualified trust service provider providing a qualified service for the management of remote QSCDs (Articles 29 and 29a, and 39a for seals). The related implementing regulation references ETSI TS 119 431-1.

An HSM is not automatically a QSCD

A FIPS 140-3 validation or a general Common Criteria certificate does not make an HSM a QSCD. What counts is certification for this purpose, in the certified configuration, and for remote signing the combination of module and signature activation module operated by a qualified provider.

From the outside there are two indicators. The certificate can carry the QcSSCD statement (0.4.0.1862.1.4) and a policy OID ending in -qscd, such as QCP-n-qscd (0.4.0.194112.1.2). And the trusted list entry for the issuing service can carry qualifiers stating that its certificates have their keys in a QSCD, or in a QSCD managed on the subject's behalf.

Try it yourself — free tools

  • Certificate Checker — see whether a certificate carries the QcSSCD statement and a -qscd policy OID, and what the trusted list says about the issuer
  • Key Ceremony Planner — script the HSM key generation behind a signing service

How MI Support IT can help

PKI Tools is built by MI Support IT, a Danish IT company with deep specialization in enterprise PKI: ADCS design and health checks, Venafi certificate automation, key ceremonies and CP/CPS documentation. Read about our PKI services or get in touch.

PKI Glossary