<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Secure Authenticationのトピックprotect firmware code in target hardware</title>
    <link>https://community.nxp.com/t5/Secure-Authentication/protect-firmware-code-in-target-hardware/m-p/1092483#M327</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, how could SE050 possibly contribute to a concept to prevent firmware from being hacked during and after a remote update process?&lt;/P&gt;&lt;P&gt;Our question in detail: During firmware remote data transfer the firmware code is protected by TLS. However, finaly the firmware sits as a de-crypted binary in the NAND or NOR Flash. The identified risk is that this NAND or NOR could be sniffed or the memory hardware component could be extracted from the PCB and put in a spy hardware environment.&lt;BR /&gt;Thank you ! Best regards, Bernd&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 13 Jul 2020 09:14:29 GMT</pubDate>
    <dc:creator>bscheuffele</dc:creator>
    <dc:date>2020-07-13T09:14:29Z</dc:date>
    <item>
      <title>protect firmware code in target hardware</title>
      <link>https://community.nxp.com/t5/Secure-Authentication/protect-firmware-code-in-target-hardware/m-p/1092483#M327</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, how could SE050 possibly contribute to a concept to prevent firmware from being hacked during and after a remote update process?&lt;/P&gt;&lt;P&gt;Our question in detail: During firmware remote data transfer the firmware code is protected by TLS. However, finaly the firmware sits as a de-crypted binary in the NAND or NOR Flash. The identified risk is that this NAND or NOR could be sniffed or the memory hardware component could be extracted from the PCB and put in a spy hardware environment.&lt;BR /&gt;Thank you ! Best regards, Bernd&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Jul 2020 09:14:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Secure-Authentication/protect-firmware-code-in-target-hardware/m-p/1092483#M327</guid>
      <dc:creator>bscheuffele</dc:creator>
      <dc:date>2020-07-13T09:14:29Z</dc:date>
    </item>
    <item>
      <title>Re: protect firmware code in target hardware</title>
      <link>https://community.nxp.com/t5/Secure-Authentication/protect-firmware-code-in-target-hardware/m-p/1092484#M328</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Bernd,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the binary is plain in the NAND or NOR flash, I think SE050 can help little on such kind of issue, instead a tamper detection device is needed for your case. As I know, some host controllers support tamper detection,&amp;nbsp;for example, Kinetis K81,&amp;nbsp;&lt;BR /&gt;Please kindly refer to&amp;nbsp;&lt;A class="link-titled" href="https://www.nxp.com/products/processors-and-microcontrollers/arm-microcontrollers/general-purpose-mcus/k-series-cortex-m4/k8x-secure/kinetis-k81-150-mhz-hw-cryptographic-co-processor-anti-tamper-quadspi-microcontrollers-mcus-based-on-arm-cortex-m4-core:K81_150" title="https://www.nxp.com/products/processors-and-microcontrollers/arm-microcontrollers/general-purpose-mcus/k-series-cortex-m4/k8x-secure/kinetis-k81-150-mhz-hw-cryptographic-co-processor-anti-tamper-quadspi-microcontrollers-mcus-based-on-arm-cortex-m4-core:K81_150"&gt;Arm® Cortex®-M4|Kinetis K81 150 MHz 32-bit MCUs | NXP&lt;/A&gt;&amp;nbsp;for details.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;Kan&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;BR /&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt;Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Jul 2020 04:49:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Secure-Authentication/protect-firmware-code-in-target-hardware/m-p/1092484#M328</guid>
      <dc:creator>Kan_Li</dc:creator>
      <dc:date>2020-07-14T04:49:15Z</dc:date>
    </item>
  </channel>
</rss>

