<?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: Ransomware Response Checklist in Threats</title>
    <link>https://community.isc2.org/t5/Threats/Ransomware-Response-Checklist/m-p/64671#M977</link>
    <description>&lt;P&gt;&lt;a href="https://community.isc2.org/t5/user/viewprofilepage/user-id/604565541"&gt;@Kyaw_Myo_Oo&lt;/a&gt;&amp;nbsp;&amp;nbsp; Not many organisations are going to own up to a ransomware attack, unless it become public or by legislation they have to report it due to the fact client data has been potentially stolen or is unable to be accessed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A good checklist and is very welcome especially for those organisations who have not prepared, practiced their Incident Response processes.&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;</description>
    <pubDate>Sat, 18 Nov 2023 06:26:30 GMT</pubDate>
    <dc:creator>Caute_cautim</dc:creator>
    <dc:date>2023-11-18T06:26:30Z</dc:date>
    <item>
      <title>Ransomware Response Checklist</title>
      <link>https://community.isc2.org/t5/Threats/Ransomware-Response-Checklist/m-p/64619#M970</link>
      <description>&lt;P&gt;Dear All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;If you have experienced a ransomware attack, CISA strongly recommends using the following checklist provided in a Joint CISA and Multi-State Information Sharing and Analysis Center (MS-ISAC) Ransomware Guide to respond. This information will take you through the response process from detection to containment and eradication.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://www.cisa.gov/ransomware-response-checklist" target="_blank" rel="noopener"&gt;https://www.cisa.gov/ransomware-response-checklist&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;Discussion &lt;/STRONG&gt;Does your organization implemented to detect Ransomware attack? Really appreciate if someone could you please kindly help with some references to develop security requirements to protect against Ransomware attacks.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 16 Nov 2023 16:46:53 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Threats/Ransomware-Response-Checklist/m-p/64619#M970</guid>
      <dc:creator>Kyaw_Myo_Oo</dc:creator>
      <dc:date>2023-11-16T16:46:53Z</dc:date>
    </item>
    <item>
      <title>Re: Ransomware Response Checklist</title>
      <link>https://community.isc2.org/t5/Threats/Ransomware-Response-Checklist/m-p/64671#M977</link>
      <description>&lt;P&gt;&lt;a href="https://community.isc2.org/t5/user/viewprofilepage/user-id/604565541"&gt;@Kyaw_Myo_Oo&lt;/a&gt;&amp;nbsp;&amp;nbsp; Not many organisations are going to own up to a ransomware attack, unless it become public or by legislation they have to report it due to the fact client data has been potentially stolen or is unable to be accessed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A good checklist and is very welcome especially for those organisations who have not prepared, practiced their Incident Response processes.&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;</description>
      <pubDate>Sat, 18 Nov 2023 06:26:30 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Threats/Ransomware-Response-Checklist/m-p/64671#M977</guid>
      <dc:creator>Caute_cautim</dc:creator>
      <dc:date>2023-11-18T06:26:30Z</dc:date>
    </item>
  </channel>
</rss>

