Skip to content

CEN EN 419 241-1: Trustworthy Systems Supporting Server Signing - Part 1: General System Security Requirements #101

Description

@IshaiO

Formal name

CEN EN 419 241-1: Trustworthy Systems Supporting Server Signing - Part 1: General System Security Requirements

Overview

This document specifies security requirements and recommendations for Trustworthy Systems Supporting Server Signing (TW4S) that generate digital signatures. The TW4S is composed at least of one Server Signing Application (SSA) and one Signature Creation Device (SCDev) or one remote Signature Creation Device.

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.

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.

So when the SSA uses a remote SCDev, the authorized signer remotely controls the signing key with a high level of confidence.

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.

Work Plan

There is no work plan.

Updates

There are no updates.

Alerts

There are no open alerts.

References

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Domain: Trust ServicesSTS underpinning trust infrastructure, including electronic signatures, timestamps, certificatesFn: QESFunctional: Qualified Electronic Signature, both for the Wallet and TSPsSecuritySecurity of the EUDI Wallet domain and the Trust Services domainnpaThe standard is not publicly availablests: cross milestoneDescribes a standard with gap affecting more than one milestonessts: readyThe standard has a stable version published

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions