<?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: Hacking Business Accounts</title>
	<atom:link href="http://www.cryptosmith.com/archives/687/feed" rel="self" type="application/rss+xml" />
	<link>http://www.cryptosmith.com/archives/687</link>
	<description>Authentication, crypto, information security, and life with gadgets - Rick Smith</description>
	<lastBuildDate>Wed, 30 Jun 2010 12:30:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: Rick (l) Admin</title>
		<link>http://www.cryptosmith.com/archives/687/comment-page-1#comment-8208</link>
		<dc:creator>Rick (l) Admin</dc:creator>
		<pubDate>Fri, 24 Jul 2009 17:19:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.cryptosmith.com/?p=687#comment-8208</guid>
		<description>I have to say that the Bank of America phishers are pretty brazen - it&#039;s incredible to think they&#039;re telling people to install new public key certificates. 

The sad thing is that I know people will fall for it.

Actually, though, that makes the attack really too complex. It gives forewarning of where the domain will be for the actual attack.</description>
		<content:encoded><![CDATA[<p>I have to say that the Bank of America phishers are pretty brazen &#8211; it&#8217;s incredible to think they&#8217;re telling people to install new public key certificates. </p>
<p>The sad thing is that I know people will fall for it.</p>
<p>Actually, though, that makes the attack really too complex. It gives forewarning of where the domain will be for the actual attack.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nides1</title>
		<link>http://www.cryptosmith.com/archives/687/comment-page-1#comment-8207</link>
		<dc:creator>nides1</dc:creator>
		<pubDate>Fri, 24 Jul 2009 02:41:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.cryptosmith.com/?p=687#comment-8207</guid>
		<description>Kudos to banks for implementing &quot;multi-factor&quot; security requiring both A. User name/password AND B. private key for authentication ...  that one worked out well. ha..

I just had a computer forensic case come in last week that was exactly this.. Client&#039;s bank flagged 2 large wire transfers as fraudulent activity that almost wiped their account. They hire us to figure out the who/how/what @#$@ happened..! Make a long story short things turn into a malware analysis real quickly as I found a nasty little thing ~~ &quot;9129837.exe&quot; a trojan w/ root kit like characteristics. 

The phishing scheme that delivered the trojan was so advanced, the fake bank web site that prompted for the user/name password, actually validated the credentials against Verisign before it even bothered passing it along to the suspect!! Then it drops the executable (wiping some of its traces) scooping up digital signatures among some other goodies. 

If you ask me, based on what I have learned from you =) , this security is like putting the fresh made chocolate chip cookies and hundred dollar bills both in the same cookie jar.. then leaving the cover wide open. Kind of asking for it in my opinion. They need to incorporate other variables that are &quot;outside of the jar&quot; sort of speak. What happened to the good old RSA tokens.. ?

http://garwarner.blogspot.com/2009/06/bank-of-america-digital-certificates.html

[includes minor edit by blogger]</description>
		<content:encoded><![CDATA[<p>Kudos to banks for implementing &#8220;multi-factor&#8221; security requiring both A. User name/password AND B. private key for authentication &#8230;  that one worked out well. ha..</p>
<p>I just had a computer forensic case come in last week that was exactly this.. Client&#8217;s bank flagged 2 large wire transfers as fraudulent activity that almost wiped their account. They hire us to figure out the who/how/what @#$@ happened..! Make a long story short things turn into a malware analysis real quickly as I found a nasty little thing ~~ &#8220;9129837.exe&#8221; a trojan w/ root kit like characteristics. </p>
<p>The phishing scheme that delivered the trojan was so advanced, the fake bank web site that prompted for the user/name password, actually validated the credentials against Verisign before it even bothered passing it along to the suspect!! Then it drops the executable (wiping some of its traces) scooping up digital signatures among some other goodies. </p>
<p>If you ask me, based on what I have learned from you =) , this security is like putting the fresh made chocolate chip cookies and hundred dollar bills both in the same cookie jar.. then leaving the cover wide open. Kind of asking for it in my opinion. They need to incorporate other variables that are &#8220;outside of the jar&#8221; sort of speak. What happened to the good old RSA tokens.. ?</p>
<p><a href="http://garwarner.blogspot.com/2009/06/bank-of-america-digital-certificates.html" rel="nofollow">http://garwarner.blogspot.com/2009/06/bank-of-america-digital-certificates.html</a></p>
<p>[includes minor edit by blogger]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
