<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Shared Secret Key provisioning on the nRF5340, Options</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/112721/shared-secret-key-provisioning-on-the-nrf5340-options</link><description>Hey All, 
 We are working on a product based on the nRF5340. We will be using symmetric key authentication(HMAC) and was wondering the best way to go about provisioning the secret key. I&amp;#39;ve seen that there&amp;#39;s a psa_set_key_lifetime api to set the key as</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 19 Sep 2024 17:08:38 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/112721/shared-secret-key-provisioning-on-the-nrf5340-options" /><item><title>RE: Shared Secret Key provisioning on the nRF5340, Options</title><link>https://devzone.nordicsemi.com/thread/503165?ContentTypeID=1</link><pubDate>Thu, 19 Sep 2024 17:08:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:541f9167-114c-4a95-9b96-1e51921f9c4e</guid><dc:creator>kartsiv</dc:creator><description>&lt;p&gt;Hi Hieu,&lt;/p&gt;
&lt;p&gt;Is there any technical limitation in storing a HMAC key in the KMU and pushing it over the secure APB interface to the CryptoCell?&lt;/p&gt;
&lt;p&gt;Arguably, this offers better security guarantees than using TF-M ITS Encrypted storage, because with KMU + secure APB, the key is never&amp;nbsp;exposed to the CPU.&lt;/p&gt;
&lt;p&gt;References:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/nrfconnect/sdk-nrfxlib/blob/main/crypto/nrf_cc312_platform/include/nrf_cc3xx_platform_kmu.h#L80"&gt;https://github.com/nrfconnect/sdk-nrfxlib/blob/main/crypto/nrf_cc312_platform/include/nrf_cc3xx_platform_kmu.h#L80&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/nrfconnect/sdk-trusted-firmware-m/blob/main/platform/ext/target/nordic_nrf/common/core/tfm_hal_its_encryption.c#L252"&gt;https://github.com/nrfconnect/sdk-trusted-firmware-m/blob/main/platform/ext/target/nordic_nrf/common/core/tfm_hal_its_encryption.c#L252&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Shared Secret Key provisioning on the nRF5340, Options</title><link>https://devzone.nordicsemi.com/thread/492919?ContentTypeID=1</link><pubDate>Tue, 09 Jul 2024 09:46:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f6a7e9d3-5188-4163-930d-3c897cf2ca1e</guid><dc:creator>Hieu</dc:creator><description>&lt;p&gt;Hi neo_here,&lt;/p&gt;
&lt;p&gt;Yes, you can import the key and use it later with PSA Crypto API. It is certainly one good way to go.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Shared Secret Key provisioning on the nRF5340, Options</title><link>https://devzone.nordicsemi.com/thread/492845?ContentTypeID=1</link><pubDate>Tue, 09 Jul 2024 02:35:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0245a78c-dddd-44e1-9fa3-d203973a53a9</guid><dc:creator>neo_here</dc:creator><description>&lt;p&gt;Hi Hieu, &lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks for the blog, I went through it and seems like PSA Crypto API are the way to go and I would like to avoid using the KMU directly. &lt;br /&gt;&lt;br /&gt;But since we are going to import a key once and not generate it, Is using the secure storage API to store the Key handle the way to go ? &lt;br /&gt;&lt;br /&gt;1) Use the PSA Crypto Import key API and import the key as persistent key&lt;/p&gt;
&lt;p&gt;2) Store the Key handle in persistent storage with Secure Storage&lt;br /&gt;&lt;br /&gt;3) Load the keyhandle from persistent storage subsequently throughout the lifecycle of the device or until it is reprovisioned&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Shared Secret Key provisioning on the nRF5340, Options</title><link>https://devzone.nordicsemi.com/thread/492491?ContentTypeID=1</link><pubDate>Fri, 05 Jul 2024 14:27:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5780fa16-5bb5-470b-ba80-fbbf4fc19426</guid><dc:creator>Hieu</dc:creator><description>&lt;p&gt;Hi neo_here,&lt;/p&gt;
&lt;p&gt;My colleague wrote a blog, with a section discussing different storage of keys.&amp;nbsp;Please give it a read:&lt;br /&gt;&lt;a href="https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/persistent-storage-of-keys-and-data-using-the-nrf-connect-sdk#Storage-alternatives-for-keys"&gt;https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/persistent-storage-of-keys-and-data-using-the-nrf-connect-sdk#Storage-alternatives-for-keys&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Hieu&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Best way to go about Symmetric Key Auth Provisioning</title><link>https://devzone.nordicsemi.com/thread/492140?ContentTypeID=1</link><pubDate>Wed, 03 Jul 2024 22:50:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:66d03a67-6abc-49e0-9189-d6058098f445</guid><dc:creator>neo_here</dc:creator><description>&lt;p&gt;To add on to the original post, this secret key provisioning is going to happen as a post manufacturing step.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>