 




<?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>The Business-Technology Weave &#187; authenticating questions</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/business-technology/tag/authenticating-questions/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/business-technology</link>
	<description>Closing divides, directing purpose, and achieving results.</description>
	<lastBuildDate>Thu, 23 May 2013 17:30:17 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>A New Security Wrinkle</title>
		<link>http://itknowledgeexchange.techtarget.com/business-technology/a-new-security-wrinkle/</link>
		<comments>http://itknowledgeexchange.techtarget.com/business-technology/a-new-security-wrinkle/#comments</comments>
		<pubDate>Sat, 21 Aug 2010 16:35:36 +0000</pubDate>
		<dc:creator>David Scott</dc:creator>
				<category><![CDATA[authenticating questions]]></category>
		<category><![CDATA[authentication]]></category>
		<category><![CDATA[authentication questions]]></category>
		<category><![CDATA[bank security]]></category>
		<category><![CDATA[data breach]]></category>
		<category><![CDATA[data security]]></category>
		<category><![CDATA[data theft]]></category>
		<category><![CDATA[financial security]]></category>
		<category><![CDATA[ID theft]]></category>
		<category><![CDATA[info security]]></category>
		<category><![CDATA[information security]]></category>
		<category><![CDATA[security plans]]></category>
		<category><![CDATA[security policies]]></category>
		<category><![CDATA[security policy]]></category>
		<category><![CDATA[security question]]></category>
		<category><![CDATA[security questions]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/business-technology/a-new-security-wrinkle/</guid>
		<description><![CDATA[  Something interesting happened to me the other day.  There was an unauthorized debit made to my checking account in the amount of $150 and some change by an entity that was unknown to me.  I was reasonably certain that I hadn’t conducted any business with any such business. These days, as most here probably know, [...]]]></description>
				<content:encoded><![CDATA[<p class="MsoNormal" style="margin: 0in 0in 10pt"> </p>
<p class="MsoNormal" style="margin: 0in 0in 10pt"><span style="font-family: &quot;Verdana&quot;,&quot;sans-serif&amp;quot"><span style="font-size: small">Something interesting happened to me the other day.<span>  </span>There was an unauthorized debit made to my checking account in the amount of $150 and some change by an entity that was unknown to me.<span> </span><span> </span>I was reasonably certain that I hadn’t conducted any business with any such business.</span></span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt"><span style="font-family: &quot;Verdana&quot;,&quot;sans-serif&amp;quot"><span style="font-size: small">These days, as most here probably know, breaches involving bank accounts usually involve modest amounts; the “breachers” hope that this allows an unauthorized withdrawal to fly under the radar, and they’d rather hit several accounts for these modest amounts than to hit one account for a massive withdrawal – sure to garner unwanted attention and, hopefully (for us), thwart.</span></span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt"><span style="font-family: &quot;Verdana&quot;,&quot;sans-serif&amp;quot"><span style="font-size: small">When I called my bank of 30+ years to report an unauthorized transaction, the initial contact was with a representative who was concerned with telling me what he (and the bank) <em>could not</em> do for me – their customer.<span>  </span>He explained that he could “delete” the transaction, but that the offending party could simply resubmit.<span>  </span>He suggested that I call the entity and discuss the transaction with them.<span>  </span>I patiently explained that they might not be the originating party – that it could be someone spinning the unauthorized transaction through them.<span>  </span>His counsel was to contact them none-the-less.<span>  </span>Having already Googled them, I called…</span></span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt"><span style="font-family: &quot;Verdana&quot;,&quot;sans-serif&amp;quot"><span style="font-size: small">That entity, a web services company, was sympathetic – and of course, in order to validate whether I was a customer or not, they wanted… my name and address; the last six digits of the debit card; the three security digits on the back – as well as other things.<span>  </span>All of this to “look me up” in determining if I was even a customer of theirs – before getting to the question of the transaction.</span></span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt"><span style="font-family: &quot;Verdana&quot;,&quot;sans-serif&amp;quot"><span style="font-size: small">My question to them was – how do I know <em><span style="text-decoration: underline">you</span></em> are who you say you are?<span>  </span>And, how do I know you’re a legitimate company, and not simply gleaning personal details and financial authentication information from people?<span>  </span>Fortunately, they were ultimately able to determine that I was not a customer with my name, primarily, and that they had not issued the charge to my account.</span></span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt"><span style="font-family: &quot;Verdana&quot;,&quot;sans-serif&amp;quot"><span style="font-size: small">I called my bank back, and I’d like to credit the second representative with some intelligence.<span>  </span>He deleted the transaction and, in his words, “blew the bridge” to the card by cancelling the card and reissuing a new one.<span>  </span><em>Thank you</em>.<span>  </span>I wish I had thought of it.<span>  </span>But that first rep had me thinking that the transaction had to be honored by the bank.<span>  </span>Hmmm… after all, what good is my word?<span>  </span>I’m just a customer in good standing for more than 30 years.</span></span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt"><span style="font-family: &quot;Verdana&quot;,&quot;sans-serif&amp;quot"><span style="font-size: small">But – my question to you, dear reader, is… when you call your bank, or any business such as the one I had to contact, or any agency that wants things such as address, last four of SSN, mother’s maiden name, birth date &#8211; and essentially wants exposure of all sorts of security data and answers to security questions:<span>  </span>How do you know to whom you are speaking?<span>  </span>What is your security question to <em>them</em>?- with attendant, and correct, security answer(s) as provided to you for your comfort and identification of <em><span style="text-decoration: underline">them</span></em>?<span>  </span></span></span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt"><span style="font-family: &quot;Verdana&quot;,&quot;sans-serif&amp;quot"><span style="font-size: small">Phone numbers can be hijacked – what if, when you call your bank’s number, you instead reach a nefarious party out to harm you?<span>  </span>Consider:<span>  </span>What if your bank’s web page is taken over, or substituted, and you dial a number posted there that goes to a hacking agency out to grab your details, and your money?</span></span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt"><span style="font-family: &quot;Verdana&quot;,&quot;sans-serif&amp;quot"><span style="font-size: small">As breaches and thefts become ever more clever, watch for breaches to be mere springboards:<span>  </span>A theft that causes an individual to launch a call, which in-turn may be hijacked into some spurious realm for further gleaning of confidential information.<span>  </span></span></span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt"><span style="font-family: &quot;Verdana&quot;,&quot;sans-serif&amp;quot"><span style="font-size: small">Security needs to be a two-way street.<span>  </span>Presently, in these circumstances, it is one-way and therefore only mounted <em>half</em>-way.<span>  </span>True security demands a face-to-face meeting in a physical location, to establish security questions that the bank, for example, must answer correctly to YOUR satisfaction when dealing with a disembodied voice on the phone.<span>  </span></span></span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt"><span style="font-family: &quot;Verdana&quot;,&quot;sans-serif&amp;quot"><span style="font-size: small">Of course, even that authenticating standard can be breached, but every layer helps.</span></span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt"><span style="font-size: small"><strong><span style="font-family: &quot;Verdana&quot;,&quot;sans-serif&amp;quot">August 21<sup>st</sup></span></strong><span style="font-family: &quot;Verdana&quot;,&quot;sans-serif&amp;quot">:<span>  </span>On this date in 1841, John Hampson patents the venetian blind.<span> </span></span></span></p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/business-technology/a-new-security-wrinkle/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
