<?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: Why Johnny Can&#8217;t Bank Safely</title>
	<atom:link href="http://emergentchaos.com/archives/2007/02/why-johnny-cant-bank-safely.html/feed" rel="self" type="application/rss+xml" />
	<link>http://emergentchaos.com/archives/2007/02/why-johnny-cant-bank-safely.html</link>
	<description>The Emergent Chaos Jazz Combo</description>
	<lastBuildDate>Mon, 15 Mar 2010 15:02:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: insurance company ratings</title>
		<link>http://emergentchaos.com/archives/2007/02/why-johnny-cant-bank-safely.html/comment-page-1#comment-3206</link>
		<dc:creator>insurance company ratings</dc:creator>
		<pubDate>Sun, 25 Feb 2007 07:55:43 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2207#comment-3206</guid>
		<description>insurance company ratings
</description>
		<content:encoded><![CDATA[<p>insurance company ratings</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zooko O'Whielacronx</title>
		<link>http://emergentchaos.com/archives/2007/02/why-johnny-cant-bank-safely.html/comment-page-1#comment-3205</link>
		<dc:creator>Zooko O'Whielacronx</dc:creator>
		<pubDate>Tue, 06 Feb 2007 14:19:34 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2207#comment-3205</guid>
		<description>I&#039;m glad to see some real experiments on this subject.  The results from this one were consistent with my pre-existing guesses.  My guess about the Pet Name Toolbar and Passpet is that they would protect users in almost all cases in a similar experiment.  (Disclaimer: I&#039;m biased, of course -- I&#039;m partially responsible for some of the ideas behind those tools.)
&lt;a href=&quot;http://petname.mozdev.org/&quot; rel=&quot;nofollow&quot;&gt;&lt;a href=&quot;http://petname.mozdev.org/&quot; rel=&quot;nofollow&quot;&gt;http://petname.mozdev.org/&lt;/a&gt;&lt;/a&gt;
&lt;a href=&quot;http://passpet.org/&quot; rel=&quot;nofollow&quot;&gt;&lt;a href=&quot;http://passpet.org/&quot; rel=&quot;nofollow&quot;&gt;http://passpet.org/&lt;/a&gt;&lt;/a&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad to see some real experiments on this subject.  The results from this one were consistent with my pre-existing guesses.  My guess about the Pet Name Toolbar and Passpet is that they would protect users in almost all cases in a similar experiment.  (Disclaimer: I&#8217;m biased, of course &#8212; I&#8217;m partially responsible for some of the ideas behind those tools.)<br />
<a href="http://petname.mozdev.org/" rel="nofollow"></a><a href="http://petname.mozdev.org/" rel="nofollow">http://petname.mozdev.org/</a><br />
<a href="http://passpet.org/" rel="nofollow"></a><a href="http://passpet.org/" rel="nofollow">http://passpet.org/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://emergentchaos.com/archives/2007/02/why-johnny-cant-bank-safely.html/comment-page-1#comment-3204</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Tue, 06 Feb 2007 05:30:16 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2207#comment-3204</guid>
		<description>&quot;People are so used to computer systems crashing and their behavior deviating from the &#039;correct&#039; way that they seem to have developed a &#039;ignore&#039; rule to any deviant behavior.&quot;
This is a really great point.  Add in the reliability (from a user standpoint) of web systems and you have a perfect storm of low expectations.
There a few things to think about within context.
First, is that this group has an agenda.  It&#039;s &quot;usable security&quot;, which is fine, we all have our windmills to charge after (mine happens to be risk).  In their case, you &#039;re talking about coming up with a standard &quot;look and feel&quot; expectation across all platforms and across many vendors.  Then you need to start the education process for some 600 million (if you believe the numbers) users.  Daunting task, no?
Second, there&#039;s an assumption that the f.i.&#039;s _care_.  We&#039;re imparting a risk tolerance of zero losses on the f.i. when the fact of the matter is, they may or may not be willing to write off losses from phishing.
Third, there&#039;s an assumption that because it is possible that the user can be duped out of their username and password, that it will result in a successful compromise.  As you say, Chris,
&quot;The press is focusing on the Sitekey angle. The hook seems to be this: even when this highly-touted anti-phishing feature is absent (and a suspicious text box left in its place), people merrily supply their passwords. Therefore, Sitekey doesn&#039;t help.&quot;
I&#039;ve had the pleasure of doing risk analysis for some large banks on this very FFIEC guidance and many are putting multiple controls in place.  Also note that, put into practice, the sort of attack needed to be successful and creating a control failure in their scenario - while certainly possible, seems like a bit of work.  Threat agents tend to be economic with their resources, and even using site key alone limits the overall willingness of most but the absolutely determined threat source.
I thought Srijith&#039;s comment was interesting:
&quot;...He had explicitly mentioned that the system is so vulnerable to people&#039;s ignorant attitude that he for one did not see the ROI on the system. They had to still implement it because that was the &#039;in&#039; thing!&quot;
Jibes with some banks that I&#039;ve worked with.  The risk they have from Phishing losses may be tolerable, but the fines and judgments from the government they face from *not* buying a vendor solution amplifies their potential losses into an unacceptable range.
I happen to believe that one angle we the infosec community are forgetting is &quot;risk transference&quot;.  These days we&#039;re all enamored with free checking, and free online billpay.  I&#039;d be willing to pay a few bucks per month for the convenience if that money went as anti-phishing/identity theft insurance _as long as the insurer guaranteed timely replacement_.
I do believe that insurance and a few more controls added to products like SiteKey (defense in depth happens to be a good thing, some bank CISO&#039;s I&#039;ve had the pleasure of working with won&#039;t stop talking about Cyota) won&#039;t make the problem go away, but will make the potential impact tolerable for everyone involved:  bank, consumer and government.
</description>
		<content:encoded><![CDATA[<p>&#8220;People are so used to computer systems crashing and their behavior deviating from the &#8216;correct&#8217; way that they seem to have developed a &#8216;ignore&#8217; rule to any deviant behavior.&#8221;<br />
This is a really great point.  Add in the reliability (from a user standpoint) of web systems and you have a perfect storm of low expectations.<br />
There a few things to think about within context.<br />
First, is that this group has an agenda.  It&#8217;s &#8220;usable security&#8221;, which is fine, we all have our windmills to charge after (mine happens to be risk).  In their case, you &#8216;re talking about coming up with a standard &#8220;look and feel&#8221; expectation across all platforms and across many vendors.  Then you need to start the education process for some 600 million (if you believe the numbers) users.  Daunting task, no?<br />
Second, there&#8217;s an assumption that the f.i.&#8217;s _care_.  We&#8217;re imparting a risk tolerance of zero losses on the f.i. when the fact of the matter is, they may or may not be willing to write off losses from phishing.<br />
Third, there&#8217;s an assumption that because it is possible that the user can be duped out of their username and password, that it will result in a successful compromise.  As you say, Chris,<br />
&#8220;The press is focusing on the Sitekey angle. The hook seems to be this: even when this highly-touted anti-phishing feature is absent (and a suspicious text box left in its place), people merrily supply their passwords. Therefore, Sitekey doesn&#8217;t help.&#8221;<br />
I&#8217;ve had the pleasure of doing risk analysis for some large banks on this very FFIEC guidance and many are putting multiple controls in place.  Also note that, put into practice, the sort of attack needed to be successful and creating a control failure in their scenario &#8211; while certainly possible, seems like a bit of work.  Threat agents tend to be economic with their resources, and even using site key alone limits the overall willingness of most but the absolutely determined threat source.<br />
I thought Srijith&#8217;s comment was interesting:<br />
&#8220;&#8230;He had explicitly mentioned that the system is so vulnerable to people&#8217;s ignorant attitude that he for one did not see the ROI on the system. They had to still implement it because that was the &#8216;in&#8217; thing!&#8221;<br />
Jibes with some banks that I&#8217;ve worked with.  The risk they have from Phishing losses may be tolerable, but the fines and judgments from the government they face from *not* buying a vendor solution amplifies their potential losses into an unacceptable range.<br />
I happen to believe that one angle we the infosec community are forgetting is &#8220;risk transference&#8221;.  These days we&#8217;re all enamored with free checking, and free online billpay.  I&#8217;d be willing to pay a few bucks per month for the convenience if that money went as anti-phishing/identity theft insurance _as long as the insurer guaranteed timely replacement_.<br />
I do believe that insurance and a few more controls added to products like SiteKey (defense in depth happens to be a good thing, some bank CISO&#8217;s I&#8217;ve had the pleasure of working with won&#8217;t stop talking about Cyota) won&#8217;t make the problem go away, but will make the potential impact tolerable for everyone involved:  bank, consumer and government.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Srijith</title>
		<link>http://emergentchaos.com/archives/2007/02/why-johnny-cant-bank-safely.html/comment-page-1#comment-3203</link>
		<dc:creator>Srijith</dc:creator>
		<pubDate>Tue, 06 Feb 2007 01:03:21 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2207#comment-3203</guid>
		<description>I agree with what Orv has said. People are so used to computer systems crashing and their behavior deviating from the &#039;correct&#039; way that they seem to have developed a &#039;ignore&#039; rule to any deviant behavior.
Strangely enough, the results of the behavior will not come as a surprise to at least one bank I know of. A year or so ago, when I had the chance to talk to the one of the bigshots in the bank&#039;s security and fraud division, he had explicitly mentioned that the system is so vulnerable to people&#039;s ignorant attitude that he for one did not see the ROI on the system. They had to still implement it because that was the &#039;in&#039; thing!
Without saying, that bank will remain anonymous here :)
</description>
		<content:encoded><![CDATA[<p>I agree with what Orv has said. People are so used to computer systems crashing and their behavior deviating from the &#8216;correct&#8217; way that they seem to have developed a &#8216;ignore&#8217; rule to any deviant behavior.<br />
Strangely enough, the results of the behavior will not come as a surprise to at least one bank I know of. A year or so ago, when I had the chance to talk to the one of the bigshots in the bank&#8217;s security and fraud division, he had explicitly mentioned that the system is so vulnerable to people&#8217;s ignorant attitude that he for one did not see the ROI on the system. They had to still implement it because that was the &#8216;in&#8217; thing!<br />
Without saying, that bank will remain anonymous here :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Orv</title>
		<link>http://emergentchaos.com/archives/2007/02/why-johnny-cant-bank-safely.html/comment-page-1#comment-3202</link>
		<dc:creator>Orv</dc:creator>
		<pubDate>Tue, 06 Feb 2007 00:07:03 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2207#comment-3202</guid>
		<description>My suspicion is that people ignore a missing SiteKey because they&#039;ve been trained, through experience, to expect websites to be flakey.  How often have you gone to a popular site and had some of the images not load?  If you&#039;re like me, pretty frequently.
</description>
		<content:encoded><![CDATA[<p>My suspicion is that people ignore a missing SiteKey because they&#8217;ve been trained, through experience, to expect websites to be flakey.  How often have you gone to a popular site and had some of the images not load?  If you&#8217;re like me, pretty frequently.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
