Commit 938819a5 authored by esou's avatar esou
Browse files

Added a suggestion for the Interfaces / Updated the Distribution of Security functions chapter

parent 8b47bcbf
Loading
Loading
Loading
Loading
+5 −0
Original line number Diff line number Diff line
@@ -713,6 +713,9 @@ Each component defining the Product is accessible through the interfaces defined
**I.RevocationManagement**	- Online access to revocation management services (certificate revocation requests).
**I.NetworkServices**	- Interface to local network services  (secure storage, timesources, user directory

<mark>El-Houari Suggestion :</mark>

<mark>Interfaces are accessible through logical environment (COM.Local, COM.StrictLocal...), There I.UI becomes useless as it is a combination of COM.StrictLocal and I.AuditAndAdministration. Threfore, I suggest to remove I.UI.</mark>


### 4.3.2 Physical/Hardware environment
@@ -727,6 +730,8 @@ A cloud service provider should have strong physical security measures in place,

## 4.4 Distribution of Security Functions

Security functions distribution is presented in [Product Architecture](#42-product-architecture) and is further refined use case by use case in the annexes. This distribution depends, for each use case, on the product functional (F. parameters) scope together with its distribution parameters.

## 4.5 Users

The product contains a number of assets that need privileged access to use. The following user classes are identified from consideration of the least privilege paradigm to the product assets as identified in the product architecture of clause [4.2](#42-product-architecture).