Commit 8bea1747 authored by Santeri Toikka's avatar Santeri Toikka
Browse files

Cleaned up the structure

parent 2358c9a0

EN-304-621.md

+57 −74
Original line number Diff line number Diff line
@@ -757,42 +757,29 @@ Application monitoring requirements: 
-   **[REQ-MON-10]** GUI and API latencies are tracked and reported.

-   **[REQ-MON-11]** GUI and API error rates are tracked and reported.



Manfacturer shall implement monitoring system features as listed in the table below.



| Name                              | [COM-L-0]     | [COM-L-1]   | [COM-L-2]         |  [COM-L-3]  |

| --------------------------------- | ------------- | ----------- | ----------------- | ----------- |

| Complexity of the managed element | Limited IoT   | Home device | Enterprise router | Basestation |

| [REQ-MON-0 test]                  | Required      | Required    | Required          | Required    |

| [REQ-MON-1 test]                  | Required      | Required    | Required          | Required    |

| [REQ-MON-2 test]                  | Required      | Required    | Required          | Required    |

| [REQ-MON-3 test]                  | Required      | Required    | Required          | Required    |

| [REQ-MON-4 test]                  | Required      | Required    | Required          | Required    |

| [REQ-MON-5 test]                  | Required      | Required    | Required          | Required    |

| [REQ-MON-6a test]                 | Required      | Required    | Required          | Required    |

| [REQ-MON-6b test]                 | Not required  | Required    | Required          | Required    |

| [REQ-MON-7 test]                  | Required      | Required    | Required          | Required    |

| [REQ-MON-8a test]                 | Required      | Required    | Required          | Required    |

| [REQ-MON-8b test]                 | Not required  | Required    | Required          | Required    |

| [REQ-MON-9 test]                  | Required      | Required    | Required          | Required    |

| [REQ-MON-10 test]                 | Required      | Required    | Required          | Required    |

| [REQ-MON-11 test]                 | Required      | Required    | Required          | Required    |



[REQ-MON-0 test]: #63x0-req-mon-0

[REQ-MON-1 test]: #63x1-req-mon-1

[REQ-MON-2 test]: #63x2-req-mon-2

[REQ-MON-3 test]: #63x3-req-mon-3

[REQ-MON-4 test]: #63x4-req-mon-4

[REQ-MON-5 test]: #63x5-req-mon-5

[REQ-MON-6a test]: #63x6-req-mon-6

[REQ-MON-6b test]: #63x6-req-mon-6

[REQ-MON-7 test]: #63x7-req-mon-7

[REQ-MON-8a test]: #63x8-req-mon-8

[REQ-MON-8b test]: #63x8-req-mon-8

[REQ-MON-9 test]: #63x9-req-mon-9

[REQ-MON-10 test]: #63x10-req-mon-10

[REQ-MON-11 test]: #63x11-req-mon-11



