@@ -1268,7 +1268,7 @@ Similarly in a modern cluster deployment, the application can not update itself,
***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-9:** The product shall automatically recover from a failed update, resume operation if applicable or else achieve a secure state.
***SU_UPDATES-10:** The product shall inform the system user about update availability if applicable.
***SU_UPDATES-11:** The product shall track the relevant component versions of the product and the managed elements if applicable.
***SU_UPDATES-12:** The product shall log start and finish of the update download if applicable.
@@ -1408,7 +1408,7 @@ This clause addresses the requirements in the CRA [\[i.1\]](#_ref_i.1) Annex 1 P
***INT_ROTATE-1** The product shall support and implement an on-demand rotation of cryptographic keys.
***INT_ROTATE-2** The product shall support the initialisation of trust with the managed elements.
***INT_ROTATE-3** The product shall not trust expired keys.
***INT_ROTATE-3** The product shall not trust expired secrets.
Trust is inherited from a parenting system or from an existing entity.
Rollout automation and zero touch configuration approaches rely on concepts, which are not necessarily well established, and vendor specific.
