<?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: Whose at fault, CITRIX or the Client in Tech Talk</title>
    <link>https://community.isc2.org/t5/Tech-Talk/Whose-at-fault-CITRIX-or-the-Client/m-p/33376#M2430</link>
    <description>&lt;P&gt;&lt;a href="https://community.isc2.org/t5/user/viewprofilepage/user-id/1676172747"&gt;@MJM&lt;/a&gt;&amp;nbsp;&amp;nbsp; Here is an example of Australian Security Directorate taking action:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.itnews.com.au/news/citrix-bug-forced-defence-to-pull-recruitment-database-offline-538955?eid=3&amp;amp;edate=20200305&amp;amp;utm_source=20200305_PM&amp;amp;utm_medium=newsletter&amp;amp;utm_campaign=daily_newsletter" target="_blank"&gt;https://www.itnews.com.au/news/citrix-bug-forced-defence-to-pull-recruitment-database-offline-538955?eid=3&amp;amp;edate=20200305&amp;amp;utm_source=20200305_PM&amp;amp;utm_medium=newsletter&amp;amp;utm_campaign=daily_newsletter&lt;/A&gt;&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>Thu, 05 Mar 2020 03:06:20 GMT</pubDate>
    <dc:creator>Caute_cautim</dc:creator>
    <dc:date>2020-03-05T03:06:20Z</dc:date>
    <item>
      <title>Whose at fault, CITRIX or the Client</title>
      <link>https://community.isc2.org/t5/Tech-Talk/Whose-at-fault-CITRIX-or-the-Client/m-p/33341#M2423</link>
      <description>&lt;P&gt;A recent Ransomware attack against a Luxembourg company resulted from a flaw in Citrix (surprise)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://today.rtl.lu/news/luxembourg/a/1477807.html" target="_blank"&gt;https://today.rtl.lu/news/luxembourg/a/1477807.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2020 20:18:23 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/Whose-at-fault-CITRIX-or-the-Client/m-p/33341#M2423</guid>
      <dc:creator>dcontesti</dc:creator>
      <dc:date>2020-03-03T20:18:23Z</dc:date>
    </item>
    <item>
      <title>Re: Whose at fault, CITRIX or the Client</title>
      <link>https://community.isc2.org/t5/Tech-Talk/Whose-at-fault-CITRIX-or-the-Client/m-p/33356#M2426</link>
      <description>&lt;P&gt;This issue definitely falls back on the client and this particular issue comes back to Patch Management practices, and also the ability to detect the zero-day exposure through good Vulnerability Management.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have several enterprise clients here in Australia with Citrix NetScaler's that were vulnerable to the exact same issue, and fortunately all of them were able to implement the initial workaround that was issued in late December.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One of my clients didn't patch until 7 January, which was just in time for malicious actors that were starting to exploit this vulnerability actively on or around 11 January.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We're lucky in Australia that our government was tracking exposure to this issue, and they were contacting large organisations to warn them to check they had applied the patch too.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Mar 2020 12:51:24 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/Whose-at-fault-CITRIX-or-the-Client/m-p/33356#M2426</guid>
      <dc:creator>MJM</dc:creator>
      <dc:date>2020-03-04T12:51:24Z</dc:date>
    </item>
    <item>
      <title>Re: Whose at fault, CITRIX or the Client</title>
      <link>https://community.isc2.org/t5/Tech-Talk/Whose-at-fault-CITRIX-or-the-Client/m-p/33374#M2429</link>
      <description>&lt;P&gt;&lt;a href="https://community.isc2.org/t5/user/viewprofilepage/user-id/1676172747"&gt;@MJM&lt;/a&gt;&amp;nbsp;&amp;nbsp; I agree, bad patch management is a major issue.&amp;nbsp; But I think this also points out a major resilience issue for the organisation as well.&amp;nbsp; They certainly need to review current current Hygiene practices, DR and BCP and some more investment from the board given the circumstances.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope they did not simply fall back to cyber insurance to bale them out.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I agree the Australian Government is very proactive, and I would say the New Zealand CERT was also doing a similar approach to minimise the impact.&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>Wed, 04 Mar 2020 23:25:49 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/Whose-at-fault-CITRIX-or-the-Client/m-p/33374#M2429</guid>
      <dc:creator>Caute_cautim</dc:creator>
      <dc:date>2020-03-04T23:25:49Z</dc:date>
    </item>
    <item>
      <title>Re: Whose at fault, CITRIX or the Client</title>
      <link>https://community.isc2.org/t5/Tech-Talk/Whose-at-fault-CITRIX-or-the-Client/m-p/33376#M2430</link>
      <description>&lt;P&gt;&lt;a href="https://community.isc2.org/t5/user/viewprofilepage/user-id/1676172747"&gt;@MJM&lt;/a&gt;&amp;nbsp;&amp;nbsp; Here is an example of Australian Security Directorate taking action:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.itnews.com.au/news/citrix-bug-forced-defence-to-pull-recruitment-database-offline-538955?eid=3&amp;amp;edate=20200305&amp;amp;utm_source=20200305_PM&amp;amp;utm_medium=newsletter&amp;amp;utm_campaign=daily_newsletter" target="_blank"&gt;https://www.itnews.com.au/news/citrix-bug-forced-defence-to-pull-recruitment-database-offline-538955?eid=3&amp;amp;edate=20200305&amp;amp;utm_source=20200305_PM&amp;amp;utm_medium=newsletter&amp;amp;utm_campaign=daily_newsletter&lt;/A&gt;&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>Thu, 05 Mar 2020 03:06:20 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/Whose-at-fault-CITRIX-or-the-Client/m-p/33376#M2430</guid>
      <dc:creator>Caute_cautim</dc:creator>
      <dc:date>2020-03-05T03:06:20Z</dc:date>
    </item>
  </channel>
</rss>

