* Screenshots, captures, or console outputs confirming the correct execution or protection behaviour;
* Logs, configuration files, or audit traces demonstrating the implementation of the requirement.
### 6.5.14 SU_UPDATES-15
**Objective:** The update process doesn't decrease the availability of the product.
**Preparation:**
1. Have the product initialised and available with the default configuration and required credentials.
2. Study the technical documentation.
**Activities:**
1. Investigate the update functionality.
2. Test the update.
**Verdict:**
1. Pass, if the update strategy used is expected to finish succesfully without impacting the availability of the product,
2. and, if the update of a layer defined in [4.3.2 Physical/Hardware environment](#432-physicalhardware-environment) doesn't impact the availability of the product.
3. Fail otherwise.
**Supporting Evidence:**
* Relevant vendor or design documentation describing the applied measures;
* Test reports showing the steps performed and results obtained;
* Screenshots, captures, or console outputs confirming the correct execution or protection behaviour;
* Logs, configuration files, or audit traces demonstrating the implementation of the requirement.
### 6.5.14 SU_UPDATES-16
**Objective:** The update is pushed automatically to a managed element, when that funcitonality is available.
**Preparation:**
1. Have the product initialised and available with the default configuration and required credentials.
2. Have a managed element initialised and available with the previous software version installed.
3. Study the technical documentation.
**Activities:**
1. Investigate the configuration options.
2. Activate the element update if needed.
**Verdict:**
1. Pass, if update happens without user interaction.
2. Fail otherwise.
**Supporting Evidence:**
* Relevant vendor or design documentation describing the applied measures;
* Test reports showing the steps performed and results obtained;
* Screenshots, captures, or console outputs confirming the correct execution or protection behaviour;
* Logs, configuration files, or audit traces demonstrating the implementation of the requirement.
