<?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>topic How can we protect the data over the interface between the EdgeLock SE050 and the host MCU?  in Secure Authentication</title>
    <link>https://community.nxp.com/t5/Secure-Authentication/How-can-we-protect-the-data-over-the-interface-between-the/m-p/981223#M150</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="margin-left: .25in;"&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;The EdgeLock SE050 supports SCP03 or FastSCP secure channel protocols. An SCP03 session is a secure channel based on AES cryptography while a FastSCP session is based on ECC cryptography.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 29 Oct 2019 14:30:46 GMT</pubDate>
    <dc:creator>jordijofrenxp</dc:creator>
    <dc:date>2019-10-29T14:30:46Z</dc:date>
    <item>
      <title>How can we protect the data over the interface between the EdgeLock SE050 and the host MCU?</title>
      <link>https://community.nxp.com/t5/Secure-Authentication/How-can-we-protect-the-data-over-the-interface-between-the/m-p/981223#M150</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="margin-left: .25in;"&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;The EdgeLock SE050 supports SCP03 or FastSCP secure channel protocols. An SCP03 session is a secure channel based on AES cryptography while a FastSCP session is based on ECC cryptography.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Oct 2019 14:30:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Secure-Authentication/How-can-we-protect-the-data-over-the-interface-between-the/m-p/981223#M150</guid>
      <dc:creator>jordijofrenxp</dc:creator>
      <dc:date>2019-10-29T14:30:46Z</dc:date>
    </item>
  </channel>
</rss>

