Commit bc79230e authored by Sammy Haddad's avatar Sammy Haddad
Browse files

Update file EN-304-624.md

parent bd77d3e5
Loading
Loading
Loading
Loading
+2 −3
Original line number Diff line number Diff line
@@ -539,8 +539,6 @@ Additionally, users of these PKI solutions often prioritize flexibility and ease

### 4.6.2 Product for use in Critical entity PKI

> - EXAMPLE: eIDAS

Critical entities often need to produce their own certificates to manage sensitive IT and network services. These services include VPNs, remote SSH connections, timestamp services, disk or message encryption, and PDF signatures. The deployment of such a private Public Key Infrastructure (PKI) is governed by regulatory or standardized requirements, which impose strict constraints, such as:
- Network and physical security,
- Encryption and access control of digital data,
@@ -549,6 +547,8 @@ Critical entities often need to produce their own certificates to manage sensiti

As a result, users of these PKI solutions do not have the same deployment flexibility as in less regulated use cases (e.g., UC1). However, they are still permitted to use PKI products that offer diverse functionalities.

> - EXAMPLE: eIDAS

### 4.6.3 Product for use in Public CA PKI
PKI product used to support certification services provided within very large multi-site company or provided by a CA to the public, and where a compromise carries a significant risk of impact to the security of remote or unknown users, other products, networks or services, or to the health, security or safety of the public.

@@ -564,7 +564,6 @@ EXAMPLE 2: In a smart contract environment, such as that outlined in ETSI TR 119

<mark>The use cases may be defined by a combination of the product context elements described in clauses 4.1 to 4.5.</mark>


# 5 Technical requirements for the Products

## 5.1 Introduction - Applicability of the requirements