<?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: SOC Audit | Vulnerability Management in Tech Talk</title>
    <link>https://community.isc2.org/t5/Tech-Talk/SOC-Audit-Vulnerability-Management/m-p/19919#M947</link>
    <description>&lt;P&gt;Thank you &lt;a href="https://community.isc2.org/t5/user/viewprofilepage/user-id/636057953"&gt;@Rick_Roach&lt;/a&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 08 Mar 2019 18:37:48 GMT</pubDate>
    <dc:creator>SafiR</dc:creator>
    <dc:date>2019-03-08T18:37:48Z</dc:date>
    <item>
      <title>SOC Audit | Vulnerability Management</title>
      <link>https://community.isc2.org/t5/Tech-Talk/SOC-Audit-Vulnerability-Management/m-p/19897#M943</link>
      <description>&lt;P&gt;Does SOC or ISO audits require an organization to identify time to mitigate in their patching policies?&lt;BR /&gt;For example, 30 day for critical vulnerabilities, 60 days for high....etc.&lt;BR /&gt;If yes, is there a minimum acceptable time frame for a SOC auditor or for ISO27001 compliance?&lt;/P&gt;</description>
      <pubDate>Thu, 07 Mar 2019 22:21:52 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/SOC-Audit-Vulnerability-Management/m-p/19897#M943</guid>
      <dc:creator>SafiR</dc:creator>
      <dc:date>2019-03-07T22:21:52Z</dc:date>
    </item>
    <item>
      <title>Re: SOC Audit | Vulnerability Management</title>
      <link>https://community.isc2.org/t5/Tech-Talk/SOC-Audit-Vulnerability-Management/m-p/19916#M945</link>
      <description>&lt;P&gt;For SOC2 audits, the auditors usually measure if you're mitigating vulnerabilities in accordance with your policy. However, policy should be in alignment with industry best practice (NIST, CIS, etc.). If your policy states that you have two years to remediate a critical vulnerability, that would be an issue. The leading practice is typically 15-30 days for critical, 30-60 days for high, 60-90 days for medium, and aligned with org's configuration management policy for low/informational.&lt;/P&gt;</description>
      <pubDate>Fri, 08 Mar 2019 16:21:00 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/SOC-Audit-Vulnerability-Management/m-p/19916#M945</guid>
      <dc:creator>Rick_Roach</dc:creator>
      <dc:date>2019-03-08T16:21:00Z</dc:date>
    </item>
    <item>
      <title>Re: SOC Audit | Vulnerability Management</title>
      <link>https://community.isc2.org/t5/Tech-Talk/SOC-Audit-Vulnerability-Management/m-p/19919#M947</link>
      <description>&lt;P&gt;Thank you &lt;a href="https://community.isc2.org/t5/user/viewprofilepage/user-id/636057953"&gt;@Rick_Roach&lt;/a&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Mar 2019 18:37:48 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/SOC-Audit-Vulnerability-Management/m-p/19919#M947</guid>
      <dc:creator>SafiR</dc:creator>
      <dc:date>2019-03-08T18:37:48Z</dc:date>
    </item>
  </channel>
</rss>

