Commit 62e817fd authored by Sammy Haddad's avatar Sammy Haddad
Browse files

Update file EN-304-624.md

parent 1262f23c
Loading
Loading
Loading
Loading
+6 −58
Original line number Diff line number Diff line
@@ -353,7 +353,7 @@ Void.

## 3.3 Abbreviations

For the purposes of the present document, the [following] abbreviations  apply:
For the purposes of the present document, the following abbreviations apply:

<table style="width: 100%; border-collapse: collapse;">
  <colgroup>
@@ -3320,7 +3320,7 @@ updatable by a recommended algorithm in the documentation.
# Annex U: Use case description

## U.1 UC1 - Product for use in Private PKI for non critical sectors
### U.1.2 General description
### U.1.2 UC1 - General description
A private enterprise using public-key cryptography that manages a PKI internally to the enterprise. The enterprise therefore manages the policy framework, the generation of key pairs, the certification of key pairs and the purposes of keys.
In such organisations the PKI may be organised on department centric hierarchies, or on location centric hierarchies, or on organisation role hierarchies or some combination of these. Whilst the set of services to be enabled by the PKI in this use case are large they may include VPN access and management, timestamp services, disk or message encryption, email, and document access and distribution and so on. The deployment of such a private Public Key Infrastructure (PKI) is not driven by regulatory or standardized requirements but rather by the need to align with the entity’s internal policies and security practices.
Additionally, users of these PKI solutions often prioritize flexibility and ease of use over highly secure but restrictive technologies. For instance, they will not rely on Secure Cryptographic Devices (SCD) but rather have private keys stored using operating system or platform key management facilities that provide protection against unauthorised access at rest. The manufacturer shall document the protection mechanisms relied upon and their limitations. Where the platform facility supports hardware-backed protection (e.g. TPM), this should be the preferred configuration.
@@ -3536,7 +3536,7 @@ In this UC the product should be able to defined user profile restriction on fun

## U.2 UC2 - Product for use in Private PKI for critical entities

### U.2.2 General description (?)
### U.2.2 UC2 - General description
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,
@@ -3557,58 +3557,32 @@ As a result, users of these PKI solutions do not have the same deployment flexib
### U.2.3 UC2 - List of functions
Product audit & administration
- F.UserAccountManagement: Creation, modification, rights attributions and modification of the different user accounts.


- F.Network_Configuration: Set up of network addresses and protocols for the different product network interfaces (management, certificate generation/revocation/status requests, etc.).


- F.AuditEventManagement: Configuration of audit events to be stored and their associated format. Search or erasure capabilities associated to stored audit events.


- F.LoggingOfSecurityEvents: For example, account access attempts, product configuration changes, and system warnings or errors.


- F.CertificateProfileManagement: Administration functions to define format and default values of certificates to be signed.
Registration
- F.OnlineRegService: A remote certificate enrolment interface (or Certificate Request Service) that enables users to submit certificate signing requests (CSRs) or certificate creation requests from any network-connected device.


- F.CertificateDissemination: Distributes signed certificates to subscribers; and, if applicable, stores and makes them available to relying parties.


- F.PrivateKeyExport: Private key, secret key or critical data can be encrypted and then exported in the form of an encrypted file.


- F.OfficerRegistrationApproval: Explicit user (Officer) approval of registration requests.


Certificate generation

- F.SCD_BasedKeyPairGen:	Request the generation of the public-private key pair to an external SCD.

- F.Non_SCD_BasedKeyPairGen: Generates the public-private key pair.

- F.SubjectCertSignCreation: Creates and signs subject certificates based on the identity and other attributes verified by the registration service


- F.OfficerCertGenApproval: Privileged users to approve and execute this issuance, when certificates are issued.


Certificate status
- F.CertificateStatus: Maintains certificate status information (e.g. active, expired, revoked).


Revocation management
- F.RevocationManagement: Processes revocation requests and reports to determine the necessary action to be taken; and provides updates to the certificate status service.


- F.OfficerRevocationApproval: Explicit user (Officer) approval of certificate revocation requests.


### U.2.3.1 UC2 - Assets

TODO


**Table: Mapping between Functions and Assets for UC2**

@@ -3715,6 +3689,7 @@ TODO
</table>

</div>

### U.2.4 UC2 - Operational Environment

Physical/Hardware
@@ -3723,10 +3698,8 @@ Logical Software
- SOE.FullyControlled: Fully controlled logical operational environment (segregation, least priviledged, network protection e.g. firewalls/IDS/IPS/etc.). Only authorised users can access the product interfaces and network data.

- EC.Audit records secure storage: External hardware and software use to store audit data.

- EC.Timesource: A network server that synchronizes the clocks of devices within an IT infrastructure to ensure consistent and accurate timekeeping for security, logging, and operational purposes.


Connectivity
- COM.Local: Local communication

