Commit 80b16631 authored by Sammy Haddad's avatar Sammy Haddad
Browse files

Section 4.2 update

parent a0a5b69a
Loading
Loading
Loading
Loading
+25 −21
Original line number Diff line number Diff line
@@ -423,31 +423,35 @@ Products with digital elements used as part of a public key cryptography scheme
The product contains the following elements:
<!-- Add definition of below elements -->

Here are the definitions for the requested PKI-related terms:

- **Private Key Store**:
   - A secure storage location where private keys are kept. It ensures that private keys are protected from unauthorized access and tampering. Private keys are used for decryption and digital signature creation.
   - Source: RFC 7519 (JSON Web Token), RFC 5208 (Public-Key Infrastructure Using X.509 (PKIX) Certificates)

- **Public Key Certificate Store**:
   - A repository that holds public key certificates. These certificates bind public keys to entities (such as users, devices, or services) and are used for verifying digital signatures and encrypting data.
   - Source: RFC 5280 (Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile)
Product audit & administration 
- F.UserAccountManagement
- F.Network_Configuration
- F.None_SCDBasedKeyManagement
- F.OfficerRegistrationApproval
- F.AuditEventManagement
- F.LoggingOfSecurityEvents 
- F.CertificateProfileManagement

- **Access Control Layer**:
   - A component of a system that enforces access control policies, determining who or what can view or use resources in a computing environment. It acts as a gatekeeper, verifying credentials and permissions before granting access.
   - Source: NIST SP 800-162 (Guide to Attribute Based Access Control (ABAC))
Registration
- F.OnlineRegService
- F.CertificateDissemination
- F.PrivateKeyExport
- F.OfficerRegistrationApproval

- **Access Control Policy Element**:
   - A rule or set of rules that define the conditions under which access to a resource is granted or denied. These policies specify who can access what, under what conditions, and with what permissions.
   - Source: NIST SP 800-162 (Guide to Attribute Based Access Control (ABAC))
Certificate generation
- F.SCD_BasedKeyPairGen
- F.NoneSCD_BasedKeyPairGen
- F.SubjectCertSignCreation
- F.OfficerCertGenApproval
- F.PseudonymCertIssuance

- **Signature Creation Entity**:
   - An entity (such as a person or software) that creates digital signatures using a private key. This entity signs data to ensure its authenticity and integrity.
   - Source: ETSI TS 119 495 (C-ITS Security; Trusted Security Entities)
Certificate status
- F.CertificateStatus 

- **Signature Verification Entity**:
   - An entity (such as a person or software) that verifies digital signatures using the corresponding public key. This entity checks the signature to confirm that the data has not been altered and that the signer is authentic.
   - Source: ETSI TS 119 495 (C-ITS Security; Trusted Security Entities)
Revocation management
- F.RevocationManagement 
- F.OfficerRevocationApproval


In addition the elements can be configured in multiple ways:
@@ -455,7 +459,7 @@ In addition the elements can be configured in multiple ways:
 - **ARC.Monolithic**: All components are integrated and run on a single machine or platform.
 - **ARC.Distributed**:  Functions are split across multiple machines or services, often communicating over a network.

![Figure 4.3-1: Indicative product architecture](media/indicative_architecture.png)
![Figure 4.3-1: Indicative product architecture](media/Figures/UC_Architecture/FunctionalArchitecture.png)


## 4.3 Operational Environment