What Is a Qualified Electronic Signature (QES)?
András Somkuti ·
A qualified electronic signature (QES) is, under the EU’s eIDAS Regulation, “an advanced electronic signature that is created by a qualified electronic signature creation device, and which is based on a qualified certificate for electronic signatures” (Article 3(12)). It has “the equivalent legal effect of a handwritten signature” (Article 25(2)), and every EU member state recognises it as a QES (Article 24a(1)).
The visible moment of electronic signing can be almost disarmingly simple. A document appears, the signer confirms the action, authentication takes place and the completed file is returned within seconds. Nothing in that experience necessarily reveals whether the resulting signature is simple, advanced or qualified. That ambiguity is understandable, because qualification is not primarily a user-interface concept. It describes the trust architecture operating behind the interaction.
A qualified electronic signature under eIDAS brings together several elements that have to work as a coherent system: a verified individual, a qualified certificate, protected signature-creation data, an intentional signing action and a validation framework capable of connecting those elements later.
Before the signature, there is an identity
Cryptography can establish that a particular private key was used to create a signature. It cannot, by itself, tell us whether that key belongs to the person named on a contract. The identity layer precedes the cryptographic one.
When a qualified trust service provider issues a qualified certificate, eIDAS requires verification of the identity of the natural or legal person concerned through methods recognised by the regulatory framework. The amended regulation accommodates several routes, including notified electronic identification at a high assurance level, existing qualified certificates, physical presence and other sufficiently reliable identification methods subject to conformity assessment.
The practical consequence is that the certificate does not simply contain a name supplied by the user, its value comes from the controlled process through which the identity associated with that certificate was established.
A certificate is part of the story, not the whole story
Digital certificates are often discussed as though possessing one automatically determines the legal quality of every signature created with it. The reality is more structured.
A qualified electronic signature must be based on a qualified certificate for electronic signatures, while the signature itself must be created using a qualified electronic signature creation device, commonly abbreviated as QSCD.
Modern remote-signing architectures have made the word “device” somewhat misleading to non-specialists. The protected cryptographic environment does not necessarily have to be a smart card physically sitting on the signer’s desk. Remote qualified signature-creation mechanisms can protect keys within secure infrastructure while still giving the individual the necessary control over the act of signing.
As a result, two signing experiences may appear almost identical to the user while the assurance model beneath them is fundamentally different.
Authentication and signing should not be confused
There is another distinction hidden inside many digital workflows. Let’s take two events: logging into a service establishes access to an account and signing a specific document expresses an action in relation to specific data. These two can happen within seconds of each other, but they answer different questions.
An authentication system may establish that the correct account holder is present. The signing process must also establish what the person is authorising. In higher-assurance transactions, the relationship between intention and the exact document being signed cannot simply be assumed from the fact that somebody happened to be logged in. This is one of the reasons signature creation should be understood as a transaction in its own right.
Integrity enters the picture
Once the signature has been created, cryptographic techniques bind it to the signed data in a manner that makes subsequent modification detectable. And that characteristic changes the nature of the evidence.
A scanned handwritten signature can be extracted from one document and inserted into another. The visual result may be extremely convincing, particularly now that manipulation tools are widely available. A cryptographic signature is concerned less with appearance than with relationships: the signed data, the cryptographic key, the certificate and the validation information.
The signature may occupy only a small rectangle on the page, while the important evidence is largely invisible.
Qualification belongs to an ecosystem
The European trust framework also provides a mechanism for determining which providers and services actually carry qualified status. Member States maintain Trusted Lists, while the European Commission provides the List of Trusted Lists and tools for navigating that infrastructure. A provider or service gains the regulatory status associated with qualification through its presence on the appropriate Trusted List.
That regulatory backbone is easy to overlook when signing has been designed well.
The best user experiences deliberately hide much of the complexity. People should not have to understand certificate chains, cryptographic keys, revocation information or qualified signature-creation environments every time they approve a document. Yet those mechanisms become extremely relevant when an organisation needs to explain what happened.
A qualified electronic signature may take only seconds to create. The confidence placed in it has been built long before those seconds begin.
Get your qualified electronic signature in about 3 minutes from sign-up. Identify yourself by video on any device with a camera, or faster with the Netlock mobile app and a chip identity card. Every signature gets a qualified time stamp. Sign up for free and start with 15 free signatures.