@@ -3735,47 +3708,27 @@ Connectivity

Distribution
- ARC.Monolithic: all components are integrated and run on a single machine or platform.

or

- ARC.Distributed: functions are split across multiple machines or services, often communicating over a network.


or

- ARC.PrivateCloud: product is deployed on a private cloud where HW infrastructure as well as orchestrator layer are in control of the organization  managing the PKI).


or

- ARC.PublicCloud: product is deployed on a public cloud where HW and orchestrator layer are managed by the cloud company.

Interfaces
- I.AuditAndAdministration: interface for remote access to for product for administration and audit purposes.


- I.Registration: online registration interface receiving remote Certificates Signing Requests from subscribers.


- I.CertificateGeneration:	Interface with external components providing cryptographic services such as signature or key management.

- I.ExternalKMS: interface with external components providing cryptographic services such as signature or key management.

- I.CertificateStatus: online certificate status requests and dissemination.


- I.RevocationManagement: online access to revocation management services (certificate revocation requests).


- I.NetworkServices: Interface to local network services (secure storage, timesources, user directory)

### U.2.6 UC2 - Users
In this UC the product should be able to defined user profile restriction on function associated to the following role:

- U.Administrator: Install, configure, and maintain the product, ensuring its proper operation and security.

- U.Officer (or Registration Authority Officer)	Manage certificate life-cycle operations, including approvals and revocations e.g. Configure profiles, policies, and security parameters, review and approve or reject certificate requests based on policy compliance, initiate and manage certificate revocation (e.g., due to compromise, expiration, or policy violations), verify the identity and authenticity of certificate applicants, ensure that certificate issuance and revocation processes align with organizational policies.

- U.Auditor	Authorized to monitor and review product operations logs to ensure compliance and security.

## U.3 UC3 - Public PKI for critical entities
@@ -3791,7 +3744,6 @@ Such PKIs are deployed in highly controlled environments, including robust physi

![Figure U.3.2: UC3 functional architecture](media/Figures/UC_Architecture/UC3.png)


### U.3.3 UC3 - List of functions

Product audit & administration
@@ -3902,20 +3854,17 @@ Revocation management

Physical/Hardware
- POE.FullyControlled: Fully controlled physical operational environment, where only authorized users have access to the product interfaces.

- POE.SCD: The environment provides a Secure Cryptographic Device (often taking the form of an Hardware Security Module) to generate keys and provide signature support.

Logical Software
- SOE.FullyControlled:	Fully controlled logical operational environment (segregation, least priviledged, network protection e.g. firewalls/IDS/IPS/etc.). Only authorised users can access the product interfaces and network data.


Required external components
- EC.Timesource:	A network server that synchronizes the clocks of devices within an IT infrastructure to ensure consistent and accurate timekeeping for security, logging, and operational purposes.
- EC.UserDirectory:	A directory server that centrally stores, organizes, and provides access to user, group, and resource information (e.g., authentication credentials, contact details) for networked systems and applications.

Connectivity
- COM.Public: Public communication

- COM.Local: Local communication

### U.3.5 UC3 - Distribution of Security Functions
@@ -3926,7 +3875,6 @@ Distribution
- ARC.Distributed:	Functions are split across multiple machines or services, often communicating over a network .
- ARC.PrivateCloud:	Product is deployed on a private cloud where HW infrastructure as well as orchestrator layer are in control of the organization  managing the PKI)


Interfaces

- I.LocalInterface:	Local interface used by the different privileged users to access the product functionalities and data.
@@ -3937,16 +3885,16 @@ Interfaces
- I.RevocationManagement:	Online access to revocation management services (certificate revocation requests).
- I.NetworkServices:	Interface to local network services (secure storage, timesources, user directory


### U.3.6 UC3 - Users
In this UC the product should be able to defined user profile restriction on function associated to the following role:
- U.Administrator:	Install, configure, and maintain the product, ensuring its proper operation and security.
- U.Operator:	Performs operational tasks to ensure the availability and integrity of the product and data, e.g. execute system backups and recovery procedures to prevent data loss, monitor product health and performance, manage routine operational tasks, such as certificate issuance workflows.
- U.Officer: (or Registration Authority Officer)	Manage certificate life-cycle operations, including approvals and revocations e.g. Configure profiles, policies, and security parameters, review and approve or reject certificate requests based on policy compliance, initiate and manage certificate revocation (e.g., due to compromise, expiration, or policy violations), verify the identity and authenticity of certificate applicants, ensure that certificate issuance and revocation processes align with organizational policies.
- U.Auditor:	Authorized to monitor and review product operations logs to ensure compliance and security.

## U.4 UC4 - Product for use in Critical Public basic PKI

### U.4.1 General description
### U.4.1 UC4 - General description

product used to support certification services (certificate generation, revocation and status management) 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.