 




<?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>Irregular Expressions &#187; banking security</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/Irregular-Expressions/tag/banking-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/Irregular-Expressions</link>
	<description>Insight into current security related events and exploits, including virtualization security and tips.</description>
	<lastBuildDate>Sun, 28 Apr 2013 08:00:32 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Protecting online banking &#8211; Part 4</title>
		<link>http://itknowledgeexchange.techtarget.com/Irregular-Expressions/protecting-online-banking-part-4/</link>
		<comments>http://itknowledgeexchange.techtarget.com/Irregular-Expressions/protecting-online-banking-part-4/#comments</comments>
		<pubDate>Tue, 24 Jan 2012 05:46:43 +0000</pubDate>
		<dc:creator>Dan O'Connor</dc:creator>
				<category><![CDATA[banking security]]></category>
		<category><![CDATA[online banking security]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/Irregular-Expressions/protecting-online-banking-part-4/</guid>
		<description><![CDATA[I just want to wrap up my thoughts on this.  This is not going to stop every type of attack, there are a few ways to get around this type of authentication method.  The first one that comes to mind is using the authenticated session that the user has created for you already and not waiting to [...]]]></description>
				<content:encoded><![CDATA[<p>I just want to wrap up my thoughts on this.  This is not going to stop every type of attack, there are a few ways to get around this type of authentication method.  The first one that comes to mind is using the authenticated session that the user has created for you already and not waiting to try and log in later.  While saying that, something is better then nothing.  This may not work against a determined targeted attack but at least you wont be low hanging fruit.</p>
<p>I tried to find a few FI&#8217;s that I could point you to that had OTP listed as a two factor method, but I just turned up a bunch of old white papers.  I did find mention of FI&#8217;s in Germany that used paper for the OTP and various ones using SMS.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/Irregular-Expressions/protecting-online-banking-part-4/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Protecting online banking &#8211; Part 3</title>
		<link>http://itknowledgeexchange.techtarget.com/Irregular-Expressions/protecting-online-banking-part-3/</link>
		<comments>http://itknowledgeexchange.techtarget.com/Irregular-Expressions/protecting-online-banking-part-3/#comments</comments>
		<pubDate>Mon, 23 Jan 2012 06:08:27 +0000</pubDate>
		<dc:creator>Dan O'Connor</dc:creator>
				<category><![CDATA[banking security]]></category>
		<category><![CDATA[online banking security]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/Irregular-Expressions/protecting-online-banking-part-3/</guid>
		<description><![CDATA[My personal choice would be a OTP ( One Time Pad ) setup. The setup should be fairly simple; Create a system to create random sets of 8 ( or more ) character pads, they should be random but careful to make it easy for users to separate 0 and O.  Maybe only upper and lower case [...]]]></description>
				<content:encoded><![CDATA[<p>My personal choice would be a OTP ( One Time Pad ) setup.</p>
<p>The setup should be fairly simple;</p>
<ul>
<li>Create a system to create random sets of 8 ( or more ) character pads, they should be random but careful to make it easy for users to separate 0 and O.  Maybe only upper and lower case with no numbers?</li>
<li>These should not be guessable or form any sort of pattern, so maybe use a hashing function. Just don&#8217;t hash 1, 2, 3, 4.</li>
<li>When creating the pad one copy is associated with the user and stored as part of the authentication system and the other is handed off.</li>
<li>The system should know when a user is nearing the end of the current pad and prompt for the creation of the next.</li>
</ul>
<div></div>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/Irregular-Expressions/protecting-online-banking-part-3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Protecting online banking &#8211; Part 2</title>
		<link>http://itknowledgeexchange.techtarget.com/Irregular-Expressions/protecting-online-banking-part-2/</link>
		<comments>http://itknowledgeexchange.techtarget.com/Irregular-Expressions/protecting-online-banking-part-2/#comments</comments>
		<pubDate>Thu, 19 Jan 2012 22:01:32 +0000</pubDate>
		<dc:creator>Dan O'Connor</dc:creator>
				<category><![CDATA[banking security]]></category>
		<category><![CDATA[online banking security]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/Irregular-Expressions/protecting-online-banking-part-2/</guid>
		<description><![CDATA[I have come down to a handful of solutions that might do the trick. 1) Use a security key fob Pros - Adds that something you have element to the authentication system. - Unless the FOB is stolen unauthorized access to the account should be fairly difficult. ( This has happened before with RSA and [...]]]></description>
				<content:encoded><![CDATA[<p>I have come down to a handful of solutions that might do the trick.</p>
<p>1) Use a security key fob</p>
<p><strong>Pros</strong></p>
<p>- Adds that something you have element to the authentication system.</p>
<p>- Unless the FOB is stolen unauthorized access to the account should be fairly difficult. ( This has happened before with RSA and some defence contrators. )</p>
<p>- Cheaper then theft.</p>
<p><strong>Cons</strong></p>
<p>- These items can be pricey.</p>
<p>- They can get lost and increase the cost of owner ship.</p>
<p>- End users may find these complex.</p>
<p>2) SMS or smart phone app</p>
<p><strong>Pros</strong></p>
<p>- Something you have.</p>
<p>- fairly inexpensive.</p>
<p>- If the device is lost the destination number could be updated in person.</p>
<p><strong>Cons</strong></p>
<p>- Not everyone has a smart phone or cell.</p>
<p>- There could be costs encouraged by the user to receive the sms messages.</p>
<p>3) One Time Pad ( OTP )</p>
<p><strong>Pros</strong></p>
<p>- Cheap, real cheap.</p>
<p>- Something you have.</p>
<p>- Could be created in house.</p>
<p>- Very simple and easily managed by a end user.  Compared to other solutions it&#8217;s not very complex.</p>
<p><strong>Cons</strong></p>
<p>- Can be created in house, you want to make sure this is done correctly.</p>
<p>- Users still may find this complex.</p>
<p>There is some institutions already doing these things, I can hardly claim them as my own.  Also I am sure I have left some off the list.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/Irregular-Expressions/protecting-online-banking-part-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
