<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>tsb &#8211; Martijn Grooten</title>
	<atom:link href="/tag/tsb/feed/" rel="self" type="application/rss+xml" />
	<link>/</link>
	<description>Lapsed Ordinary</description>
	<lastBuildDate>Wed, 11 Jul 2018 21:00:20 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.3</generator>
	<item>
		<title>Bank of England to U.K. banks: Your tech needs a Plan B</title>
		<link>/2018/07/11/bank-of-england-to-u-k-banks-your-tech-needs-a-plan-b/</link>
					<comments>/2018/07/11/bank-of-england-to-u-k-banks-your-tech-needs-a-plan-b/#respond</comments>
		
		<dc:creator><![CDATA[Martijn]]></dc:creator>
		<pubDate>Wed, 11 Jul 2018 21:00:20 +0000</pubDate>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[bank]]></category>
		<category><![CDATA[bank of england]]></category>
		<category><![CDATA[cyber attack]]></category>
		<category><![CDATA[payment source]]></category>
		<category><![CDATA[stress test]]></category>
		<category><![CDATA[tsb]]></category>
		<category><![CDATA[visa]]></category>
		<guid isPermaLink="false">https://www.lapsedordinary.net/?p=482</guid>

					<description><![CDATA[The bank Bank of England, together with the Financial Conduct Authority and the Prudential Regulation Authority, has cautioned U.K. banks to prepare for cyber attacks and technical failures. Read more on Payment Source. (Note: subscription wall.)]]></description>
										<content:encoded><![CDATA[<p>The bank Bank of England, together with the Financial Conduct Authority and the Prudential Regulation Authority, has cautioned U.K. banks to prepare for cyber attacks and technical failures.<br />
Read more on <a href="https://www.paymentssource.com/news/bank-of-england-to-uk-banks-your-tech-needs-a-plan-b">Payment Source</a>. (Note: subscription wall.)</p>
]]></content:encoded>
					
					<wfw:commentRss>/2018/07/11/bank-of-england-to-u-k-banks-your-tech-needs-a-plan-b/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How TSB&#039;s simple tech issue became a big phishing problem</title>
		<link>/2018/05/10/how-tsbs-simple-tech-issue-became-a-big-phishing-problem/</link>
					<comments>/2018/05/10/how-tsbs-simple-tech-issue-became-a-big-phishing-problem/#respond</comments>
		
		<dc:creator><![CDATA[Martijn]]></dc:creator>
		<pubDate>Thu, 10 May 2018 09:46:04 +0000</pubDate>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[bank]]></category>
		<category><![CDATA[payment source]]></category>
		<category><![CDATA[phishing]]></category>
		<category><![CDATA[tsb]]></category>
		<category><![CDATA[uk]]></category>
		<guid isPermaLink="false">https://www.lapsedordinary.net/?p=458</guid>

					<description><![CDATA[Security is a top priority for financial institutions around the world. In the past few weeks, the U.K.’s TSB Bank has learned the hard way that availability is even more important. And when availability is an issue, security can’t be ignored. Read more on Payment Source. (Note: subscription wall.)]]></description>
										<content:encoded><![CDATA[<p>Security is a top priority for financial institutions around the world. In the past few weeks, the U.K.’s TSB Bank has learned the hard way that availability is even more important. And when availability is an issue, security can’t be ignored.<br />
Read more on <a href="https://www.paymentssource.com/news/how-tsb-banks-simple-tech-issue-became-a-big-phishing-problem">Payment Source</a>. (Note: subscription wall.)</p>
]]></content:encoded>
					
					<wfw:commentRss>/2018/05/10/how-tsbs-simple-tech-issue-became-a-big-phishing-problem/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
