@@ -1251,13 +1251,13 @@ Therefore, application of updates needs to be performed in a manner that maintai
***SU_UPDATES-4:** Authenticity and integrity of the update package shall be verifiable using a cryptographic signature verification prior to installation.
***SU_UPDATES-5:** The product shall maintain a monotonic version counter or equivalent mechanism to prevent installation of updates with an older version.
***SU_UPDATES-6:** The product shall provide a mechanism to restore the system to the operational state after a failed update.
***SU_UPDATES-7:** The product shall provide a way for the system user to postpone or re-schedule the application update.
The requirements **SU_UPDATES-8** to **13** are conditional due to different operative management and ownership models.
The requirements **SU_UPDATES-7** to **13** are conditional due to different operative management and ownership models.
A cellphone that is connected to a corporate inventory management often has its own update manager, and the device does not rely on the centralised control.
Similarly in a modern cluster deployment, the application can not update itself, as the control is in the cluster, which makes the provisioning, scheduling and network shaping decisions for all applications running in the same context.
***SU_UPDATES-7:** The product shall provide a way for the system user to postpone or re-schedule the application update if the operative environment makes it possible.
***SU_UPDATES-8:** If the product supports intentional version rollback, the invoking actions shall require explicit authorisation and an auditable event shall be emitted with related rollback metadata.
***SU_UPDATES-9:** The product shall automatically recover from a failed update and resume operation if applicable.
***SU_UPDATES-10:** The product shall inform the system user about update availability if applicable.
