<?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: Windows unsafe for online banking</title>
	<atom:link href="http://cuinnovators.com/blog/windows-unsafe-for-online-banking/feed/" rel="self" type="application/rss+xml" />
	<link>http://cuinnovators.com/blog/windows-unsafe-for-online-banking/</link>
	<description>At CU Innovators, we help credit unions, CUSO&#039;s, and service providers create meaningful products and services for their members and clients.</description>
	<lastBuildDate>Mon, 14 Mar 2011 17:53:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Greg</title>
		<link>http://cuinnovators.com/blog/windows-unsafe-for-online-banking/comment-page-1/#comment-662</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Mon, 16 Nov 2009 16:23:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cuemployee.com/?p=408#comment-662</guid>
		<description>As someone just passing through, I wanted to say that Windows attacks aren&#039;t just a function of Windows being popular. Linux is fundamentally more secure. Being open source means there&#039;s more eyes looking for problems, and when a problem is discovered the fact that antagonists can also see the code provides an incentive to fix the problem immediately.

Of course that doesn&#039;t mean it&#039;s practical to tell clients, &quot;Don&#039;t use windows!&quot; If they&#039;re not careful enough to avoid viruses/phishing then they&#039;re not going to be inconvenienced by using a live CD. Assume your users will mess up.</description>
		<content:encoded><![CDATA[<p>As someone just passing through, I wanted to say that Windows attacks aren&#8217;t just a function of Windows being popular. Linux is fundamentally more secure. Being open source means there&#8217;s more eyes looking for problems, and when a problem is discovered the fact that antagonists can also see the code provides an incentive to fix the problem immediately.</p>
<p>Of course that doesn&#8217;t mean it&#8217;s practical to tell clients, &#8220;Don&#8217;t use windows!&#8221; If they&#8217;re not careful enough to avoid viruses/phishing then they&#8217;re not going to be inconvenienced by using a live CD. Assume your users will mess up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robbie Wright</title>
		<link>http://cuinnovators.com/blog/windows-unsafe-for-online-banking/comment-page-1/#comment-661</link>
		<dc:creator>Robbie Wright</dc:creator>
		<pubDate>Thu, 12 Nov 2009 20:11:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cuemployee.com/?p=408#comment-661</guid>
		<description>Matt, thanks for the comment.  Most current multi-factor authentication mechanisms taken into account both IP and MAC address spoofing and thus do not rely solely on those identifications as a factor.  Generally, some type of encrypted cookie is placed on the hard drive instructing the FI to &quot;remember&quot; their computer.  Any security designed for online banking, e-trading, or anything else similar should make the assumption that the consumer&#039;s computer has already been compromised, by a key logger for example, and take that into account when designing their system.  Since MFA is still in &quot;generation 1&quot;, we&#039;re still learning many things.  Most MFA Q&amp;A&#039;s have questions that can be answered on Facebook or by looking through public records.  Personally, I believe for MFA to be truly secure, you have to have some other out-of-band technique for authenticate the person logging on.  I like the Verisign VIP program with either the key fob, or their iPhone and/or Blackberry app.  And yes, it is absolutely the job of the FI to take care of the security for their members, but members can also do things to dramatically decrease their likelihood of being compromised.</description>
		<content:encoded><![CDATA[<p>Matt, thanks for the comment.  Most current multi-factor authentication mechanisms taken into account both IP and MAC address spoofing and thus do not rely solely on those identifications as a factor.  Generally, some type of encrypted cookie is placed on the hard drive instructing the FI to &#8220;remember&#8221; their computer.  Any security designed for online banking, e-trading, or anything else similar should make the assumption that the consumer&#8217;s computer has already been compromised, by a key logger for example, and take that into account when designing their system.  Since MFA is still in &#8220;generation 1&#8243;, we&#8217;re still learning many things.  Most MFA Q&#038;A&#8217;s have questions that can be answered on Facebook or by looking through public records.  Personally, I believe for MFA to be truly secure, you have to have some other out-of-band technique for authenticate the person logging on.  I like the Verisign VIP program with either the key fob, or their iPhone and/or Blackberry app.  And yes, it is absolutely the job of the FI to take care of the security for their members, but members can also do things to dramatically decrease their likelihood of being compromised.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matt</title>
		<link>http://cuinnovators.com/blog/windows-unsafe-for-online-banking/comment-page-1/#comment-660</link>
		<dc:creator>matt</dc:creator>
		<pubDate>Wed, 11 Nov 2009 21:00:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cuemployee.com/?p=408#comment-660</guid>
		<description>In the article referenced it talks about the ability of these thieves to trick the FI into thinking it is a customer&#039;s usual computer/IP address. If that is one of the three lines of defense(something they are [computer identification]), and a keylogger can pick up either/or the second or third piece (something they know or something they have), then apparently it isn&#039;t all that &#039;nearly impossible&#039; because people are out there doing it.
I would have to argue that the responsibility for security lies in the hands of the FI, not the consumer. The point of a FI is to keep peoples money safe, that is why we pay them. Otherwise, I&#039;d put my money in a shoebox under my bed. It would be cheaper, anyway. (And apparently safer than online banking) I know its tough, but FI&#039;s need to stay one step ahead of the online security game, no matter the cost. Its their job.</description>
		<content:encoded><![CDATA[<p>In the article referenced it talks about the ability of these thieves to trick the FI into thinking it is a customer&#8217;s usual computer/IP address. If that is one of the three lines of defense(something they are [computer identification]), and a keylogger can pick up either/or the second or third piece (something they know or something they have), then apparently it isn&#8217;t all that &#8216;nearly impossible&#8217; because people are out there doing it.<br />
I would have to argue that the responsibility for security lies in the hands of the FI, not the consumer. The point of a FI is to keep peoples money safe, that is why we pay them. Otherwise, I&#8217;d put my money in a shoebox under my bed. It would be cheaper, anyway. (And apparently safer than online banking) I know its tough, but FI&#8217;s need to stay one step ahead of the online security game, no matter the cost. Its their job.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

