Product state

Coming soon

1. What is product lifecycle

PRODUCT Lifecycle is used to control the product security configuration. It allows to control the activation of the platform’s security mechanisms.

1.1. New product lifecycle

We are introducing a new PRODUCT Lifecycle, in order to allow more flexibilities on product manufacturing and maintenance.

The new PRODUCT Lifecycle considers different phases using the product.

The considered phases are:

- development phase, offering all debug allowed to developer.

- provisioning phase, where main assets area become protected (no more accessible) …

- final phase, where the product is considered in the field.

- maintenance phase: field return management.

During all product life, the solution must guarantee that ROT and user assets are never disclosed.

This must be true for development, provisioning, final phase, and field return phases.

The new product Lifecycle propose the below product states:

- Open

- Provisioning

- iROT-Provisioned

- TZ-Closed (optional: only when TrustZone is supported)

- Closed or Locked

The goal of this document is to provide details on the different lifecycle states.

Warning: The Debug Authentication configuration (DA-config) must be provisioned in Provisioning state.

1.2. Up to 3 third parties

In the development and provisioning phases, the product Lifecycle allows to consider the product being developed by up to 3 third parties.

Different third parties means that for development and provisioning, we are able to set the product in a state that's allow to protect (isolate) the different parties.

The Lifecycle allows to consider up to 3 different third parties (iROT + TZ-Application + NS Application) for development and Provisioning.

Up to 3 parties

Distribution models

Initial Provisioning

File:ToCompleteInitialProvisioning.png