Matching tests for these requirements are listed in [6.3.x Monitoring tests](#63x-monitoring-tests).

Manfacturer shall implement requirements as listed in the table below.



| Name                              | [COM-L-0]     | [COM-L-1]   | [COM-L-2]         |  [COM-L-3]  | [6.3.6 Monitoring tests]     |

| --------------------------------- | ------------- | ----------- | ----------------- | ----------- | ---------------------------- |

| Complexity of the managed element | Limited IoT   | Home device | Enterprise router | Basestation |                              |

| [REQ-MON-0]                       | Required      | Required    | Required          | Required    | [6.3.6.0](#6360-req-mon-0)   |

| [REQ-MON-1]                       | Required      | Required    | Required          | Required    | [6.3.6.1](#6360-req-mon-1)   |

| [REQ-MON-2]                       | Required      | Required    | Required          | Required    | [6.3.6.2](#6360-req-mon-2)   |

| [REQ-MON-3]                       | Required      | Required    | Required          | Required    | [6.3.6.3](#6360-req-mon-3)   |

| [REQ-MON-4]                       | Required      | Required    | Required          | Required    | [6.3.6.4](#6360-req-mon-4)   |

| [REQ-MON-5]                       | Required      | Required    | Required          | Required    | [6.3.6.5](#6360-req-mon-5)   |

| [REQ-MON-6a]                      | Required      | Required    | Required          | Required    | [6.3.6.6](#6360-req-mon-6)   |

| [REQ-MON-6b]                      | Not required  | Required    | Required          | Required    | [6.3.6.6](#6360-req-mon-6)   |

| [REQ-MON-7]                       | Required      | Required    | Required          | Required    | [6.3.6.7](#6360-req-mon-7)   |

| [REQ-MON-8a]                      | Required      | Required    | Required          | Required    | [6.3.6.8](#6360-req-mon-8)   |

| [REQ-MON-8b]                      | Not required  | Required    | Required          | Required    | [6.3.6.8](#6360-req-mon-8)   |

| [REQ-MON-9]                       | Required      | Required    | Required          | Required    | [6.3.6.9](#6360-req-mon-9)   |

| [REQ-MON-10]                      | Required      | Required    | Required          | Required    | [6.3.6.10](#6360-req-mon-10) |

| [REQ-MON-11]                      | Required      | Required    | Required          | Required    | [6.3.6.11](#6360-req-mon-10) |



Matching tests for these requirements are listed in [6.3.6 Monitoring tests].



[6.3.6 Monitoring tests]: #636-monitoring-tests



### 5.3.7 Data minimization
@@ -818,6 +805,8 @@ The high availability requirements are: 
-   <mark>How to include protections against DDoS or similar?</mark>

    -   Unwanted traffic in the interfaces can cause a denial of service from the managed elements.



Manfacturer shall implement requirements as listed in the table below.



| Name       | ACC-L-0    | ACC-L-1                | ACC-L-2            | ACC-L-3         |

| ---------- | ---------- | ---------------------- | ------------------ | --------------- |

| Network    | Air gapped | Single public endoint  | Multiple endpoints | Everything else |
@@ -834,13 +823,17 @@ The high availability requirements are: 
| [REQ-HA-2]                        | Not required | Required                    | Required |

| [REQ-HA-3]                        | Not required | Required                    | Required |



| Name                  | [EXP-L-0]      | [EXP-L-1]   |

| --------------------- | -------------- | ----------- |

| Entity classification | Undefined      | NIS2 entity |

| [REQ-HA-0]            | Not required   | Required    |

| [REQ-HA-1]            | Not required   | Required    |

| [REQ-HA-2]            | Not required   | Required    |

| [REQ-HA-3]            | Not required   | Required    |

| Name                  | [EXP-L-0]      | [EXP-L-1]   | [6.3.8 High availability tests] |

| --------------------- | -------------- | ----------- | ------------------------------- |

| Entity classification | Undefined      | NIS2 entity |                                 |

| [REQ-HA-0]            | Not required   | Required    | [6.3.8.0](#6380-req-ha-0)       |

| [REQ-HA-1]            | Not required   | Required    | [6.3.8.1](#6380-req-ha-1)       |

| [REQ-HA-2]            | Not required   | Required    | [6.3.8.2](#6380-req-ha-2)       |

| [REQ-HA-3]            | Not required   | Required    | [6.3.8.3](#6380-req-ha-3)       |



[6.3.8 High availability tests]: #638-high-availability-tests



Matching tests for these requirements are listed in [6.3.8 High availability tests].



# 6 Conformity assesments and tests
@@ -1056,20 +1049,11 @@ The high availability requirements are: 


## 6.3 Risk mitigations tests



### 6.3.x Logging tests



| Requirement  | Objective                                                                                |

| ------------ | ---------------------------------------------------------------------------------------- |

| [REQ-LOG-1]  | From the running process, it is impossible to overwrite the stored log output.           |

| [REQ-LOG-2]  | Technical documentation specifies how to integrate into an external logging system.      |

| [REQ-LOG-3]  | Detailed information of all emitted events is available.                                 |

| [REQ-LOG-4]  | National MSAs are able to validate the system design comformity without a deployment.    |

| [REQ-LOG-6a] | SIEM event for anomalities in clock accuracy is included in the technical documentation. |

| [REQ-LOG-6b] | SIEM event is emitted when clock anomalies occur.                                        |

### 6.3.5 Logging tests



### 6.3.x Monitoring tests

### 6.3.6 Monitoring tests



#### 6.3.x.0 REQ-MON-0

#### 6.3.6.0 REQ-MON-0



**Objective**: Collected and stored metrics data can not be altered.<br/>

**Preparation**:
@@ -1077,7 +1061,7 @@ The high availability requirements are: 
**Verdict**: Pass if no process step allows the alteration before ingestion of collected metrics data after it has left the target.<br/>

**Supporting Evidence**: The technical documentation.<br/>



#### 6.3.x.1 REQ-MON-1

#### 6.3.6.1 REQ-MON-1



**Objective**: Historical metrics data import overwriting an existing data point is noticed.<br/>

**Preparation**:
@@ -1098,7 +1082,7 @@ The high availability requirements are: 
1. Collect output showing the whether the current metrics data is being handled by the normal flow as expected.

1. Collect output showing how the modfied data set was accepted or discarded.



#### 6.3.x.2 REQ-MON-2

#### 6.3.6.2 REQ-MON-2



**Objective**: Metric name, purpose, and value interpretation are described for the user.<br/>

**Preparation**:
@@ -1123,7 +1107,7 @@ The high availability requirements are: 
1. The technical documentation.

1. Screenshot of the GUI displayging how the data is displayed.



#### 6.3.x.3 REQ-MON-3

#### 6.3.6.3 REQ-MON-3



**Objective**: Metrics cadence, accuracy and storage time are described for the user.<br/>

**Preparation**:
@@ -1146,7 +1130,7 @@ The high availability requirements are: 
1. The technical documentation.

1. Metrics storage plan.



#### 6.3.x.4 REQ-MON-4

#### 6.3.6.4 REQ-MON-4



**Objective**: System does not collect metrics that are not used in operative purposes.<br/>

**Preparation**:
@@ -1170,7 +1154,7 @@ The high availability requirements are: 
1. Metrics comformity assesment.

1. Product position in relation to GDPR.



#### 6.3.x.5 REQ-MON-5

#### 6.3.6.5 REQ-MON-5



**Objective**: Relevant system and connected element metrics like CPU, memory, disk utilisation are tracked and reported.<br/>

**Preparation**:
@@ -1192,7 +1176,7 @@ The high availability requirements are: 
1. The technical documentation.

1. Screenshot of the GUI displayging how the data is displayed.



#### 6.3.x.6 REQ-MON-6

#### 6.3.6.6 REQ-MON-6



**Reference**: **[REQ-MON-6a]** and **[REQ-MON-6b]** <br/>
@@ -1216,7 +1200,7 @@ The high availability requirements are: 


**Supporting Evidence**: Log or and metrics output showing detected system or managed element crash or restart with the reported cause.<br/>



#### 6.3.x.7 REQ-MON-7

#### 6.3.6.7 REQ-MON-7



**Objective**: Managed elements and system nodes and provided services availabilities and statuses are tracked and reported.<br/>

**Preparation**:
@@ -1239,7 +1223,7 @@ The high availability requirements are: 
1. The technical documentation.

1. Screenshot of the GUI displayging how the data is displayed.



#### 6.3.x.8 REQ-MON-8

#### 6.3.6.8 REQ-MON-8



**Reference**: **[REQ-MON-8a]** and **[REQ-MON-8b]** <br/>

**Objective a**: Relevant system database and storage health metrics like queries per second, latency and throughput are tracked and reported.<br/>
@@ -1268,7 +1252,7 @@ The high availability requirements are: 
1. The technical documentation.

1. Screenshot of the GUI displayging how the data is displayed.



#### 6.3.x.9 REQ-MON-9

#### 6.3.6.9 REQ-MON-9



**Objective**: Relevant networking metrics like throughput and protocol errros are tracked and reported.<br/>

**Preparation**:
@@ -1292,7 +1276,7 @@ The high availability requirements are: 
1. The technical documentation.

1. Screenshot of the GUI displayging how the data is displayed.



#### 6.3.x.10 REQ-MON-10

#### 6.3.6.10 REQ-MON-10



**Objective**: GUI and API latencies are tracked and reported.<br/>

**Preparation**:
@@ -1315,7 +1299,7 @@ The high availability requirements are: 


1. Relevant metrics described in the technical documentation.



#### 6.3.x.11 REQ-MON-11

#### 6.3.6.11 REQ-MON-11



**Objective**: GUI and API error rates are tracked and reported.<br/>

**Preparation**:
@@ -1338,9 +1322,9 @@ The high availability requirements are: 
1. System log output.

1. Relevant metrics described in the technical documentation.



### 6.3.x High availability tests

### 6.3.8 High availability tests



#### 6.3.x.0 REQ-HA-0

#### 6.3.8.0 REQ-HA-0



**Objective**: Expected availability is defined for each relevant system component.<br/>

**Preparation**:
@@ -1361,7 +1345,7 @@ The high availability requirements are: 
1. Relevant metrics described in the technical documentation.

1. Screen shots of metrics being visualised in the dashboards.



#### 6.3.x.1 REQ-HA-1

#### 6.3.8.1 REQ-HA-1



**Objective**: System tolerates loss of resources.<br/>

**Preparation**:
@@ -1382,7 +1366,7 @@ The high availability requirements are: 


1. Structured log output or other documentation that shows made actions and perceived operative response.



#### 6.3.x.2 REQ-HA-2

#### 6.3.8.2 REQ-HA-2



**Objective**: Disaster recovery plan is available.<br/>

**Preparation**: None <br/>
@@ -1402,7 +1386,7 @@ The high availability requirements are: 


1. Written evaluation.



#### 6.3.x.3 REQ-HA-3

#### 6.3.8.3 REQ-HA-3



**Objective**: System updates and changes are included in the availability definition.<br/>

**Preparation**: None <br/>
@@ -1463,7 +1447,6 @@ The high availability requirements are: 
[5.3.7 Data minimization]: #537-data-minimization

[5.3.8 High Availability]: #538-high-availability





# Annex B (informative): Relationship between the present document and any related ETSI standards (if any)



> List any related ETSI standards and how they interact with the present document.