The signing keys are used, with a low level of confidence, under the sole control of the signer.
The authorized signer’s use of its key for signing is enforced by the Server Signing Application Service Component which authenticates the signer. The activation of the signing key can remain for a given period and/or for a given number of signatures.
In case of SCAL1, the user relies on the server signing application to ensure that the appropriate signing key is selected. The functionality supporting signature activation and ensuring sole control is implemented as part of the server signing application.
SCAL1 signing architecture
The server signing application handles signature activation outside the QSCD. The cryptographic module is inside the QSCD.
SCAL1 signing architectureRead components, boundaries and directed exchanges
The server signing application handles signature activation outside the QSCD. The cryptographic module is inside the QSCD.
CA (Certification Authority) ↔ SSA (Server Signing Application)
RA (Registration Authority) ↔ CA (Certification Authority)
Signer ↔ User interface: Authentication
CM (Cryptographic Module) → SSA (Server Signing Application): Signature value
SSA (Server Signing Application) → CM (Cryptographic Module): DTBS (Data To Be Signed)
User interface ↔ SSA (Server Signing Application): Signature activation; DTBS (Data To Be Signed)
Arrows show exchange direction; double-headed arrows show exchanges in both directions. The activation band connects the user interface to the SSA. The band represents an exchange, not an additional environment boundary.
The signing keys are used, with a high level of confidence, under the sole control of the signer.
The authorized signer’s use of their key for signing is enforced by the signature activation module by means of signature activation data provided, by the signer, using a signature activation protocol, in order to enable the use of the corresponding signing key to sign specific documents.
SCAL2 provides greater assurance of sole control by requiring code within the HSM to implement signature activation, called signature activation module. This code is certified to the same security level as the HSM’s general cryptographic functions. The signature activation data passes, in protected form using the signature activation protocol, from the signer’s device to the HSM to ensure that the user’s signing keys can’t be abused, even if the TSP’s server signing application were to be compromised.
SCAL2 signing architecture
The signer activates the key through the SIC and protected SAP exchange with the SAM. The SAM and cryptographic module are inside the QSCD; the SSA is outside it.
SCAL2 signing architectureThe signer activates the key through the SIC and protected SAP exchange with the SAM. The SAM and cryptographic module are inside the QSCD; the SSA is outside it. SCA (Signature Creation Application) ↔ User interface. SCA (Signature Creation Application) ↔ SSA (Server Signing Application). Signer ↔ User interface: Document / data. RA (Registration Authority) ↔ User interface. CA (Certification Authority) ↔ SSA (Server Signing Application). RA (Registration Authority) ↔ CA (Certification Authority). Signer ↔ User interface: Authentication; 2FA. CM (Cryptographic Module) → SSA (Server Signing Application): Signature value. SSA (Server Signing Application) → SAM (Signature Activation Module): DTBS (Data To Be Signed). SAM (Signature Activation Module) → CM (Cryptographic Module): DTBS (Data To Be Signed). SIC (Signer Interaction Component) ↔ SAM (Signature Activation Module): SAP (Signature Activation Protocol); SAD (Signature Activation Data); DTBS (Data To Be Signed).SCASignature Creation ApplicationUnprotected environmentUser's deviceTSP protected environmentTrustworthy system supportingserver signingSignerUser interfaceSSAServer SigningApplicationTamper protected environmentQSCDRARegistration AuthorityCACertification AuthoritySAMSignatureActivation ModuleCMCryptographicModuleDocument /dataAuthentication2FASignature valueDTBSDTBSSAP · Signature Activation ProtocolSAD · Signature Activation DataDTBS · Data To Be SignedSICSignerInteractionComponentSCAL2 signing architectureRead components, boundaries and directed exchanges
The signer activates the key through the SIC and protected SAP exchange with the SAM. The SAM and cryptographic module are inside the QSCD; the SSA is outside it.
CA (Certification Authority) ↔ SSA (Server Signing Application)
RA (Registration Authority) ↔ CA (Certification Authority)
Signer ↔ User interface: Authentication; 2FA
CM (Cryptographic Module) → SSA (Server Signing Application): Signature value
SSA (Server Signing Application) → SAM (Signature Activation Module): DTBS (Data To Be Signed)
SAM (Signature Activation Module) → CM (Cryptographic Module): DTBS (Data To Be Signed)
SIC (Signer Interaction Component) ↔ SAM (Signature Activation Module): SAP (Signature Activation Protocol); SAD (Signature Activation Data); DTBS (Data To Be Signed)
Arrows show exchange direction; double-headed arrows show exchanges in both directions. The SAP band carries SAD and DTBS between the SIC and SAM. The band represents an exchange, not an additional environment boundary.