<?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 NIST updating Cybersecurity Framework, seeking feedback in Industry News</title>
    <link>https://community.isc2.org/t5/Industry-News/NIST-updating-Cybersecurity-Framework-seeking-feedback/m-p/56971#M6091</link>
    <description>&lt;P&gt;&lt;A href="https://www.nist.gov/system/files/documents/2023/01/19/CSF_2.0_Concept_Paper_01-18-23.pdf" target="_blank" rel="noopener"&gt;https://www.nist.gov/system/files/documents/2023/01/19/CSF_2.0_Concept_Paper_01-18-23.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Do the proposed changes reflect the current cybersecurity landscape (standards, risks, and technologies)?&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Are the proposed changes sufficient and appropriate? Are there other elements that should be considered under each area?&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Do the proposed changes support different use cases in various sectors, types, and sizes of organizations (and with varied capabilities, resources, and technologies)?&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Are there additional changes not covered here that should be considered?&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;For those using CSF 1.1, would the proposed changes affect continued adoption of the Framework, and how so?&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;&lt;SPAN&gt;For those not using the Framework, would the proposed changes affect the potential use of the Framework?&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;&lt;SPAN&gt;Feedback and comments should be directed to cyberframework@nist.gov by March 3, 2023.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Mon, 30 Jan 2023 14:14:14 GMT</pubDate>
    <dc:creator>gidyn</dc:creator>
    <dc:date>2023-01-30T14:14:14Z</dc:date>
    <item>
      <title>NIST updating Cybersecurity Framework, seeking feedback</title>
      <link>https://community.isc2.org/t5/Industry-News/NIST-updating-Cybersecurity-Framework-seeking-feedback/m-p/56971#M6091</link>
      <description>&lt;P&gt;&lt;A href="https://www.nist.gov/system/files/documents/2023/01/19/CSF_2.0_Concept_Paper_01-18-23.pdf" target="_blank" rel="noopener"&gt;https://www.nist.gov/system/files/documents/2023/01/19/CSF_2.0_Concept_Paper_01-18-23.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Do the proposed changes reflect the current cybersecurity landscape (standards, risks, and technologies)?&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Are the proposed changes sufficient and appropriate? Are there other elements that should be considered under each area?&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Do the proposed changes support different use cases in various sectors, types, and sizes of organizations (and with varied capabilities, resources, and technologies)?&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Are there additional changes not covered here that should be considered?&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;For those using CSF 1.1, would the proposed changes affect continued adoption of the Framework, and how so?&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;&lt;SPAN&gt;For those not using the Framework, would the proposed changes affect the potential use of the Framework?&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;&lt;SPAN&gt;Feedback and comments should be directed to cyberframework@nist.gov by March 3, 2023.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 30 Jan 2023 14:14:14 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/NIST-updating-Cybersecurity-Framework-seeking-feedback/m-p/56971#M6091</guid>
      <dc:creator>gidyn</dc:creator>
      <dc:date>2023-01-30T14:14:14Z</dc:date>
    </item>
    <item>
      <title>Re: NIST updating Cybersecurity Framework, seeking feedback</title>
      <link>https://community.isc2.org/t5/Industry-News/NIST-updating-Cybersecurity-Framework-seeking-feedback/m-p/56983#M6092</link>
      <description>Excellent information share.</description>
      <pubDate>Tue, 31 Jan 2023 00:11:44 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/NIST-updating-Cybersecurity-Framework-seeking-feedback/m-p/56983#M6092</guid>
      <dc:creator>PeteHayden</dc:creator>
      <dc:date>2023-01-31T00:11:44Z</dc:date>
    </item>
  </channel>
</rss>

