Skip to content

Commit d5f1e22

Browse files
greg-ferrlubos
authored andcommitted
doc: tfm: disabling ITS
Removed dependency on ITS for CONFIG_TFM_PARTITION_CRYPTO. Updated documentation where required to mention KMU as an alternative. NCSDK-35016. Signed-off-by: Grzegorz Ferenc <[email protected]>
1 parent c8d2338 commit d5f1e22

File tree

4 files changed

+18
-8
lines changed

4 files changed

+18
-8
lines changed

doc/nrf/app_dev/device_guides/nrf54l/kmu_basics.rst

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,10 @@ This feature is crucial not only for private keys but also for public keys, as t
1616
Even when keys must pass through addressable RAM, the KMU significantly reduces the risk of key exposure.
1717
Therefore, you should use KMU for managing secrets whenever possible.
1818

19+
When using an nRF54L device with Trusted Firmware-M, you can use the KMU to store keys instead of using the :ref:`ug_tfm_services_its`.
20+
For this to work, you need to enable the :ref:`tfm_partition_crypto` service, which enables the :ref:`ug_tfm_services_its` service by default.
21+
You can then manually disable the ITS service and start using KMU instead.
22+
1923
Key Types
2024
*********
2125

doc/nrf/security/key_storage.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Key generation and import
5353
Keys can have one of the following lifetimes:
5454

5555
* Volatile - Stored in RAM, lost on reset.
56-
* Persistent - Stored in PSA Internal Trusted Storage, retained during reboots.
56+
* Persistent - Stored in PSA Internal Trusted Storage or Key Management Unit, retained during reboots.
5757

5858
The PSA Crypto API supports two methods for using keys:
5959

@@ -129,7 +129,7 @@ For an example of how to derive keys from HUKs, see the :ref:`Hardware unique ke
129129
Key Management Unit (KMU)
130130
=========================
131131

132-
The Key Management Unit (KMU) is a hardware peripheral for secure key storage available on select nRF devices.
132+
The Key Management Unit (KMU) is a hardware peripheral for secure key storage available on select Nordic Semiconductor devices.
133133
It provides hardware-level protection for cryptographic keys.
134134

135135
This option offers the following features:

doc/nrf/security/tfm/tfm_building.rst

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -114,23 +114,23 @@ Following are the available Kconfig options for TF-M partitions:
114114
- Default value
115115
- Dependencies
116116
* - :kconfig:option:`CONFIG_TFM_PARTITION_PLATFORM`
117-
- Provides platform services.
117+
- Provides :ref:`ug_tfm_services_platform`.
118118
- Enabled
119119
-
120120
* - :kconfig:option:`CONFIG_TFM_PARTITION_CRYPTO`
121-
- Provides cryptographic services.
121+
- Provides :ref:`tfm_partition_crypto`.
122122
- Enabled
123-
- INTERNAL_TRUSTED_STORAGE
123+
-
124124
* - :kconfig:option:`CONFIG_TFM_PARTITION_PROTECTED_STORAGE`
125-
- Provides secure storage services.
125+
- Provides :ref:`tfm_partition_ps`.
126126
- Enabled
127127
- PLATFORM, CRYPTO
128128
* - :kconfig:option:`CONFIG_TFM_PARTITION_INTERNAL_TRUSTED_STORAGE`
129-
- Provides internal trusted storage services.
129+
- Provides :ref:`ug_tfm_services_its`.
130130
- Enabled
131131
-
132132
* - :kconfig:option:`CONFIG_TFM_PARTITION_INITIAL_ATTESTATION`
133-
- Provides initial attestation services.
133+
- Provides :ref:`ug_tfm_services_initial_attestation`.
134134
- Disabled
135135
- CRYPTO
136136

doc/nrf/security/tfm/tfm_services.rst

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,9 @@ ITS is meant to be used by other TF-M partitions.
5050
It must not be accessed directly by a user application :ref:`placed in the Non-Secure Processing Environment <app_boards_spe_nspe_cpuapp_ns>`.
5151
If you want the user application to access the contents of the partition, use the :ref:`tfm_partition_ps`.
5252

53+
This service is enabled as the default storage mechanism when you enable the :ref:`tfm_partition_crypto` service.
54+
If you are using a device with the :ref:`key_storage_kmu`, you can disable the :ref:`ug_tfm_services_its` and start using KMU instead to save memory.
55+
5356
For more information about the general features of the TF-M ITS service, see `TF-M ITS`_.
5457

5558
.. _tfm_encrypted_its:
@@ -140,6 +143,9 @@ These will enable the required ``CONFIG_TFM_CRYPTO_*`` Kconfig options.
140143

141144
TF-M uses :ref:`hardware unique keys <lib_hw_unique_key>` when the PSA Crypto key derivation APIs are used, and ``psa_key_derivation_setup`` is called with the algorithm ``TFM_CRYPTO_ALG_HUK_DERIVATION``.
142145

146+
When enabled, the Crypto service by default uses the :ref:`ug_tfm_services_its` to store the keys and other sensitive data.
147+
If you are using a device with the :ref:`key_storage_kmu`, you can disable the :ref:`ug_tfm_services_its` and start using KMU instead to save memory.
148+
143149
For more information about the general features of the Crypto partition, see `TF-M Crypto`_.
144150

145151
.. _tfm_partition_ps:

0 commit comments

Comments
 (0)