{"id":350109,"date":"2024-10-20T00:40:27","date_gmt":"2024-10-20T00:40:27","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-419241-12018\/"},"modified":"2024-10-26T00:25:15","modified_gmt":"2024-10-26T00:25:15","slug":"bs-en-419241-12018","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-419241-12018\/","title":{"rendered":"BS EN 419241-1:2018"},"content":{"rendered":"

1.1 General<\/b><\/p>\n

This document specifies security requirements and recommendations for Trustworthy Systems Supporting Server Signing (TW4S) that generate digital signatures.<\/p>\n

The TW4S is composed at least of one Server Signing Application (SSA) and one Signature Creation Device (SCDev) or one remote Signature Creation Device.<\/p>\n

A remote SCDev is a SCDev extended with remote control provided by a Signature Activation Module (SAM) executed in a tamper protected environment. This module uses the Signature Activation Data (SAD), collected through a Signature Activation Protocol (SAP), in order to guarantee with a high level of confidence that the signing keys are used under sole control of the signer.<\/p>\n

The SSA uses a SCDev or a remote SCDev in order to generate, maintain and use the signing keys under the sole control of their authorized signer. Signing key import from CAs is out of scope.<\/p>\n

So when the SSA uses a remote SCDev, the authorized signer remotely controls the signing key with a high level of confidence.<\/p>\n

A TW4S is intended to deliver to the signer or to some other application, a digital signature created based on the data to be signed.<\/p>\n

This standard:<\/p>\n