<?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 Re: S32K144 SecOC Implementation - Freshness Value Manager and Anti-Replay Solutio in S32K</title>
    <link>https://community.nxp.com/t5/S32K/S32K144-SecOC-Implementation-Freshness-Value-Manager-and-Anti/m-p/2302247#M56418</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/257154"&gt;@Kishore_14&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You don’t need anything special for SecOC. As long as the hardware can do AES‑128 CMAC, it’s sufficient. That’s the only crypto primitive SecOC actually uses. CSEc (SHE‑based) on the S32K is fully enough - it gives you HW‑accelerated AES‑CMAC and protected key slots, which is exactly what SecOC needs.&lt;/P&gt;
&lt;P&gt;All the other CSEc features (secure boot MAC, key derivation, random number, etc.) is nice to have but SecOC doesn’t depend on it. Freshness values and anti‑replay counters are handled completely in software by the FVM. Hardware doesn’t provide any special counter for this. CSEc provides only features given by SHE specification.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
    <pubDate>Wed, 28 Jan 2026 12:23:14 GMT</pubDate>
    <dc:creator>lukaszadrapa</dc:creator>
    <dc:date>2026-01-28T12:23:14Z</dc:date>
    <item>
      <title>S32K144 SecOC Implementation - Freshness Value Manager and Anti-Replay Solutio</title>
      <link>https://community.nxp.com/t5/S32K/S32K144-SecOC-Implementation-Freshness-Value-Manager-and-Anti/m-p/2301822#M56409</link>
      <description>&lt;P&gt;Hardware: S32K144EVB&lt;BR /&gt;Current Setup: CSEc module operational with CMAC functions working.&lt;BR /&gt;Requirement: SecOC (Secure Onboard Communication) implementation.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;For SecOC implementation on S32K144, does NXP provide:&lt;/P&gt;&lt;P&gt;1. Built-in Freshness Value Manager (FVM) for SecOC compliance?&lt;BR /&gt;2. Hardware-based anti-replay mechanisms suitable for SecOC?&lt;BR /&gt;3. Any other S32K144 features that support SecOC freshness management?&lt;BR /&gt;&lt;BR /&gt;SecOC-specific requirements:&lt;BR /&gt;- Freshness value generation for message authentication&lt;BR /&gt;- Anti-replay attack protection for CAN messages&lt;BR /&gt;- Synchronization between ECUs for freshness values&lt;BR /&gt;&lt;BR /&gt;1. Does S32K144 have built-in FVM or similar for SecOC?&lt;BR /&gt;2. Any NXP SecOC reference implementations or application notes?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jan 2026 05:50:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K144-SecOC-Implementation-Freshness-Value-Manager-and-Anti/m-p/2301822#M56409</guid>
      <dc:creator>Kishore_14</dc:creator>
      <dc:date>2026-01-28T05:50:17Z</dc:date>
    </item>
    <item>
      <title>Re: S32K144 SecOC Implementation - Freshness Value Manager and Anti-Replay Solutio</title>
      <link>https://community.nxp.com/t5/S32K/S32K144-SecOC-Implementation-Freshness-Value-Manager-and-Anti/m-p/2302247#M56418</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/257154"&gt;@Kishore_14&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You don’t need anything special for SecOC. As long as the hardware can do AES‑128 CMAC, it’s sufficient. That’s the only crypto primitive SecOC actually uses. CSEc (SHE‑based) on the S32K is fully enough - it gives you HW‑accelerated AES‑CMAC and protected key slots, which is exactly what SecOC needs.&lt;/P&gt;
&lt;P&gt;All the other CSEc features (secure boot MAC, key derivation, random number, etc.) is nice to have but SecOC doesn’t depend on it. Freshness values and anti‑replay counters are handled completely in software by the FVM. Hardware doesn’t provide any special counter for this. CSEc provides only features given by SHE specification.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jan 2026 12:23:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K144-SecOC-Implementation-Freshness-Value-Manager-and-Anti/m-p/2302247#M56418</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2026-01-28T12:23:14Z</dc:date>
    </item>
  </channel>
</rss>

