@@ -2348,7 +2348,7 @@ Risk, as per TS 102 165-1 [] is calculated as the product of impact and likeliho
</div>
#### Network security
#### Network and Physical security
<divalign="center">
@@ -4082,7 +4082,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 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.
@@ -4095,9 +4095,9 @@ TO DO - Include UC1 functional figure
