<?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: CVSS v3 Environmental Considerations in Tech Talk</title>
    <link>https://community.isc2.org/t5/Tech-Talk/CVSS-v3-Environmental-Considerations/m-p/34506#M2539</link>
    <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.isc2.org/t5/user/viewprofilepage/user-id/1073616531"&gt;@StevenJ6052&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;My organization has begun using CVSS v3 as a critical metric in our vulnerability management program. We have several air gapped enclaves included in our program and I am looking for feedback on how others have leveraged the temporal or environmental portions of the CVSS v3 to tailor the base CVSS v3 spring of vulnerabilities to consider system architecture and implemented security controls to accurately access severity in their environment.&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;I've used the calculator for years in our application security program and often come across information system owners that tell me that they are safe because their systems are air gaped and not connected to the Internet. I remind them that they are connected to "other" networks that in possible times of conflict could be infiltrated. There is also, always, the insider threat to consider. Sure, I've seen other systems that are truly air gaped usually in labs. For those, there would not be a network attack vector.&lt;/P&gt;</description>
    <pubDate>Mon, 06 Apr 2020 13:38:42 GMT</pubDate>
    <dc:creator>AppDefects</dc:creator>
    <dc:date>2020-04-06T13:38:42Z</dc:date>
    <item>
      <title>CVSS v3 Environmental Considerations</title>
      <link>https://community.isc2.org/t5/Tech-Talk/CVSS-v3-Environmental-Considerations/m-p/34490#M2536</link>
      <description>&lt;P&gt;My organization has begun using CVSS v3 as a critical metric in our vulnerability management program. We have several air gapped enclaves included in our program and I am looking for feedback on how others have leveraged the temporal or environmental portions of the CVSS v3 to tailor the base CVSS v3 spring of vulnerabilities to consider system architecture and implemented security controls to accurately access severity in their environment.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Oct 2023 09:29:36 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/CVSS-v3-Environmental-Considerations/m-p/34490#M2536</guid>
      <dc:creator>StevenJ6052</dc:creator>
      <dc:date>2023-10-09T09:29:36Z</dc:date>
    </item>
    <item>
      <title>Re: CVSS v3 Environmental Considerations</title>
      <link>https://community.isc2.org/t5/Tech-Talk/CVSS-v3-Environmental-Considerations/m-p/34506#M2539</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.isc2.org/t5/user/viewprofilepage/user-id/1073616531"&gt;@StevenJ6052&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;My organization has begun using CVSS v3 as a critical metric in our vulnerability management program. We have several air gapped enclaves included in our program and I am looking for feedback on how others have leveraged the temporal or environmental portions of the CVSS v3 to tailor the base CVSS v3 spring of vulnerabilities to consider system architecture and implemented security controls to accurately access severity in their environment.&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;I've used the calculator for years in our application security program and often come across information system owners that tell me that they are safe because their systems are air gaped and not connected to the Internet. I remind them that they are connected to "other" networks that in possible times of conflict could be infiltrated. There is also, always, the insider threat to consider. Sure, I've seen other systems that are truly air gaped usually in labs. For those, there would not be a network attack vector.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Apr 2020 13:38:42 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/CVSS-v3-Environmental-Considerations/m-p/34506#M2539</guid>
      <dc:creator>AppDefects</dc:creator>
      <dc:date>2020-04-06T13:38:42Z</dc:date>
    </item>
    <item>
      <title>Re: CVSS v3 Environmental Considerations</title>
      <link>https://community.isc2.org/t5/Tech-Talk/CVSS-v3-Environmental-Considerations/m-p/34510#M2541</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.isc2.org/t5/user/viewprofilepage/user-id/887781263"&gt;@AppDefects&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;BLOCKQUOTE&gt;&lt;HR /&gt;... There is also, always, the insider threat to consider. Sure, I've seen other systems that are truly air gaped usually in labs. For those, there would not be a network attack vector.&lt;/BLOCKQUOTE&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;I am sure Rachel knows this aspect, but for other forum readers, I must remind all of the Stuxnet lesson: If you allow any use at all of portable USB devices by your users on the "air-gapped" network components, your network is not, in fact, truly air gapped and isolated. Sneakernet connections are just as significant as network connections using ethernet, wifi, Bluetooth, and other radio and cabling connections.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, remember that the insider threat has two parts: the intentionally malicious insider who actively attacks the network, and the naive or lazy insider who fails to follow mandated procedures and unknowingly brings malicious content into the system.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Craig&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Apr 2020 13:47:32 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/CVSS-v3-Environmental-Considerations/m-p/34510#M2541</guid>
      <dc:creator>CraginS</dc:creator>
      <dc:date>2020-04-06T13:47:32Z</dc:date>
    </item>
    <item>
      <title>Re: CVSS v3 Environmental Considerations</title>
      <link>https://community.isc2.org/t5/Tech-Talk/CVSS-v3-Environmental-Considerations/m-p/34537#M2551</link>
      <description>Thanks for the response.&lt;BR /&gt;&lt;BR /&gt;My situation is not a user trying to avoid or deny responsibility for the security of their systems, but are looking to provide an accurate measure of their vulnerability. Treating a truly air gapped industrial control system the same as you would for an internet accessible general support system is not an accurate representation of vulnerability.</description>
      <pubDate>Mon, 06 Apr 2020 22:47:35 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/CVSS-v3-Environmental-Considerations/m-p/34537#M2551</guid>
      <dc:creator>StevenJ6052</dc:creator>
      <dc:date>2020-04-06T22:47:35Z</dc:date>
    </item>
    <item>
      <title>Re: CVSS v3 Environmental Considerations</title>
      <link>https://community.isc2.org/t5/Tech-Talk/CVSS-v3-Environmental-Considerations/m-p/34541#M2552</link>
      <description>&lt;P&gt;Thanks for the response to my post&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I appreciate the perspective you provide regarding supply chain and insider threats.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;All too many people rush to dismiss risks in these situations, however the risk is still there, it just doesn't;t manifest itself through the usual attack vectors. Hence my question for how others have leveraged the CVSS scoring system to address these vulnerabilities in a responsible manner.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Apr 2020 22:58:40 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/CVSS-v3-Environmental-Considerations/m-p/34541#M2552</guid>
      <dc:creator>StevenJ6052</dc:creator>
      <dc:date>2020-04-06T22:58:40Z</dc:date>
    </item>
  </channel>
</rss>

