**Objective:**Reduce the outages due to failed update.
**Objective:**The product outage time after a failed update is minimised.
**Preparation:**
@@ -2189,11 +2189,11 @@ Verify that:
### 6.5.7 SU_UPDATES-7
**Objective:**Protect the high availability of the system in peak usage hours and prevent of installation of updates that are known to break services.
**Objective:**The product allows to schedule or postpone updates that meet the high availability needs.
**Preparation:**
1.Have the product initialised and available with the default configuration and required credentials.
1.Study the interface and how scheduling or postponing of an update works.
2. Study the technical documentation.
**Activities:**
@@ -2202,7 +2202,7 @@ Verify that:
**Verdict:**
1. Pass, if the system user has control over when the update is made.
1. Pass, if the system user controls the point in time the update is made.
2. Fail otherwise.
**Supporting Evidence:**
@@ -2214,7 +2214,7 @@ Verify that:
### 6.5.8 SU_UPDATES-8
**Objective:**Rollback operations are auditable.
**Objective:**Any rollback operation is authorised and generates a log entry.
**Preparation:**
@@ -2223,8 +2223,9 @@ Verify that:
**Activities:**
1. Perform a rollback to a previous version.
2. Observe the emitted audit record.
1. Check that the user role to operate the rollback is authorised;
2. Login and perform a rollback to a previous version;
3. Observe the emitted audit record.
**Verdict:**
@@ -2241,7 +2242,7 @@ Verify that:
### 6.5.9 SU_UPDATES-9
**Objective:**Protect the availability of the product.
**Objective:**The product recovers after a failed update either to the operational, or a secure state that cannot be exploited.
**Preparation:**
@@ -2255,7 +2256,7 @@ Verify that:
**Verdict:**
1. Pass, if the system recovers to fully functional state.
1. Pass, if the system recovers to a functional operational or a secure state.
2. Fail otherwise.
**Supporting Evidence:**
@@ -2267,7 +2268,7 @@ Verify that:
### 6.5.10 SU_UPDATES-10
**Objective:**Product user have knowledge about the possibility to update.
**Objective:**The system user receives information when a product update is made available.
**Preparation:**
@@ -2280,7 +2281,7 @@ Verify that:
**Verdict:**
1. Pass, if the notification mechanism functions as expected.
1. Pass, if the notification mechanism functions as expected, which is either with on-product mechanism, or verify that there are direct manufacturer-to-system-user notifications on available updates
2. Fail otherwise.
**Supporting Evidence:**
@@ -2292,7 +2293,7 @@ Verify that:
### 6.5.11 SU_UPDATES-11
**Objective:**Product user has an understatement of what versions are installed.
**Objective:**The product can provide a list of the components it is constituted from and provide a list of the managed elements.
**Preparation:**
@@ -2301,8 +2302,8 @@ Verify that:
**Activities:**
1. Investigate the version information.
2. Cross-reference to technical documentation to understand the relevancy of the component.
1. Investigate the version information;
2. Cross‑reference the components to the technical documentation and identify which can be updated and are subject to versioning.
**Verdict:**
@@ -2318,7 +2319,7 @@ Verify that:
### 6.5.12 SU_UPDATES-12
**Objective:**Product user understand the status of the system.
**Objective:**The product user understands when the system is in update operation.
**Preparation:**
@@ -2344,7 +2345,7 @@ Verify that:
### 6.5.13 SU_UPDATES-13
**Objective:**Ensure the latest fixes are applied to the product.
**Objective:**The product operates with the latest available updates.
**Preparation:**
@@ -2354,7 +2355,8 @@ Verify that:
**Activities:**
1. Observe the automation performing the update.
1. Have an old version of the product initialised and available with the default configuration and required credentials;
2. Study the technical documentation and the logs.
**Verdict:**
@@ -2372,7 +2374,7 @@ Verify that:
### 6.5.14 SU_UPDATES-14
**Objective:**
**Objective:** If the product has automated update functionality, then is activated by default.
