<?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>Limiting Access via Bluetooth</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/121360/limiting-access-via-bluetooth</link><description>I have a greenfield project that I am currently working on and I am trying to work out the best approach to limiting access/features via Bluetooth. 
 In the past we have used Just Works, anyone can connect and do anything they like. We had a way of setting</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 12 May 2025 13:39:01 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/121360/limiting-access-via-bluetooth" /><item><title>RE: Limiting Access via Bluetooth</title><link>https://devzone.nordicsemi.com/thread/534918?ContentTypeID=1</link><pubDate>Mon, 12 May 2025 13:39:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4fa4956a-da2d-4343-ae1d-ac1e547d2322</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Pairing/bonding is done on a per device basis to secure the link between the two pairs. From what I understand, you need a way for the nRF device to know that it is communicating with a device tha had your app? If so, perhaps the pairing (just owrks or a higher level) should be used only for securign the link, and then you additionally have an extra application specific authentication method (some form of challenge-response mechanism, perhaps)? This could be implemented in the application layer, independent of the Bluetooth stack.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>