<?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>The Bluetooth connection of the nRF52832 module encounters a DoS attack</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/94019/the-bluetooth-connection-of-the-nrf52832-module-encounters-a-dos-attack</link><description>Hello, 
 When using two nRF52832 modules for Bluetooth connection, can it prevent Dos attack program? We have found a situation where a malfunctioning or malicious client could perform a DoS attack on the nRF52832 pre-programmed firmware by doing the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 18 Nov 2022 14:33:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/94019/the-bluetooth-connection-of-the-nrf52832-module-encounters-a-dos-attack" /><item><title>RE: The Bluetooth connection of the nRF52832 module encounters a DoS attack</title><link>https://devzone.nordicsemi.com/thread/396447?ContentTypeID=1</link><pubDate>Fri, 18 Nov 2022 14:33:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:81cc90d2-0812-4382-b618-b51966aa56dc</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;DoS attacks isn&amp;#39;t a really common term in Bluetooth Low Energy, but I understand what you mean (I think).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In BLE we have something called pairing and bonding. Pairing is the encryption of the connection, while bonding is storing these encryption keys for later. When you bond you can use something called whitelisting when you advertise, meaning the peripheral will only allow connections from that specific device.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Strictly speaking, a malicious client could pretend to be the bonded device, and try to connect, but when it turns out that it doesn&amp;#39;t have the correct encryption keys, the device will automatically disconnect.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;To see how this is done, you can have a look at the SDK\examples\ble_peripheral\ble_app_hrs.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>