<?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>Regulatory Reality &#187; id theft</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/regulatory-compliance/tag/id-theft/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance</link>
	<description>A SearchFinancialSecurity.com blog</description>
	<lastBuildDate>Wed, 06 Mar 2013 17:19:34 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Credit Card Breaches: The times they need a changin&#8217;</title>
		<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance/credit-card-breaches-the-times-they-need-a-changin/</link>
		<comments>http://itknowledgeexchange.techtarget.com/regulatory-compliance/credit-card-breaches-the-times-they-need-a-changin/#comments</comments>
		<pubDate>Sun, 29 Jul 2012 18:39:13 +0000</pubDate>
		<dc:creator>David Schneier</dc:creator>
				<category><![CDATA[ATM]]></category>
		<category><![CDATA[bank]]></category>
		<category><![CDATA[banking]]></category>
		<category><![CDATA[banks]]></category>
		<category><![CDATA[breach]]></category>
		<category><![CDATA[checking account]]></category>
		<category><![CDATA[community bank]]></category>
		<category><![CDATA[credit]]></category>
		<category><![CDATA[credit card]]></category>
		<category><![CDATA[cyber security]]></category>
		<category><![CDATA[data security]]></category>
		<category><![CDATA[evidence]]></category>
		<category><![CDATA[financial institutions]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[hacker]]></category>
		<category><![CDATA[hackers]]></category>
		<category><![CDATA[hacking]]></category>
		<category><![CDATA[id theft]]></category>
		<category><![CDATA[identity theft]]></category>
		<category><![CDATA[information security]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[oversight]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[personally identifiable informaiton]]></category>
		<category><![CDATA[PII]]></category>
		<category><![CDATA[regulation]]></category>
		<category><![CDATA[regulations]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[security breach]]></category>
		<category><![CDATA[theft]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/regulatory-compliance/?p=945</guid>
		<description><![CDATA[If my blogging about credit card breaches has a bit of a deja vu feel to it you&#8217;re not crazy, I last touched on it less than six months ago.  Sadly I was handed a new update this week in the form of my bank card being cancelled from right out underneath me again.   [...]]]></description>
				<content:encoded><![CDATA[<p>If my blogging about credit card breaches has a bit of a deja vu feel to it you&#8217;re not crazy, I last touched on it less than six months ago.  Sadly I was handed a new update this week in the form of my bank card being cancelled from right out underneath me again.   For those of you keeping score this would be the second time in 2012, a new personal record.</p>
<p>Here&#8217;s the sequence of events:</p>
<p>Wednesday morning I received an email alert from a company I use that my automatic monthly payment was declined.  Knowing full well it wasn&#8217;t a balance issue I assumed correctly that my bank had cancelled the card.  As I travel extensively and rely on the card exclusively I made my way to a local branch later that morning.  Along the way I called into the service center and confirmed my suspicions, that Visa informed the bank that my card was part of a range of numbers that was possibly exposed via a breach.  I asked if it was possible to learn the name of the offending vendor and was told (same as last time) that Visa doesn&#8217;t share that information.  As I am now a two-time victim it&#8217;s easy to spot the trend and hard to ignore the possibility that it might have involved the same vendor both times.  It wound up taking three visits to a branch to straighten me out and actually get a functioning card in my wallet.  The inconvenience is more than benign as I use the card in several places and will now need to make manual, one-off payments with the temporary card while awaiting the permanent card so that I can update the affected accounts.  By the time this is all said and done it will have resulted in my exhausting more than a half day of billable time trying to fix a problem I didn&#8217;t create.</p>
<p>A few things need to change.</p>
<ul>
<li>First, as part of the breach notification the card issuer needs to share with the cardholder the source of said breach.  I&#8217;ve been hit twice in six months, there&#8217;s a better than even chance that it involved the same vendor and/or processor and I deserve to know if that&#8217;s true.</li>
<li>Second, affected cardholders should receive status updates providing details about the breach including the suspected source, the techniques potentially used and a description of any follow-up actions including investigative and (hopefully) criminal prosecution.</li>
<li>Third, issuers need to have a better system in place to address breaches.  The fact that I have to overtly take action in order to replace the card is a joke.  I&#8217;m a billable resource and taking time out to wait to talk to a customer service representative results in loss of income; I&#8217;m being punished twice as a result.  I should have been offered the option to have a card overnighted to me or have been able to receive a card at any teller window and have it activated right there and then (I had to first activate at an ATM before I could use the temporary plastic).  The card replacement process needs to be streamlined.</li>
</ul>
<p>We collectively as an industry and a society need to accept that both identity and card theft is a mainstream occurrence and adjust accordingly.  Legislation is needed to further insulate the victims (like me) from any extended damage or inconvenience and ensure as smooth a process as possible to allow us to continue living our lives.  Because right now I don&#8217;t just feel like a victim, I feel like I&#8217;m being punished for being one and treated like I simply don&#8217;t matter.</p>
<p>Hey Washington, make the industry tell us what&#8217;s going on and to treat the consumers better!</p>
<p>Oh, and PCI Security Standards Council, how&#8217;s that framework working out for you?  I&#8217;m thinking the only one benefiting from your content are the practitioners making money by supporting it.</p>
<p>Seriously, something needs to change.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/regulatory-compliance/credit-card-breaches-the-times-they-need-a-changin/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Online identify theft: One victim&#8217;s story</title>
		<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance/identify-theft-one-victims-story/</link>
		<comments>http://itknowledgeexchange.techtarget.com/regulatory-compliance/identify-theft-one-victims-story/#comments</comments>
		<pubDate>Thu, 08 Apr 2010 14:24:58 +0000</pubDate>
		<dc:creator>David Schneier</dc:creator>
				<category><![CDATA[cyber security]]></category>
		<category><![CDATA[id theft]]></category>
		<category><![CDATA[information security]]></category>
		<category><![CDATA[password]]></category>
		<category><![CDATA[password theft]]></category>
		<category><![CDATA[phish]]></category>
		<category><![CDATA[phishing]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[scam]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[security awareness]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/regulatory-compliance/?p=329</guid>
		<description><![CDATA[Because whether it be the result of a successful phishing attempt, poor judgement or sloppy controls (e.g. post-it notes under the keyboard/phone/stapler, etc.) the number one entry point used by hackers to gain access to sensitive information remains password sharing.]]></description>
				<content:encoded><![CDATA[<p>Last month I blogged about a phishing attempt that landed in my inbox.  The email account belonged to someone named Rebecca Keen who I had never heard of before (or so I believed at the time).  As I was finishing writing that post, I received a follow-up email from the same person indicating that all was well, that her account was hacked and asked that no one respond to the original phishing email.  As it turned out, Rebecca Keen was actually someone in my extended network, courtesy of a PTA email thread that I was part of.  Because she used Yahoo mail and went with their default settings, all of her outbound email addresses were added to her address book and so I was one of her contacts.</p>
<p>Ms. Keen was kind enough to share her story with me so that I in turn could share it with you.</p>
<p>Her bad day started with the most basic error in judgement: She responded to a Yahoo-branded email requesting that she confirm her account information or else her account would be closed.  She said that &#8220;despite my initial instincts, I fell for it.&#8221;  It&#8217;s not hard to understand why.  Like most parents with school-age children, she has too much going on, depends on email to keep things moving and if she is anything like my wife, is of a mind to address things as they arise; she was a perfect target for a hacker.</p>
<p>Ms. Keen first became aware that she was about to have a bad day when she received an early morning phone call from a friend indicating they&#8217;d received an email from her asking for help.  She attempted to sign on to her Yahoo account to see what was going on but the hackers had changed her password and she was locked out.  She explained what happened next:</p>
<p>&#8220;<em>I had to wait for Yahoo to open at 9:00am to resolve the issue and regain access to my account.  Yahoo was extremely helpful and we were able to take the account back quite easily.  The representative I spoke with knew to advise me to confirm if any of my personal information had been changed, which it had.  An alternate email address had been added by the hacker as a way to retain control of my account even after I had gotten back in.  And my understanding is this is how they would continue to log in and check to see if anyone was actually trying to send me money.  If I did not know to delete this alternate email, the hackers could continue to monitor the account and target anyone asking me where to send the money</em>.&#8221;</p>
<p>I asked her if anyone actually attempted to send money or respond favorably to the hacker&#8217;s phishing attempt and fortunately no one had.  While she did receive a few calls and/or emails trying to confirm if the request was legitimate, because as Ms. Keen explained, &#8220;<em>They did indeed want to help me if I really needed it,&#8221;</em> no one actually took further action.  Apparently the majority of people who received the phishing attempt knew it was a hoax and ignored it (score one for security awareness in the private sector).</p>
<p>Was there a lesson learned from all of this for Ms. Keen to share?</p>
<p>&#8220;<em>Do not respond to emails requesting personal account information, no matter how reputable they may seem,&#8221; </em>she said.  &#8221;<em>As Yahoo explained, they would never request that sort of account information from me (they already have it and there is no need for it to be confirmed).&#8221;</em></p>
<p>To which I would add that you could easily replace the Yahoo name with literally any reputable business with which you have an online account.  I would also recommend that you print Rebecca Keen&#8217;s advice and tape it to your monitors and keyboards at both work and home for all to see.  Because whether it be the result of a successful phishing attempt, poor judgment or sloppy controls (e.g. sticky notes under the keyboard/phone/stapler, etc.) the number one entry point used by hackers to gain access to sensitive information remains password sharing.</p>
<p>Check back here next week. I have an interesting (if not scary) story to share about how some financial institutions are (mis)managing regulatory requirements.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/regulatory-compliance/identify-theft-one-victims-story/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
