Commit a56b1124 authored by Santeri Toikka's avatar Santeri Toikka
Browse files

Updated wording in the assessments second patch 

Closes #56, #58, #60, #59
parent a5152f11

EN-304-621.md

+9 −8
Original line number Diff line number Diff line
@@ -843,7 +843,7 @@ DDoS mitigations: 


**Activities:**



1. Dump all clock from all participating systems and nodes.

1. Dump all clock from all participating systems and computational nodes.

2. Ensure that the clock deviation is within limits specified in the techinal documentation.

3. If unsure, verify that the clock synchronisation mechanism is in use and functioning in the default installation.
@@ -984,7 +984,7 @@ DDoS mitigations: 


#### 6.3.6.0 REQ-METRICS-0



**Objective:** An attacker wants to hide its operations. System should prepare for that.<br/>

**Objective:** Verifies the ingestion pipline design upholds integrity and confidentiality requirements.<br/>

**Preparation:** None<br/>

**Activities:**
@@ -1134,8 +1134,8 @@ DDoS mitigations: 


**Verdict:**



1. Pass if Service Level Indicator defines and implements expected operation availability per connected element and relevant system processes.

1. Fail otherwise.

1. Pass if expected operation availability is defined per connected element and relevant system processes.

2. Fail otherwise.



**Supporting Evidence:**
@@ -1227,11 +1227,12 @@ DDoS mitigations: 


**Activities:**



1.  Study the metrics for availability information

1.  Study the metrics for availability information provided in the technical documentation

2.  Check in the system whether the features are available as described in the technical documentation



**Verdict:**



1. Pass all relevant components availability is defined and tracked

1. Pass, if all relevant features are available as defined and tracked.

1. Fail otherwise.



**Supporting Evidence:**
@@ -1294,7 +1295,7 @@ DDoS mitigations: 
**Verdict:**



1. Pass if recovery expectations are clearly defined,

2. and the system returns to stability after removal of the largest resource in the toleration description,

2. and the system returns to stability after removal of the the maximum capasity mentioned in the toleration description,

3. and the deleted or removed resources returns operation after they are reintroduced to the system,

4. and the defined high availability is hold.

5. Fail otherwise.
@@ -1318,7 +1319,7 @@ DDoS mitigations: 
**Verdict:**



1. Pass if recovery expectations are clearly defined

1. and the distribution of the system operation is within reasonable scope in regards of the production size.

1. and the distribution of the system operations is within reasonable scope in regards to the production computational resources.

1. Fail otherwise.



**Supporting Evidence:**