<?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>Tricerion Security Blog &#187; Vulnerabilities</title>
	<atom:link href="http://blog.tricerion.com/category/vulnerabilities/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tricerion.com</link>
	<description></description>
	<lastBuildDate>Tue, 17 Jan 2012 14:02:41 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Zappos insight, direct from Twitter</title>
		<link>http://blog.tricerion.com/2012/01/zappos-insight-direct-from-twitter/</link>
		<comments>http://blog.tricerion.com/2012/01/zappos-insight-direct-from-twitter/#comments</comments>
		<pubDate>Tue, 17 Jan 2012 14:02:41 +0000</pubDate>
		<dc:creator>Eugen</dc:creator>
				<category><![CDATA[Cyberthieves]]></category>
		<category><![CDATA[Phishing]]></category>
		<category><![CDATA[Retail]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[Vulnerabilities]]></category>

		<guid isPermaLink="false">http://blog.tricerion.com/?p=151</guid>
		<description><![CDATA[Scanning Twitter for responses to the Zappos breach, we have a few favourites that are awfully telling: From @jjmartucci: I bet 99% of the stolen Zappos passwords were &#8220;shoes&#8221;. // Fact: most passwords are frighteningly easy to guess. We bet that those passwords aren&#8217;t &#8220;shoes&#8221; at all, but rather &#8220;password&#8221;, &#8220;abc123&#8243; and others from the [...]]]></description>
			<content:encoded><![CDATA[<p>Scanning Twitter for responses to the Zappos breach, we have a few favourites that are awfully telling:</p>
<p>From @jjmartucci: I bet 99% of the stolen Zappos passwords were &#8220;shoes&#8221;. // Fact: most passwords are frighteningly easy to guess. We bet that those passwords aren&#8217;t &#8220;shoes&#8221; at all, but rather &#8220;password&#8221;, &#8220;abc123&#8243; and others from the list of too-often-used passwords. Alphanumeric passwords just aren&#8217;t as safe as we think they are.</p>
<p>From @dombenoit: receive @zappos email asking to change password after hack, can&#8217;t change password because i&#8217;m outside the US&#8230; good thinking guys.// Fact: American may be in the center of some poorly conceived maps, but it is not the center of the universe. Corporations, don&#8217;t forget that the majority of the world lives outside of the US, and they need customer service too.</p>
<p>From @kimfouroffive: In order to change my Zappos password I would have to remember my Zappos password and that&#8217;s not going to happen. // Fact: Tons of consumers rely on the &#8220;cookies&#8221; on their computer to remember their passwords. There&#8217;s no need to delve into all the reasons that&#8217;s poor practice. But let&#8217;s face it &#8211; many users either don&#8217;t remember their passwords, or they have them written on a post-it in their desk.</p>
<p>From @Kevbo1111: Wait, you&#8217;re telling me a company whose office looks like this, has lax security? #Zappos http://pic.twitter.com/pr9SrfCF // Fact: If we could see inside the workings of all the places that hold our &#8216;secure data&#8217; we wouldn&#8217;t feel so secure.</p>
<p>From @Tuna999: Im confused, is that zappos security email real? // Fact: This is actually a very smart question, that many wouldn&#8217;t think to ask (or research before clicking through). A phishing attempt can look much the same, and confuse consumers into handing over their credentials to fraudulent sites.</p>
<p>From @justAK: Had someone try to acces my bank info a few times. Could this be cause of the #zappos #hacking ? I hope not. #worried // Fact: Too many users have the same password for all online accounts. It&#8217;s not hard to believe that hackers would use information from one site to try to access others.</p>
<p>From @andishehnouraee: Zappos hacked, &#8220;sensitive&#8221; customer info stolen. Before I&#8217;m outed, I&#8217;ll confess here: I&#8217;m a size 12. // Fact: sensitive information is a lot more sensitive than shoe size. That said, great sense of humor!</p>
<p>From @Tontiella: Zappos why are your accounts being hacked into?? Who is not doing their job to prevent this?  // Fact: Strong security measures are fabled to be more expensive than responding to data breaches. Time will tell how this affects Zappos in the long term, but let&#8217;s just say that resetting passwords doesn&#8217;t instill a sense of trust. (And, for the record, strong mutual authentication is well worth the investment)</p>



		<!-- Added by WP-DragToShare-eXtended Plugin -->
		<script type="text/javascript">
			dtsv.dtse_post_151_permalink = 'http://blog.tricerion.com/2012/01/zappos-insight-direct-from-twitter/';
			dtsv.dtse_post_151_title = 'Zappos insight, direct from Twitter';
		</script>
		<!-- End of WP-DragToShare-eXtended Plugin -->]]></content:encoded>
			<wfw:commentRss>http://blog.tricerion.com/2012/01/zappos-insight-direct-from-twitter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Zappos breach: What not to do</title>
		<link>http://blog.tricerion.com/2012/01/zappos-breach-what-not-to-do/</link>
		<comments>http://blog.tricerion.com/2012/01/zappos-breach-what-not-to-do/#comments</comments>
		<pubDate>Mon, 16 Jan 2012 14:37:29 +0000</pubDate>
		<dc:creator>Eugen</dc:creator>
				<category><![CDATA[Banking]]></category>
		<category><![CDATA[Cyberthieves]]></category>
		<category><![CDATA[Phishing]]></category>
		<category><![CDATA[Retail]]></category>
		<category><![CDATA[Vulnerabilities]]></category>

		<guid isPermaLink="false">http://blog.tricerion.com/?p=148</guid>
		<description><![CDATA[Zappos has remained tight-lipped about the nature of their data breach this week. As many as 24 million consumer accounts may have been accessed through an attack on their server in Kentucky. That is as detailed as they&#8217;re willing to go. Full credit card numbers were not stolen, since those were stored separately. It would [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignright dtse-img dtse-post-148" title="Zappos" src="http://buildinternet.s3.amazonaws.com/images/more-popular-logos/zappos_logo.jpg" alt="" width="270" height="203" />Zappos has remained tight-lipped about the nature of their data breach this week. As many as 24 million consumer accounts may have been accessed through an attack on their server in Kentucky. That is as detailed as they&#8217;re willing to go. Full credit card numbers were not stolen, since those were stored separately. It would seem that they expect that security measure to reassure consumers of their multi-tier, rock solid security system, but as far as we&#8217;re concerned, perceived security does not equal actual security, and the breach that disclosed passwords for user accounts breaches actual security.</p>
<p>Some facts that the typical ecommerce consumer should be aware of:</p>
<ol>
<li>Too many users have a single set of login credentials (username and password) for all their online accounts. That means, when someone gets their info from Zappos, they can use it to access Facebook, Amazon, online magazine subscriptions, PayPal, email, gaming sites, online banking, and more.</li>
<li>&#8220;Fixing&#8221; an alphanumeric password breach with new alphanumeric passwords doesn&#8217;t actually &#8220;fix&#8221; anything. If I know the guy trying to break into my house is a locksmith, I don&#8217;t just cut a new key &#8211; I install security measures that a locksmith isn&#8217;t an expert in.</li>
<li>Zappos has chosen the path of least resistance &#8211; deploying consumers themselves to fix the breach. Zappos users have to follow instructions given in an email (which may have gone into spam folders), change their passwords, and email Zappos with any questions or concerns. Anyone with an email address they don&#8217;t regularly check, an overactive spam filter, or the &#8216;grandma&#8217; syndrome (not computer savvy, and likely suspicious of &#8216;official&#8217; email communication) may fall through the cracks.</li>
<li>Changing the Zappos password doesn&#8217;t change all the other similar or identical passwords the consumer uses on other accounts, leaving their customer base open to further attack elsewhere.</li>
</ol>
<p>One of the key takeaways from this is that ecommerce systems should not be based on &#8216;security&#8217; systems that rely on users&#8217; unreliable alertness. Users expect the systems that hold their sensitive information to bear the burden of iron-clad security for their data. Strong, two-factor authentication systems aren&#8217;t just an option in today&#8217;s online environment &#8211; they are where the market is heading by default and by necessity. Zappos has shown us exactly how not to handle a data breach. Of course, if more systems used strong mutual authentication, we&#8217;d see decidedly fewer breaches like the one this weekend.</p>



		<!-- Added by WP-DragToShare-eXtended Plugin -->
		<script type="text/javascript">
			dtsv.dtse_post_148_permalink = 'http://blog.tricerion.com/2012/01/zappos-breach-what-not-to-do/';
			dtsv.dtse_post_148_title = 'Zappos breach: What not to do';
		</script>
		<!-- End of WP-DragToShare-eXtended Plugin -->]]></content:encoded>
			<wfw:commentRss>http://blog.tricerion.com/2012/01/zappos-breach-what-not-to-do/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Safeguarding, as attacks evolve</title>
		<link>http://blog.tricerion.com/2011/12/safeguarding-as-attacks-evolve/</link>
		<comments>http://blog.tricerion.com/2011/12/safeguarding-as-attacks-evolve/#comments</comments>
		<pubDate>Fri, 09 Dec 2011 14:41:23 +0000</pubDate>
		<dc:creator>Eugen</dc:creator>
				<category><![CDATA[Phishing]]></category>
		<category><![CDATA[Trends]]></category>
		<category><![CDATA[Vulnerabilities]]></category>

		<guid isPermaLink="false">http://blog.tricerion.com/?p=140</guid>
		<description><![CDATA[These days it seems that while hackers evolve with trends in technology, the general computer user is no more identity savvy than he was before Facebook made identities a virtual open book. Data breaches, hacks, and attempted hacks are in the news regularly, and yet Joe Consumer still uses &#8220;password&#8221; or &#8220;password1&#8243; for all his [...]]]></description>
			<content:encoded><![CDATA[<p>These days it seems that while hackers evolve with trends in technology, the general computer user is no more identity savvy than he was before Facebook made identities a virtual open book. Data breaches, hacks, and attempted hacks are in the news regularly, and yet Joe Consumer still uses &#8220;password&#8221; or &#8220;password1&#8243; for all his accounts, keeps them written in a little black book, and uses FourSquare, Facebook, and Twitter to tell would-be burglars exactly how far from home he is at any given time.</p>
<p>Those in the business know that December is a notoriously risk-ridden time for identity theft, as hackers take advantage of escalating ecommerce around the holidays. How are merchants and business owners to safeguard identity when customers like Joe Consumer make identity theft child&#8217;s play? One of the keys in identity protection is anticipating the evolution of technology. Responding reactively to current and past attacks only leaves users highly vulnerable.</p>
<p>A recent two-pronged <a href="http://www.theregister.co.uk/2011/10/11/rsa_securid_breach_keynote/" target="_blank">RSA security breach </a>hows just how deep hackers will go, uniting efforts across nations to attack secure data. Tokens are out of reach for many, with their high cost of maintenance. SMS authentication is cumbersome at best, and the most user-friendly solutions require nothing other than the user himself. That said, biometrics are excessively expensive.</p>
<p>Strong mutual authentication systems, like that of Tricerion, offer secure protection against assault while maintaining accessible affordability in comparison with biometric or token-based systems.  Picture-passwords have been found more memorable and harder to crack than alpha numeric passwords in <a href="http://etd.ohiolink.edu/view.cgi?acc_num=bgsu1194297698" target="_blank">multiple studies</a> . Details on our authentication systems can be found on <a href="http://www.tricerion.com/" target="_blank">our website</a>.</p>



		<!-- Added by WP-DragToShare-eXtended Plugin -->
		<script type="text/javascript">
			dtsv.dtse_post_140_permalink = 'http://blog.tricerion.com/2011/12/safeguarding-as-attacks-evolve/';
			dtsv.dtse_post_140_title = 'Safeguarding, as attacks evolve';
		</script>
		<!-- End of WP-DragToShare-eXtended Plugin -->]]></content:encoded>
			<wfw:commentRss>http://blog.tricerion.com/2011/12/safeguarding-as-attacks-evolve/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>1024-bit RSA encryption cracked by carefully starving CPU of electricity</title>
		<link>http://blog.tricerion.com/2010/03/1024-bit-rsa-encryption-cracked-by-carefully-starving-cpu-of-electricity/</link>
		<comments>http://blog.tricerion.com/2010/03/1024-bit-rsa-encryption-cracked-by-carefully-starving-cpu-of-electricity/#comments</comments>
		<pubDate>Tue, 09 Mar 2010 15:01:04 +0000</pubDate>
		<dc:creator>Eugen</dc:creator>
				<category><![CDATA[Banking]]></category>
		<category><![CDATA[Phishing]]></category>
		<category><![CDATA[Vulnerabilities]]></category>

		<guid isPermaLink="false">http://blog.tricerion.com/?p=132</guid>
		<description><![CDATA[Several researchers the University of Michigan have succeeded in cracking  the RSA security technology which protects all ecommerce and online banking transactions. The university scientists found that they could deduce tiny pieces of a private key by injecting slight fluctuations in a device&#8217;s power supply as it was processing encrypted messages. In a little more [...]]]></description>
			<content:encoded><![CDATA[<p>Several researchers the University of Michigan have succeeded in cracking  the RSA security technology which protects all ecommerce and online banking transactions.</p>
<p>The university scientists found that they could deduce tiny pieces of a private key by injecting slight fluctuations in a device&#8217;s power supply as it was processing encrypted messages. In a little more than 100 hours, they fed the device enough &#8220;transient faults&#8221; that they were able to assemble the entirety of its 1024-bit key.</p>
<p><a href="http://blog.tricerion.com/wp-content/uploads/2010/03/3-8-10-rsahardwarefaultattackgraphic.jpg"><img class="aligncenter size-full wp-image-133 dtse-img dtse-post-132" title="1024-bit RSA encryption cracked" src="http://blog.tricerion.com/wp-content/uploads/2010/03/3-8-10-rsahardwarefaultattackgraphic.jpg" alt="" width="544" height="352" /></a></p>
<blockquote><p>&#8220;The RSA algorithm gives security under the assumption that as long as the private key is private, you can&#8217;t break in unless you guess it. We&#8217;ve shown that that&#8217;s not true,&#8221; said Valeria Bertacco, an associate professor in the Department of Electrical Engineering and Computer Science.</p></blockquote>
<p><a href="http://www.ns.umich.edu/htdocs/releases/story.php?id=7551" target="_blank">Read the full statement here</a>.</p>



		<!-- Added by WP-DragToShare-eXtended Plugin -->
		<script type="text/javascript">
			dtsv.dtse_post_132_permalink = 'http://blog.tricerion.com/2010/03/1024-bit-rsa-encryption-cracked-by-carefully-starving-cpu-of-electricity/';
			dtsv.dtse_post_132_title = '1024-bit RSA encryption cracked by carefully starving CPU of electricity';
		</script>
		<!-- End of WP-DragToShare-eXtended Plugin -->]]></content:encoded>
			<wfw:commentRss>http://blog.tricerion.com/2010/03/1024-bit-rsa-encryption-cracked-by-carefully-starving-cpu-of-electricity/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

