https://devzone.nordicsemi.com/f/nordic-q-a/4512/secure-connection-other-than-just-bondinghiii.... i am developing a custom profile with five services... i want to make these 5 services and its characteristics available only for some authorized devices.. ie, whenever a device want to connect with our device it should know the security keyen-USTelligent Community 13Sat, 31 Oct 2015 07:43:02 GMThttps://devzone.nordicsemi.com/thread/16007?ContentTypeID=1Sat, 31 Oct 2015 07:43:02 GMT137ad170-7792-4731-bb38-c0d22fbe4515:4cb9ae11-ee13-45e4-8402-d72e92ab2fd3vineeshvs<p>@sruthiraj: Hi, did you try out the above suggestions. Could you post the results.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/16006?ContentTypeID=1Wed, 19 Nov 2014 12:42:57 GMT137ad170-7792-4731-bb38-c0d22fbe4515:4f0ba0f6-b664-46eb-8ed1-4fc125ba1edbAsbj&#248;rn<p>I suggest you have use the functionality related to white listing in the Bluetooth core spec. 4.1, volume 6, part B, chapter 4.3. The functions are defined in ble_gap.h <a href="http://developer.nordicsemi.com/nRF51_SDK/doc/7.0.1/s110/html/a00807.html#gac37d0158c7458cb4250f9bdfba593858">and information found here.</a></p> <p>It basically enables you to filter who&#39;s allowed to receive responses on scan_req and who&#39;s allowed to connect.</p> <p>You might also have a benefit from reading other posts here on DevZone regarding implementing white lists and perhaps this post here: <a href="https://devzone.nordicsemi.com/question/1622/how-to-connect-to-one-specific-master/">devzone.nordicsemi.com/.../</a></p><div style="clear:both;"></div>