https://devzone.nordicsemi.com/f/nordic-q-a/39369/best-place-to-lock-debugging-interface-swd-using-approtectHello All I&#39;m trying to lock debugging/reading capability in my code. My system consists of a bootloader and an application beside the Softdevice and MBR. What is already done is to check and change APPROTECT as the first thing in the main functionen-USTelligent Community 13Thu, 11 Oct 2018 10:05:21 GMThttps://devzone.nordicsemi.com/thread/152458?ContentTypeID=1Thu, 11 Oct 2018 10:05:21 GMT137ad170-7792-4731-bb38-c0d22fbe4515:994b004e-f685-453a-a575-d71cca8795a3Yahya Tawil<p>Tahnks for the answer. Got it.&nbsp;</p> <p></p> <p>Yes, we are working on an encrypted DFU process.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/152456?ContentTypeID=1Thu, 11 Oct 2018 09:55:53 GMT137ad170-7792-4731-bb38-c0d22fbe4515:56f5ebdf-e7d5-42ee-9b3d-e413f8ee6a3eTurbo J<p>Simply don&#39;t use mass erase in the firmware update process. There is no need to touch UICR during an upgrade.</p> <p>Note that unless your firmware upgrade file is properly encryped (not easy), the attacker has everything in his hands already.</p><div style="clear:both;"></div>