Lines Matching +full:write +full:- +full:protected

7 …`Platform Security Architecture (PSA) Secure Storage API <https://arm-software.github.io/psa-api/s…
15 non-volatile memory support.
19 cannot enable the subsystem because TF-M already provides an implementation of the API.
22   device-specific security features and the configuration, the subsystem
24 | Keep in mind, however, that it's preferable to use a secure processing environment like TF-M when
39   This depends on device-specific security features and the configuration.
41 * does not yet provide an implementation of the Protected Storage (PS) API as of this writing.
44   (unless a `custom implementation <#whole-api>`_ of the PS API is provided).
50 …rage requirements <https://arm-software.github.io/psa-api/storage/1.0/overview/requirements.html#i…
53     ``implicitly confidential and protected from replay``
54 …ted Storage API <https://arm-software.github.io/psa-api/storage/1.0/overview/architecture.html#the…
55     because ``most embedded microprocessors (MCU) have on-chip flash storage that can be made
57 …2.2. Technical Background <https://arm-software.github.io/psa-api/storage/1.0/overview/architectur…
61   because this depends on device-specific security features and the configuration.
65   In addition, the data stored in the ITS is not protected against replay attacks,
66   because this requires storage that is protected by hardware.
68 * The data stored via the PSA Secure Storage API is not protected from direct
69   read/write by software or debugging. (Against ``2.`` and ``10.`` in
70 …rage requirements <https://arm-software.github.io/psa-api/storage/1.0/overview/requirements.html#i…
113 * :zephyr:code-sample:`persistent_key`
114 * :zephyr:code-sample:`psa_its`