<?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>Bluetooth Security</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/123393/bluetooth-security</link><description>Hello Nordic Team, We are developing a wearable health device using the nRF5340-DK and Zephyr RTOS. As part of the BLE communication design, we intend to use **Security Level 2 (Encryption without MITM protection)** due to the user experience constraints</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 12 Aug 2025 14:01:52 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/123393/bluetooth-security" /><item><title>RE: Bluetooth Security</title><link>https://devzone.nordicsemi.com/thread/545394?ContentTypeID=1</link><pubDate>Tue, 12 Aug 2025 14:01:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d4803855-68d4-47f0-a4b3-e0964bf16409</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Try to erase all or recover the board before programming, and turn off and on BLE on the iOS.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth Security</title><link>https://devzone.nordicsemi.com/thread/545297?ContentTypeID=1</link><pubDate>Tue, 12 Aug 2025 05:49:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e6b622be-924a-40a7-8c7c-260d2ccba3aa</guid><dc:creator>mehmetefe</dc:creator><description>&lt;p&gt;&lt;span class="HwtZe" lang="en"&gt;&lt;span class="jCAhz ChMk0b"&gt;&lt;span class="ryNqvb"&gt;Hello Amanda, &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="HwtZe" lang="en"&gt;&lt;span class="jCAhz ChMk0b"&gt;&lt;span class="ryNqvb"&gt;Thank you for your reply.&lt;/span&gt;&lt;/span&gt;&lt;span class="jCAhz ChMk0b"&gt;&lt;span class="ryNqvb"&gt; &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="HwtZe" lang="en"&gt;&lt;span class="jCAhz ChMk0b"&gt;&lt;span class="ryNqvb"&gt;We implemented our project based on your suggestions.&lt;/span&gt;&lt;/span&gt; &lt;span class="jCAhz ChMk0b"&gt;&lt;span class="ryNqvb"&gt;However, we encountered another problem.&lt;/span&gt;&lt;/span&gt; &lt;span class="jCAhz ChMk0b"&gt;&lt;span class="ryNqvb"&gt;Our problem is that when connecting to Bluetooth on iOS devices, the pairing request doesn&amp;#39;t appear.&lt;/span&gt;&lt;/span&gt; &lt;span class="jCAhz ChMk0b"&gt;&lt;span class="ryNqvb"&gt;On Android devices, the Bluetooth connection is established, and then the Android device sends us a pairing request.&lt;/span&gt;&lt;/span&gt; &lt;span class="jCAhz ChMk0b"&gt;&lt;span class="ryNqvb"&gt;When we accept this request, the service opens.&lt;/span&gt;&lt;/span&gt;&lt;span class="jCAhz ChMk0b"&gt;&lt;span class="ryNqvb"&gt; &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="HwtZe" lang="en"&gt;&lt;span class="jCAhz ChMk0b"&gt;&lt;span class="ryNqvb"&gt;My research revealed that there&amp;#39;s no specific solution.&lt;/span&gt;&lt;/span&gt;&lt;span class="jCAhz ChMk0b"&gt;&lt;span class="ryNqvb"&gt; Do you have any solutions or resources you can recommend for this issue?&lt;/span&gt;&lt;/span&gt;&lt;span class="jCAhz ChMk0b"&gt;&lt;span class="ryNqvb"&gt; &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="HwtZe" lang="en"&gt;&lt;span class="jCAhz ChMk0b"&gt;&lt;span class="ryNqvb"&gt;Thank you very much for your time and support.&lt;/span&gt;&lt;/span&gt;&lt;span class="jCAhz ChMk0b"&gt;&lt;span class="ryNqvb"&gt; &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="HwtZe" lang="en"&gt;&lt;span class="jCAhz ChMk0b"&gt;&lt;span class="ryNqvb"&gt;Best wishes, &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class="HwtZe" lang="en"&gt;&lt;span class="jCAhz ChMk0b"&gt;&lt;span class="ryNqvb"&gt;Mehmet Efe&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth Security</title><link>https://devzone.nordicsemi.com/thread/545219?ContentTypeID=1</link><pubDate>Mon, 11 Aug 2025 13:16:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:66e7f3e9-fcfe-4c8f-857c-a21bb131d194</guid><dc:creator>Amanda Hsieh</dc:creator><description>[quote user="mehmetefe"]Whether &lt;strong&gt;Security Level 2 is considered sufficient&lt;/strong&gt; for production-grade wearable devices (e.g., fitness bands) without user interaction.[/quote]
&lt;p&gt;&lt;span&gt;You should do a threat model for your use case to answer this question. On the technical side, you should enable LESC only mode. That should be the default on the latest NCS. Check BT_SMP_SC_PAIR_ONLY config. Without OOB or IO capabilities, it would still land on level 2; however, it protects against eavesdropper attack, unlike legacy pairing, which should not be used.&lt;/span&gt;&lt;/p&gt;
[quote user="mehmetefe"]Suggestions regarding &lt;strong&gt;TRNG (True Random Number Generator)&lt;/strong&gt; usage in BLE pairing/bonding.[/quote]
&lt;p&gt;For the nRF5340 CPUAPP, we only have the option to get PRNG seeded by TRNG via CryptoCell on-device.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If&amp;nbsp;you use code in the CPUAPP that requires RNG, then it will be default enabled&lt;/p&gt;
[quote user="mehmetefe"]&lt;strong&gt;Best practices&lt;/strong&gt; for bonding and key storage when using Zephyr with the nRF5340.[/quote]
&lt;p&gt;Check out&amp;nbsp;&lt;a href="https://academy.nordicsemi.com/courses/bluetooth-low-energy-fundamentals/lessons/lesson-5-bluetooth-le-security-fundamentals/topic/blefund-lesson-5-exercise-2/"&gt;https://academy.nordicsemi.com/courses/bluetooth-low-energy-fundamentals/lessons/lesson-5-bluetooth-le-security-fundamentals/topic/blefund-lesson-5-exercise-2/&lt;/a&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth Security</title><link>https://devzone.nordicsemi.com/thread/544409?ContentTypeID=1</link><pubDate>Mon, 04 Aug 2025 05:55:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bac7504a-f7e5-4329-9b7c-bdc6d3acb049</guid><dc:creator>mehmetefe</dc:creator><description>&lt;p data-start="1110" data-end="1120"&gt;Hi Amanda,&lt;/p&gt;
&lt;p data-start="1122" data-end="1150"&gt;Thank you for your response.&lt;/p&gt;
&lt;p data-start="1152" data-end="1392"&gt;I&amp;rsquo;ve reviewed Lesson 5 and all related links you mentioned in detail. However, the provided materials don&amp;#39;t fully address our specific use case: a &lt;strong data-start="1299" data-end="1391"&gt;displayless wearable device using nRF5340 and Security Level 2 (encryption without MITM)&lt;/strong&gt;.&lt;/p&gt;
&lt;p data-start="1394" data-end="1496"&gt;We would greatly appreciate further clarification or official recommendations on the following topics:&lt;/p&gt;
&lt;ol data-start="1498" data-end="1821"&gt;
&lt;li data-start="1498" data-end="1640"&gt;
&lt;p data-start="1501" data-end="1640"&gt;Whether &lt;strong data-start="1509" data-end="1554"&gt;Security Level 2 is considered sufficient&lt;/strong&gt; for production-grade wearable devices (e.g., fitness bands) without user interaction.&lt;/p&gt;
&lt;/li&gt;
&lt;li data-start="1641" data-end="1735"&gt;
&lt;p data-start="1644" data-end="1735"&gt;Suggestions regarding &lt;strong data-start="1666" data-end="1705"&gt;TRNG (True Random Number Generator)&lt;/strong&gt; usage in BLE pairing/bonding.&lt;/p&gt;
&lt;/li&gt;
&lt;li data-start="1736" data-end="1821"&gt;
&lt;p data-start="1739" data-end="1821"&gt;&lt;strong data-start="1739" data-end="1757"&gt;Best practices&lt;/strong&gt; for bonding and key storage when using Zephyr with the nRF5340.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p data-start="1823" data-end="1954"&gt;Our goal is to balance &lt;strong data-start="1846" data-end="1878"&gt;user experience and security&lt;/strong&gt;, and we&amp;rsquo;re seeking Nordic&amp;#39;s official guidance for this particular scenario.&lt;/p&gt;
&lt;p data-start="1956" data-end="2002"&gt;Thank you very much for your time and support.&lt;/p&gt;
&lt;p data-start="2004" data-end="2035"&gt;Best regards,&lt;br data-start="2017" data-end="2020" /&gt; Mehmet Efe &amp;Ouml;ten&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth Security</title><link>https://devzone.nordicsemi.com/thread/544344?ContentTypeID=1</link><pubDate>Fri, 01 Aug 2025 13:37:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6df8327f-f9de-4f6f-8ce2-2c01dc2fe45c</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Check out this course&amp;nbsp;&lt;a href="https://academy.nordicsemi.com/courses/bluetooth-low-energy-fundamentals/lessons/lesson-5-bluetooth-le-security-fundamentals/"&gt;Lesson 5 – Security in Bluetooth LE communication&lt;/a&gt;&amp;nbsp;and its exercises.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Amanda H.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>