<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: The ATM Protection Racket</title>
	<atom:link href="http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/</link>
	<description>Security Research, Computer Laboratory, University of Cambridge</description>
	<lastBuildDate>Thu, 09 Sep 2010 08:25:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: P.Seymour</title>
		<link>http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/comment-page-1/#comment-31150</link>
		<dc:creator>P.Seymour</dc:creator>
		<pubDate>Sat, 20 Jun 2009 09:20:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/#comment-31150</guid>
		<description>Hi,

Did the major banks ever respond to this issue and solution?</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Did the major banks ever respond to this issue and solution?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vern</title>
		<link>http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/comment-page-1/#comment-21208</link>
		<dc:creator>vern</dc:creator>
		<pubDate>Sun, 01 Apr 2007 22:04:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/#comment-21208</guid>
		<description>To answer the following question , But surely after a few such attacks it will be very easy to identify the responsible parties from CCTV footage, since presumably the machines log enough information to be able to identify the last transaction in which the ATM was able to communicate with a chip on a card?
Yes the machine logs all the information of transactions and faults.Even if you begin to insert youre card and then pull it out before the card reader takes it a card tease is registered.If the banks wanted to they could implement more safty features on the ATM to protect the customer such as Biometrics where finger prints would be required along with pin numbers,There is also the obtion of retena scan .But this becomes costly and banks dont charge for atm withdrawls,If I had to catch a person vandalising an ATM Id have no problem in breaking there fingers.cause they piss me of and waste my time .</description>
		<content:encoded><![CDATA[<p>To answer the following question , But surely after a few such attacks it will be very easy to identify the responsible parties from CCTV footage, since presumably the machines log enough information to be able to identify the last transaction in which the ATM was able to communicate with a chip on a card?<br />
Yes the machine logs all the information of transactions and faults.Even if you begin to insert youre card and then pull it out before the card reader takes it a card tease is registered.If the banks wanted to they could implement more safty features on the ATM to protect the customer such as Biometrics where finger prints would be required along with pin numbers,There is also the obtion of retena scan .But this becomes costly and banks dont charge for atm withdrawls,If I had to catch a person vandalising an ATM Id have no problem in breaking there fingers.cause they piss me of and waste my time .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Lightfoot</title>
		<link>http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/comment-page-1/#comment-6009</link>
		<dc:creator>Chris Lightfoot</dc:creator>
		<pubDate>Tue, 21 Nov 2006 21:05:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/#comment-6009</guid>
		<description>So if the criminal damaging the ATM wants to minimise their chances of being caught at the scene, they want to attack it in a way that seems indistinguishable from the activities of a normal user. Sticking in a card which zaps the smartcard reader contacts with a high voltage seems suitable here. But surely after a few such attacks it will be very easy to identify the responsible parties from CCTV footage, since presumably the machines log enough information to be able to identify the last transaction in which the ATM was able to communicate with a chip on a card?</description>
		<content:encoded><![CDATA[<p>So if the criminal damaging the ATM wants to minimise their chances of being caught at the scene, they want to attack it in a way that seems indistinguishable from the activities of a normal user. Sticking in a card which zaps the smartcard reader contacts with a high voltage seems suitable here. But surely after a few such attacks it will be very easy to identify the responsible parties from CCTV footage, since presumably the machines log enough information to be able to identify the last transaction in which the ATM was able to communicate with a chip on a card?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/comment-page-1/#comment-5787</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Mon, 20 Nov 2006 15:18:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/#comment-5787</guid>
		<description>But someone who goes around damaging ATMs 200 times in a weekend is at a far greater risk of being caught than someone who makes 200 phantom withdrawals - sticking a card in one is so normal you wouldn&#039;t see it, whacking it with a bat isn&#039;t. And even if you are only arrested for vandalism, the kind of person who is doing this probably has excellent reasons to avoid any dealings with cops whatsoever.

Further, what makes you think the bank is losing money whilst the ATM is out of service? Cash handling is a cost.</description>
		<content:encoded><![CDATA[<p>But someone who goes around damaging ATMs 200 times in a weekend is at a far greater risk of being caught than someone who makes 200 phantom withdrawals &#8211; sticking a card in one is so normal you wouldn&#8217;t see it, whacking it with a bat isn&#8217;t. And even if you are only arrested for vandalism, the kind of person who is doing this probably has excellent reasons to avoid any dealings with cops whatsoever.</p>
<p>Further, what makes you think the bank is losing money whilst the ATM is out of service? Cash handling is a cost.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lev</title>
		<link>http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/comment-page-1/#comment-5774</link>
		<dc:creator>Lev</dc:creator>
		<pubDate>Mon, 20 Nov 2006 14:05:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/#comment-5774</guid>
		<description>Are we forgetting something here?

How much money can the fraudster get out of the broken machine? I think the theory is correct but in practise?</description>
		<content:encoded><![CDATA[<p>Are we forgetting something here?</p>
<p>How much money can the fraudster get out of the broken machine? I think the theory is correct but in practise?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Bond</title>
		<link>http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/comment-page-1/#comment-5684</link>
		<dc:creator>Mike Bond</dc:creator>
		<pubDate>Sun, 19 Nov 2006 19:43:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/#comment-5684</guid>
		<description>Alex says:

&lt;i&gt;I don’t think this is workable. &lt;/i&gt;

This is the crucial issue. Could such a racket actually work or not? I see your arguments about DOS being practicable on the net because it&#039;s cheap, the cost of nodes is low, and the cost of losing nodes is low. But I think these facts also remain true in the real world for ATM infrastructure attack...

* One man working full time over a weekend can easily visit 200 cash machines (I&#039;ve known a case where 200 phantom withdrawals were made in a single weekend), and they don&#039;t need a lot of people -- they just need more people than there are ATM repair engineers, scaled by the factor for how long a break takes (seconds) versus a repair (hours--days). It&#039;s much quicker to break stuff than to repair it, I promise. &lt;i&gt;And to find problems with the ATM network, than to solve them ;-)&lt;/i&gt; 

*DOS based on killing hardware-equipment is very different from DOS based on filling up bandwidth pipes. Once the attack stops in the latter, business can resume as normal, no-one needs to go round fixing anything as such, possibly reboot a few computers.

* Remember that smashing it with a bat is at the extreme end of a whole spectrum I presented. Some of the subtle stuff could be done so that ATMs could be disabled even while under surveillance.
 
* Don&#039;t think that the police would put ATM racketeering at the top of their priority list without a serious political impetus, or a wad of cash from the banks to go investigate. There are a lot more violent and hurtful crimes to think about too. And you are not even disabling the whole ATM, just the chip functionality.

</description>
		<content:encoded><![CDATA[<p>Alex says:</p>
<p><i>I don’t think this is workable. </i></p>
<p>This is the crucial issue. Could such a racket actually work or not? I see your arguments about DOS being practicable on the net because it&#8217;s cheap, the cost of nodes is low, and the cost of losing nodes is low. But I think these facts also remain true in the real world for ATM infrastructure attack&#8230;</p>
<p>* One man working full time over a weekend can easily visit 200 cash machines (I&#8217;ve known a case where 200 phantom withdrawals were made in a single weekend), and they don&#8217;t need a lot of people &#8212; they just need more people than there are ATM repair engineers, scaled by the factor for how long a break takes (seconds) versus a repair (hours&#8211;days). It&#8217;s much quicker to break stuff than to repair it, I promise. <i>And to find problems with the ATM network, than to solve them <img src='http://www.lightbluetouchpaper.org/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </i> </p>
<p>*DOS based on killing hardware-equipment is very different from DOS based on filling up bandwidth pipes. Once the attack stops in the latter, business can resume as normal, no-one needs to go round fixing anything as such, possibly reboot a few computers.</p>
<p>* Remember that smashing it with a bat is at the extreme end of a whole spectrum I presented. Some of the subtle stuff could be done so that ATMs could be disabled even while under surveillance.</p>
<p>* Don&#8217;t think that the police would put ATM racketeering at the top of their priority list without a serious political impetus, or a wad of cash from the banks to go investigate. There are a lot more violent and hurtful crimes to think about too. And you are not even disabling the whole ATM, just the chip functionality.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Clayton</title>
		<link>http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/comment-page-1/#comment-5679</link>
		<dc:creator>Richard Clayton</dc:creator>
		<pubDate>Sun, 19 Nov 2006 18:51:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/#comment-5679</guid>
		<description>The extended advertisement of ID KEY above doesn&#039;t seem to be quite relevant to Mike&#039;s post :(

It probably deserves some response though

The author appears to suggest that ATM fraud will be solved by updating all the ATMs (that&#039;s quite an investment) to read another sort of card (the ID KEY) which they happen to have patented. This card will require you to input not only your PIN but also a one-time code (so that observing the transaction doesn&#039;t assist the bad guys).

There is no discussion as to the costs (or methods) of updating these one-time codes, or indeed whether a camera (or a shoulder-surfing crook) will be unable to read the paper on which all these codes will (necessarily) be written out.

Clearly this does make ATM usage a bit more secure (and a bit more inconvenient), but it&#039;s a pretty disruptive change to their use and so it doesn&#039;t look like a no-brainer to implement it (rather the reverse).

The second safeguard is apparently the use of embedded photo-id. This is straightforward to rebut as a solution since there&#039;s existing research as to its ineffectiveness. A description of the classic experiment can be found in &lt;a href=&quot;http://www.cl.cam.ac.uk/~rja14/Papers/SE-13.pdf&quot; rel=&quot;nofollow&quot; rel=&quot;nofollow&quot;&gt;#13.3 of Ross&#039;s book&lt;/a&gt;. Those who have not read about it will find the time well spent.</description>
		<content:encoded><![CDATA[<p>The extended advertisement of ID KEY above doesn&#8217;t seem to be quite relevant to Mike&#8217;s post <img src='http://www.lightbluetouchpaper.org/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
<p>It probably deserves some response though</p>
<p>The author appears to suggest that ATM fraud will be solved by updating all the ATMs (that&#8217;s quite an investment) to read another sort of card (the ID KEY) which they happen to have patented. This card will require you to input not only your PIN but also a one-time code (so that observing the transaction doesn&#8217;t assist the bad guys).</p>
<p>There is no discussion as to the costs (or methods) of updating these one-time codes, or indeed whether a camera (or a shoulder-surfing crook) will be unable to read the paper on which all these codes will (necessarily) be written out.</p>
<p>Clearly this does make ATM usage a bit more secure (and a bit more inconvenient), but it&#8217;s a pretty disruptive change to their use and so it doesn&#8217;t look like a no-brainer to implement it (rather the reverse).</p>
<p>The second safeguard is apparently the use of embedded photo-id. This is straightforward to rebut as a solution since there&#8217;s existing research as to its ineffectiveness. A description of the classic experiment can be found in <a href="http://www.cl.cam.ac.uk/~rja14/Papers/SE-13.pdf" rel="nofollow" rel="nofollow">#13.3 of Ross&#8217;s book</a>. Those who have not read about it will find the time well spent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/comment-page-1/#comment-5648</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Sun, 19 Nov 2006 14:56:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/#comment-5648</guid>
		<description>I don&#039;t think this is workable. What you describe is essentially a DOS attack, but the reason for DOS attacks&#039; prevalence on the Net is that a) the incremental cost of one more bot is near-zero, b) the risk of one being caught is small, and c) the cost of one bot being caught is zero. Imagine trying to push John Lewis out of business by sending lots and lots of mail-order  forms, and then compare using a botnet to hammer their website.

Delivering enough smash attacks to impose a cost that is significant compared to the bank&#039;s free cash flow is far harder in reality than in cyberspace - you need quite a few people. The chance of getting caught each time is probably far greater on the streets, and you only need to get caught a few times before the cost spikes dramatically (i.e. someone realises that the same person keeps smashing ATMs and asks why, you go down for blackmail rather than crim dam).

The banks have every reason to keep cash machines cheap, cover them with CCTV cameras, and design them to fail-secure by breaking down easily under attack.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think this is workable. What you describe is essentially a DOS attack, but the reason for DOS attacks&#8217; prevalence on the Net is that a) the incremental cost of one more bot is near-zero, b) the risk of one being caught is small, and c) the cost of one bot being caught is zero. Imagine trying to push John Lewis out of business by sending lots and lots of mail-order  forms, and then compare using a botnet to hammer their website.</p>
<p>Delivering enough smash attacks to impose a cost that is significant compared to the bank&#8217;s free cash flow is far harder in reality than in cyberspace &#8211; you need quite a few people. The chance of getting caught each time is probably far greater on the streets, and you only need to get caught a few times before the cost spikes dramatically (i.e. someone realises that the same person keeps smashing ATMs and asks why, you go down for blackmail rather than crim dam).</p>
<p>The banks have every reason to keep cash machines cheap, cover them with CCTV cameras, and design them to fail-secure by breaking down easily under attack.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clive Robinson</title>
		<link>http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/comment-page-1/#comment-5620</link>
		<dc:creator>Clive Robinson</dc:creator>
		<pubDate>Sun, 19 Nov 2006 11:17:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/#comment-5620</guid>
		<description>Mike,

You say,

   &quot;Fraud migrates&quot;

I actualy think &quot;it evolves&quot;, that is simple fraud works against an unsophisticated system, the users get hurt and scream the system operators are then forced to marginaly increase security.

However the criminal now knows from experiance that the improvment is only going to be small, therefor their previous fraud gives the funding and incentive to take the fraud to the next level and so on, and alows them to continue to recoup on their initial investment in associated procedures (fencing) to deal with their ill goton gains.

So the war starts, at each stage the defender has a choice, a simple / incremental  improvment, or a major / quantum improvment. If they chose the former due to expediancy then the war goes on, if the later there is a reasonable chance they will raise the threshold beyond the attackers means.

It is almost exactly the same as EW / ECM / ECCM / ECCCM....

Likewise if the system operator had implemented a sensible level of security at the out set then the fraud would not have been started in the first place as it would have been to difficult / expensive for the attacking fraudster to gain the initial toe hold. However once in the attacker goes on to make further investment into the attack, and this gives the attacker an increased incentive to prolong the war. 

The fact that the system operator was lazy / negligent / unknowing allowed a crack to appear in the system, and once it is there, the crack will be fourced open again and again unless the operator takes a sufficiently large step to prevent it.

Examples of this abound, the German Enigma is one of the earliest. The Sky Card system a more modern example, likewise the &quot;set top box cube&quot; that still bedevils cable operators. If at any point the system operators had taken a sensible look at their system security and not an expident look then the initial attack threshold would have been to dificult to cross.

To the fraudster, it is almost like a drug dependency, the initial fairly easy crack starts them off they then develop methods and systems to exploit it and they become hooked on hacking the system.

Therefor unless the system operator uses sufficient resources and makes the threshold to high for the attacker they are actually commiting themselves to an endless round of expensive incremental changes. 

It is fairly easy to see that even in the short term it is more cost effective to commit the required resources to raise the threashold properly...</description>
		<content:encoded><![CDATA[<p>Mike,</p>
<p>You say,</p>
<p>   &#8220;Fraud migrates&#8221;</p>
<p>I actualy think &#8220;it evolves&#8221;, that is simple fraud works against an unsophisticated system, the users get hurt and scream the system operators are then forced to marginaly increase security.</p>
<p>However the criminal now knows from experiance that the improvment is only going to be small, therefor their previous fraud gives the funding and incentive to take the fraud to the next level and so on, and alows them to continue to recoup on their initial investment in associated procedures (fencing) to deal with their ill goton gains.</p>
<p>So the war starts, at each stage the defender has a choice, a simple / incremental  improvment, or a major / quantum improvment. If they chose the former due to expediancy then the war goes on, if the later there is a reasonable chance they will raise the threshold beyond the attackers means.</p>
<p>It is almost exactly the same as EW / ECM / ECCM / ECCCM&#8230;.</p>
<p>Likewise if the system operator had implemented a sensible level of security at the out set then the fraud would not have been started in the first place as it would have been to difficult / expensive for the attacking fraudster to gain the initial toe hold. However once in the attacker goes on to make further investment into the attack, and this gives the attacker an increased incentive to prolong the war. </p>
<p>The fact that the system operator was lazy / negligent / unknowing allowed a crack to appear in the system, and once it is there, the crack will be fourced open again and again unless the operator takes a sufficiently large step to prevent it.</p>
<p>Examples of this abound, the German Enigma is one of the earliest. The Sky Card system a more modern example, likewise the &#8220;set top box cube&#8221; that still bedevils cable operators. If at any point the system operators had taken a sensible look at their system security and not an expident look then the initial attack threshold would have been to dificult to cross.</p>
<p>To the fraudster, it is almost like a drug dependency, the initial fairly easy crack starts them off they then develop methods and systems to exploit it and they become hooked on hacking the system.</p>
<p>Therefor unless the system operator uses sufficient resources and makes the threshold to high for the attacker they are actually commiting themselves to an endless round of expensive incremental changes. </p>
<p>It is fairly easy to see that even in the short term it is more cost effective to commit the required resources to raise the threashold properly&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Surreptitious Evil</title>
		<link>http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/comment-page-1/#comment-5612</link>
		<dc:creator>Surreptitious Evil</dc:creator>
		<pubDate>Sun, 19 Nov 2006 09:49:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/11/18/the-atm-protection-racket/#comment-5612</guid>
		<description>Mike,

On your initial premise - &quot;whether or not EMV is capable of sorting out the ATM fraud problem (also known as &#039;phantom withdrawals&#039;)&quot; - I am afraid that the answer is clearly &quot;no&quot;.  Phantom withdrawals are going to fall into one of the following categories:

1.  Where the withdrawal actually happened and the customer is deliberately trying to defraud the bank (for those without long history in this debate, this is the long-held position as the only option by the UK banks) or, to be fair, the customer simply does not remember conducting the transaction (most of us have had nights out like that :) ).

2.  Where the withdrawal was conducted with the customer&#039;s genuine card and their pin, but not but the customer and without their permission.  Often friends / family and not necessary with the customer having deliberately disclosed the pin (well-known numbers, seen the pin form, shoulder surfing ...)

3.  Where the card is forged and the pin captured through camera, bodged pin-pad, shoulder surfing etc.  EMV should go some way towards making the card forging more difficult, provided fallback is disabled.

4.  Simple (and non-malicious) error in the bank ATM or ledger systems.  (Error in the ledger should be catchable by cross-reference to the ATM transaction logs, but if the ATM accidentally records the wrong card / account number ...)

5.  Casual (possible, but I can&#039;t see how it could be done) or systematic fraud by bank staff or contractors (this would require multiple developers to be involved or some more local dodginess around authentication keys.)

There are some other (harder to do - normally needing stolen cards) attacks that apply to the smaller and simpler pay-for ATM estates but not to the main bank estates.

Addressing your main contentions:

    * Is this a war that the banks can win?

Not the way you frame it.  A bat through the screen will take any ATM out.

    * How much of bank anti-fraud policy is really driven by economics, and how much by honour?

Some is driven by economics, much is driven by regulatory context and displeasure, a considerable amount by (the marketing department&#039;s view of) public opinion, and a little by honour.

    * Should security architects be designing security protocols and systems that try and write the crook totally out of the equation, or should we leave them a small (acceptable) window, lest they fight us on a battleground which is more costly? Think here of the problems suffered in South Africa by improving anti-theft security on cars; live hijackings and the like soared upwards

We need to consider holistic risk - already the most common attack is against cash delivery when it is in the street.

    * What technologies can help us armour ATMs against denial of service?

Ah - sounds like a research project to me :)

S-E</description>
		<content:encoded><![CDATA[<p>Mike,</p>
<p>On your initial premise &#8211; &#8220;whether or not EMV is capable of sorting out the ATM fraud problem (also known as &#8216;phantom withdrawals&#8217;)&#8221; &#8211; I am afraid that the answer is clearly &#8220;no&#8221;.  Phantom withdrawals are going to fall into one of the following categories:</p>
<p>1.  Where the withdrawal actually happened and the customer is deliberately trying to defraud the bank (for those without long history in this debate, this is the long-held position as the only option by the UK banks) or, to be fair, the customer simply does not remember conducting the transaction (most of us have had nights out like that <img src='http://www.lightbluetouchpaper.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  ).</p>
<p>2.  Where the withdrawal was conducted with the customer&#8217;s genuine card and their pin, but not but the customer and without their permission.  Often friends / family and not necessary with the customer having deliberately disclosed the pin (well-known numbers, seen the pin form, shoulder surfing &#8230;)</p>
<p>3.  Where the card is forged and the pin captured through camera, bodged pin-pad, shoulder surfing etc.  EMV should go some way towards making the card forging more difficult, provided fallback is disabled.</p>
<p>4.  Simple (and non-malicious) error in the bank ATM or ledger systems.  (Error in the ledger should be catchable by cross-reference to the ATM transaction logs, but if the ATM accidentally records the wrong card / account number &#8230;)</p>
<p>5.  Casual (possible, but I can&#8217;t see how it could be done) or systematic fraud by bank staff or contractors (this would require multiple developers to be involved or some more local dodginess around authentication keys.)</p>
<p>There are some other (harder to do &#8211; normally needing stolen cards) attacks that apply to the smaller and simpler pay-for ATM estates but not to the main bank estates.</p>
<p>Addressing your main contentions:</p>
<p>    * Is this a war that the banks can win?</p>
<p>Not the way you frame it.  A bat through the screen will take any ATM out.</p>
<p>    * How much of bank anti-fraud policy is really driven by economics, and how much by honour?</p>
<p>Some is driven by economics, much is driven by regulatory context and displeasure, a considerable amount by (the marketing department&#8217;s view of) public opinion, and a little by honour.</p>
<p>    * Should security architects be designing security protocols and systems that try and write the crook totally out of the equation, or should we leave them a small (acceptable) window, lest they fight us on a battleground which is more costly? Think here of the problems suffered in South Africa by improving anti-theft security on cars; live hijackings and the like soared upwards</p>
<p>We need to consider holistic risk &#8211; already the most common attack is against cash delivery when it is in the street.</p>
<p>    * What technologies can help us armour ATMs against denial of service?</p>
<p>Ah &#8211; sounds like a research project to me <img src='http://www.lightbluetouchpaper.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>S-E</p>
]]></content:encoded>
	</item>
</channel>
</rss>
