<?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 Incident Response SOPs/Policies in Tech Talk</title>
    <link>https://community.isc2.org/t5/Tech-Talk/Incident-Response-SOPs-Policies/m-p/35604#M2671</link>
    <description>&lt;P&gt;Good morning,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am in the process of reviewing/editing/consolidating my organization's set of SOPs and policy documents regarding incident response.&amp;nbsp; These include DR-BCP, incident response framework, roles and responsibilities, etc..&amp;nbsp; All in all, we have 7-8 documents all surrounding cyber incident response, with a lot of double dipping.&amp;nbsp; I believe this creates confusion, not to mention version control issues.&amp;nbsp; So I was wondering - in your organizations, how many separate documents do you have that deal with cyber incident response?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 09 Oct 2023 09:31:22 GMT</pubDate>
    <dc:creator>N_Bakewell</dc:creator>
    <dc:date>2023-10-09T09:31:22Z</dc:date>
    <item>
      <title>Incident Response SOPs/Policies</title>
      <link>https://community.isc2.org/t5/Tech-Talk/Incident-Response-SOPs-Policies/m-p/35604#M2671</link>
      <description>&lt;P&gt;Good morning,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am in the process of reviewing/editing/consolidating my organization's set of SOPs and policy documents regarding incident response.&amp;nbsp; These include DR-BCP, incident response framework, roles and responsibilities, etc..&amp;nbsp; All in all, we have 7-8 documents all surrounding cyber incident response, with a lot of double dipping.&amp;nbsp; I believe this creates confusion, not to mention version control issues.&amp;nbsp; So I was wondering - in your organizations, how many separate documents do you have that deal with cyber incident response?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 09 Oct 2023 09:31:22 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/Incident-Response-SOPs-Policies/m-p/35604#M2671</guid>
      <dc:creator>N_Bakewell</dc:creator>
      <dc:date>2023-10-09T09:31:22Z</dc:date>
    </item>
    <item>
      <title>Re: Incident Response SOPs/Policies</title>
      <link>https://community.isc2.org/t5/Tech-Talk/Incident-Response-SOPs-Policies/m-p/35616#M2672</link>
      <description>&lt;P&gt;I work with a lot of orgs and review their policies and documentation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I typically see:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A BC/DR Policy document&lt;/P&gt;&lt;P&gt;A CSIR Policy document&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A BIA document listing critical applications and their owner, RTO, RPO, etc&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A BC/DR plan document (larger orgs will have this as 2 separate plans), which gives the details on how these are done.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A CSIR plan document.&amp;nbsp; Some groups will have a 'run book' or 'play book' with details on how to handle different specific incidents (DDOS attack, malware, ransomware, etc)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ideally, orgs should do a run thru of their BC plan, DR plan and CSIR plan on at least an annual basis.&amp;nbsp; I am really impressed when orgs do this more then once a year, but that seems rare.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 May 2020 17:38:53 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/Incident-Response-SOPs-Policies/m-p/35616#M2672</guid>
      <dc:creator>emb021</dc:creator>
      <dc:date>2020-05-13T17:38:53Z</dc:date>
    </item>
  </channel>
</rss>

