<?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: For 2026, The Move Towards FIPS 140–3 in Tech Talk</title>
    <link>https://community.isc2.org/t5/Tech-Talk/For-2026-The-Move-Towards-FIPS-140-3/m-p/69531#M4396</link>
    <description>&lt;P&gt;Thanks for sharing this information with us&amp;nbsp;&lt;a href="https://community.isc2.org/t5/user/viewprofilepage/user-id/809125741"&gt;@Caute_cautim&lt;/a&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 16 Apr 2024 10:59:31 GMT</pubDate>
    <dc:creator>Kyaw_Myo_Oo</dc:creator>
    <dc:date>2024-04-16T10:59:31Z</dc:date>
    <item>
      <title>For 2026, The Move Towards FIPS 140–3</title>
      <link>https://community.isc2.org/t5/Tech-Talk/For-2026-The-Move-Towards-FIPS-140-3/m-p/69333#M4386</link>
      <description>&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If your company is serious about cybersecurity and in protecting data, there’s a good chance that it will support FIPS (Federal Information Processing Standards Publications) 140–2. Currently, there are 946 certified modules for FIPS 140–2 [&lt;A class="" href="https://csrc.nist.gov/projects/cryptographic-module-validation-program/validated-modules/search?SearchMode=Basic&amp;amp;CertificateStatus=Active&amp;amp;ValidationYear=0" target="_blank" rel="noopener ugc nofollow"&gt;here&lt;/A&gt;]:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://medium.com/asecuritysite-when-bob-met-alice/for-2026-the-move-towards-fips-140-3-cac79df08789" target="_blank" rel="noopener"&gt;https://medium.com/asecuritysite-when-bob-met-alice/for-2026-the-move-towards-fips-140-3-cac79df08789&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Caute_Cautim&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 10 Apr 2024 06:08:36 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/For-2026-The-Move-Towards-FIPS-140-3/m-p/69333#M4386</guid>
      <dc:creator>Caute_cautim</dc:creator>
      <dc:date>2024-04-10T06:08:36Z</dc:date>
    </item>
    <item>
      <title>Re: For 2026, The Move Towards FIPS 140–3</title>
      <link>https://community.isc2.org/t5/Tech-Talk/For-2026-The-Move-Towards-FIPS-140-3/m-p/69531#M4396</link>
      <description>&lt;P&gt;Thanks for sharing this information with us&amp;nbsp;&lt;a href="https://community.isc2.org/t5/user/viewprofilepage/user-id/809125741"&gt;@Caute_cautim&lt;/a&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 16 Apr 2024 10:59:31 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/For-2026-The-Move-Towards-FIPS-140-3/m-p/69531#M4396</guid>
      <dc:creator>Kyaw_Myo_Oo</dc:creator>
      <dc:date>2024-04-16T10:59:31Z</dc:date>
    </item>
    <item>
      <title>Re: For 2026, The Move Towards FIPS 140–3</title>
      <link>https://community.isc2.org/t5/Tech-Talk/For-2026-The-Move-Towards-FIPS-140-3/m-p/69948#M4415</link>
      <description>&lt;P&gt;There are two transitions to be aware of here based on the company's role.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Product development: The only option at this point is 140-3.&amp;nbsp; Some updates can still be done for existing 140-2 devices, but if a company wishes to validate a new product to FIPS 140, FIPS 140-3 is their only option.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Product procurement: All 140-2 products will migrate to the historical list 2026 as this article states.&amp;nbsp; This does not mean they can no longer be used (unless company policy dictates this).&amp;nbsp; This means these devices can no longer be procured and only 140-3 devices will be procurable for compliance.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Overall just because a device is 140-2 compliant does not mean it is inherently less secure than 140-3. This will come down to the specific device in question.&amp;nbsp; Cryptographic algorithms, for instance, are not necessarily different between 140-2 and 140-3. Approved cryptographic algorithms are added and removed in parallel to this program (algorithms fall under CAVP while the other requirements fall under CMVP).&amp;nbsp; The impact of 140-3 is more apparent in more complex and higher level devices.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 May 2024 14:57:10 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/For-2026-The-Move-Towards-FIPS-140-3/m-p/69948#M4415</guid>
      <dc:creator>BRutan</dc:creator>
      <dc:date>2024-05-02T14:57:10Z</dc:date>
    </item>
  </channel>
</rss>

