<?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>BLE Connection security</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/100556/ble-connection-security</link><description>I have an application that allows for FOTA using the SMP Service. That all works fine. 
 But I&amp;#39;ve been asked &amp;quot;is the connection encrypted and secure?&amp;quot; 
 I&amp;#39;ve had a search through the DevZone but can&amp;#39;t really find a clear answer to: 
 1. Is the DFU via</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 09 Jun 2023 07:09:07 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/100556/ble-connection-security" /><item><title>RE: BLE Connection security</title><link>https://devzone.nordicsemi.com/thread/430121?ContentTypeID=1</link><pubDate>Fri, 09 Jun 2023 07:09:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1ae06015-6559-4183-bb16-275000b15485</guid><dc:creator>AHaug</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote user="AHaug"]This corresponds to my understanding as well, but I will ask with a colleague of mine when I get to the office tomorrow (Friday 9th) just to be sure we&amp;#39;re not missing any available options for your design.[/quote]
&lt;p&gt;I have discussed this item with a colleague of mine and I can confirm that your understanding is correct, and &amp;quot;Just works&amp;quot; is the only option with the configuration you mention. You could add a static passkey to your app, but that won&amp;#39;t do much for security other than ensuring that you connect to the correct device more easily.&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Andreas&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection security</title><link>https://devzone.nordicsemi.com/thread/430060?ContentTypeID=1</link><pubDate>Thu, 08 Jun 2023 18:03:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:925b4020-8602-4c4c-b3b3-b33c1b062ddd</guid><dc:creator>AHaug</dc:creator><description>&lt;p&gt;Hi Mike,&lt;/p&gt;
[quote user="Mike Austin (LPI)"]This&amp;nbsp;might seem like a dumb question, but how do I setup BLE connections in my device to require the Client to Pair?[/quote]
&lt;p&gt;No such thing as a dumb question, so no worries. The&lt;a href="https://academy.nordicsemi.com/courses/bluetooth-low-energy-fundamentals/"&gt; BLE fundamentals course at academy.nordicsemi.com&lt;/a&gt;&amp;nbsp;showcases both how to do this and some theory for how to do this. Spefically &lt;a href="https://academy.nordicsemi.com/lessons/lesson-3-bluetooth-le-connections/"&gt;lesson 3 &lt;/a&gt;takes you through the Connection process and &lt;a href="https://academy.nordicsemi.com/lessons/lesson-5-bluetooth-le-security-fundamentals/"&gt;lesson 5&lt;/a&gt; takes you through the pairing process&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I do believe that taking this course &lt;em&gt;should&amp;nbsp;&lt;/em&gt;answer your questions, but please feel free to ask follow up questions in case you still have any questions left unanswered after&amp;nbsp;having a look at the topics in the BLE course&lt;/p&gt;
[quote user="Mike Austin (LPI)"]We’ve implemented Private/Public key signing of the firmware, but as I understand it that will only prevent someone trying to put unauthorized firmware into our device. It won’t stop them “sniffing” the image file being sent across to our device and taking that. Is that correct?[/quote]
&lt;p&gt;Your understanding is 100% correct. There will be ways to get access to the firmware if you only do signing of the image, but signing the image stops a large portion of the malicious activities regarding getting access to the product.&amp;nbsp;&lt;/p&gt;
[quote user="Mike Austin (LPI)"]Our device has no user input or display method, so the only security we can implement is the Just Works option if I understand things correctly. Longer term we might look at OOB pairing with NFC.[/quote]
&lt;p&gt;This corresponds to my understanding as well, but I will ask with a colleague of mine when I get to the office tomorrow (Friday 9th) just to be sure we&amp;#39;re not missing any available options for your design.&lt;/p&gt;
&lt;p&gt;I&amp;#39;ll get back to you tomorrow regarding the last item&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Andreas&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection security</title><link>https://devzone.nordicsemi.com/thread/429858?ContentTypeID=1</link><pubDate>Wed, 07 Jun 2023 21:17:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6bbcc5d2-b560-4d69-9872-397b361d53e0</guid><dc:creator>Mike Austin (LPI)</dc:creator><description>&lt;p&gt;Thanks Andreas.&lt;/p&gt;
&lt;p&gt;This&amp;nbsp;might seem like a dumb question, but how do I setup BLE connections in my device to require the Client to Pair?&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ve implemented Private/Public key signing of the firmware, but as I understand it that will only prevent someone trying to put unauthorized firmware into our device. It won&amp;rsquo;t stop them &amp;ldquo;sniffing&amp;rdquo; the image file being sent across to our device and taking that. Is that correct?&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re probably not at the point where we are able to develop our own encryption/decryption solution just yet.&lt;/p&gt;
&lt;p&gt;Our device has no user input or display method, so the only security we can implement is the Just Works option if I understand things correctly. Longer term we might look at OOB pairing with NFC.&lt;/p&gt;
&lt;p&gt;Regatds,&lt;/p&gt;
&lt;p&gt;Mike&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection security</title><link>https://devzone.nordicsemi.com/thread/429787?ContentTypeID=1</link><pubDate>Wed, 07 Jun 2023 13:00:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:acccff51-b318-4111-b2cd-1be2fe6e4d81</guid><dc:creator>AHaug</dc:creator><description>&lt;p&gt;Hi Mike,&lt;/p&gt;
[quote user=""]1.&amp;nbsp; Is the DFU via SMP Service a secure, encypted connection by default?[/quote]
&lt;p&gt;The connection is not encrypted&lt;span&gt;&amp;nbsp;&lt;/span&gt;by default unless you pair/bond the devices. If the case is that the devices are paired, then the BLE link is encrypted&lt;/p&gt;
&lt;p&gt;Regarding 2. and 3. I need to know a bit more about what your goals are regarding the encryption&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;If your aim is to tamperproof your DFU-procedure, I would recommend you to have a look at how to sign the firmware. This will ensure that any firmware that has been tampered with will be revoked in the DFU procedure&lt;/li&gt;
&lt;li&gt;If your aim is to perform encrypted DFU, then we unfortunately don&amp;#39;t have support for this and you will have to create your own proprietary solution&amp;nbsp;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Let me know if this answers your questions and feel free to ask follow up questions regarding this topic&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Andreas&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>