<?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 TSB IT meltdown in Industry News</title>
    <link>https://community.isc2.org/t5/Industry-News/TSB-IT-meltdown/m-p/11265#M1065</link>
    <description>&lt;P&gt;&lt;A href="https://www.bbc.com/news/business-44370802" target="_blank"&gt;TSB Bank has had a bit of an issue with its computers&lt;/A&gt;.&amp;nbsp; Some people haven't been able to make transactions.&amp;nbsp; Sometimes it's been worse.&amp;nbsp; One customer watched thousands of pounds in wedding savings being stolen from his internet account as he waited on hold for the bank's fraud department.&amp;nbsp; The problem seems to have been created when a new upgrade was installed.&amp;nbsp; (The greatest cause of computer problems is computer "solutions," right?)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have all seen situation where a new system is introduced or a new upgrade is installed, and no provision has been made for roll-back.&amp;nbsp; It never ends well.&amp;nbsp; One of the areas that should always be covered in your business continuity plan is dealing with fallout from some keener manager's great new idea/baby.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(I could possibly make comments about an organization that has "updated" [and killed] two systems that worked with two that didn't ... but I won't ...)&lt;/P&gt;</description>
    <pubDate>Mon, 09 Oct 2023 08:48:32 GMT</pubDate>
    <dc:creator>rslade</dc:creator>
    <dc:date>2023-10-09T08:48:32Z</dc:date>
    <item>
      <title>TSB IT meltdown</title>
      <link>https://community.isc2.org/t5/Industry-News/TSB-IT-meltdown/m-p/11265#M1065</link>
      <description>&lt;P&gt;&lt;A href="https://www.bbc.com/news/business-44370802" target="_blank"&gt;TSB Bank has had a bit of an issue with its computers&lt;/A&gt;.&amp;nbsp; Some people haven't been able to make transactions.&amp;nbsp; Sometimes it's been worse.&amp;nbsp; One customer watched thousands of pounds in wedding savings being stolen from his internet account as he waited on hold for the bank's fraud department.&amp;nbsp; The problem seems to have been created when a new upgrade was installed.&amp;nbsp; (The greatest cause of computer problems is computer "solutions," right?)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have all seen situation where a new system is introduced or a new upgrade is installed, and no provision has been made for roll-back.&amp;nbsp; It never ends well.&amp;nbsp; One of the areas that should always be covered in your business continuity plan is dealing with fallout from some keener manager's great new idea/baby.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(I could possibly make comments about an organization that has "updated" [and killed] two systems that worked with two that didn't ... but I won't ...)&lt;/P&gt;</description>
      <pubDate>Mon, 09 Oct 2023 08:48:32 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/TSB-IT-meltdown/m-p/11265#M1065</guid>
      <dc:creator>rslade</dc:creator>
      <dc:date>2023-10-09T08:48:32Z</dc:date>
    </item>
  </channel>
</rss>

