 




<?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; personally identifiable informaiton</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/regulatory-compliance/tag/personally-identifiable-informaiton/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>Are banks unfairly scrutinized?</title>
		<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance/are-banks-unfairly-scrutinized/</link>
		<comments>http://itknowledgeexchange.techtarget.com/regulatory-compliance/are-banks-unfairly-scrutinized/#comments</comments>
		<pubDate>Mon, 22 Oct 2012 14:09:17 +0000</pubDate>
		<dc:creator>David Schneier</dc:creator>
				<category><![CDATA[ACH]]></category>
		<category><![CDATA[assess]]></category>
		<category><![CDATA[assessment]]></category>
		<category><![CDATA[assessments]]></category>
		<category><![CDATA[Audit]]></category>
		<category><![CDATA[auditor]]></category>
		<category><![CDATA[audits]]></category>
		<category><![CDATA[banking]]></category>
		<category><![CDATA[banks]]></category>
		<category><![CDATA[business]]></category>
		<category><![CDATA[CISA]]></category>
		<category><![CDATA[CISO]]></category>
		<category><![CDATA[community bank]]></category>
		<category><![CDATA[compliance]]></category>
		<category><![CDATA[credit unions]]></category>
		<category><![CDATA[CU]]></category>
		<category><![CDATA[exam]]></category>
		<category><![CDATA[examination]]></category>
		<category><![CDATA[examinations]]></category>
		<category><![CDATA[examiner]]></category>
		<category><![CDATA[examiners]]></category>
		<category><![CDATA[exams]]></category>
		<category><![CDATA[FFIEC]]></category>
		<category><![CDATA[financial institutions]]></category>
		<category><![CDATA[general controls]]></category>
		<category><![CDATA[GLBA]]></category>
		<category><![CDATA[identify theft]]></category>
		<category><![CDATA[identity theft]]></category>
		<category><![CDATA[information security]]></category>
		<category><![CDATA[information security office]]></category>
		<category><![CDATA[Information Technology General Controls]]></category>
		<category><![CDATA[internal audit]]></category>
		<category><![CDATA[internal controls]]></category>
		<category><![CDATA[ITGC]]></category>
		<category><![CDATA[NPPI]]></category>
		<category><![CDATA[observations]]></category>
		<category><![CDATA[oversight]]></category>
		<category><![CDATA[personally identifiable informaiton]]></category>
		<category><![CDATA[PII]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[risk assess]]></category>
		<category><![CDATA[risk assessment]]></category>
		<category><![CDATA[risk assessments]]></category>
		<category><![CDATA[risk management]]></category>
		<category><![CDATA[risk-based]]></category>
		<category><![CDATA[risks]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/regulatory-compliance/?p=993</guid>
		<description><![CDATA[A few years back when I first cut over to working somewhat exclusively with financial institutions I memorized an elevator speech that still somewhat defines who I am and what I do professionally.  Part of the speech pointed out that my firm helped &#8220;banks and credit unions meet regulatory compliance with respect to GLBA 501(b) [...]]]></description>
				<content:encoded><![CDATA[<p>A few years back when I first cut over to working somewhat exclusively with financial institutions I memorized an elevator speech that still somewhat defines who I am and what I do professionally.  Part of the speech pointed out that my firm helped &#8220;banks and credit unions meet regulatory compliance with respect to GLBA 501(b) and NCUA Part 748 A&amp;B&#8221;.  To this day when anyone inquires as to what I do for a living this surfaces in some form as an answer.</p>
<p>Truth be told, while I&#8217;ve spent somewhere near seventy-five percent of my time over the past ten years working for financial institutions I&#8217;ve also done a fair amount of work for insurance companies, mostly centered on SOX with occasional diversions into general risk assessment work.  The drivers in the insurance industry are different in terms of oversight and requirements and so the volume of work isn&#8217;t nearly the same.  But that by itself begs a question: Why isn&#8217;t the insurance industry as regulated as financial institutions?</p>
<p>I&#8217;ve now done major audit and assurance work for financial institutions, insurance companies and health care providers and for most of them the risk profile is almost identical in terms of non-public personal information.  So why isn&#8217;t the level of scrutiny equal across all three of them?  While some might start spouting about how it is, about how states routinely audit insurance companies and how the health care industry has to comply with HIPAA the truth is that banks and credit unions are held to a much higher degree of accountability than any other vertical.  Why is that?</p>
<p>I&#8217;m fond of routinely, almost incessantly beating the drum about how it&#8217;s all about the risk.  I get my initial client opportunities because I have a deep resume with relevant experience but I generate repeat business because I tend to whittle things down to what matters most both to my clients and to their oversight providers (auditors and examiners alike).  Compliance exists because risks need to be addressed &#8211; if the risks aren&#8217;t credible or likely the work should be adjusted to reflect that.  But where the risks are real they&#8217;re really real.  The type  of data shared with an insurance company is in many ways even more sensitive than anything shared with a bank and most of what&#8217;s shared with insurance companies is also shared with health care providers.  Yet there&#8217;s no true Federal oversight for the insurance industry and HIPAA is about as much of a toothless tiger as anything I&#8217;ve ever encountered.</p>
<p>I recently completed a boatload of documentation to get my family on a new health insurance plan.  I turned over every piece of sensitive information I have for every member of my family minus my bank account information because that&#8217;s what was required.  I had to provide all of this online and follow that up by sending them an impressive array of hard-copy documents with even more sensitive information that should never be kicking around in the public domain.   In the past I&#8217;ve also been required to provide my bank account information because one plan in particular would only provide coverage if they could automatically deduct monthly premiums via ACH drafts.  So now the insurance industry has access to it all; name, address, social security number, date-of-birth, maiden name, medical history and banking information.  And yet there&#8217;s no true oversight agency that&#8217;s responsible for making sure they&#8217;re protecting all of MY information.</p>
<p>To compound my frustration, of the four insurance companies I&#8217;ve conducted work for since 2006 (two of which are Fortune 5oo&#8217;s) exactly none of them have something akin to a Chief Information Security Officer.  They all have risk people focused on the business side of things (because that&#8217;s necessary to protect profitability) but that&#8217;s it.  There&#8217;s typically an information security manager who&#8217;s part of the infrastructure team but who almost never reports right into the senior-most technology person (e.g. CIO, CTO).  Any audit work that occurs is coordinated across multiple IT managers and on rare occasions there will be an audit/assurance manager.  However in the one example I personally know of where that position exists the person in the role was really just a converted IT manager who obtained a CISA designation &#8211; no fundamental audit or assessment experience.</p>
<p>The question has to be asked:  Why is it that banks and credit unions are heavily regulated regarding protection of non-public personal information but other industries with similar risk profiles are  not?  Why aren&#8217;t insurance companies required to comply with FFIEC-type guidance?  Why isn&#8217;t there a Federal regulatory agency that is responsible for keeping an eye on the insurance industry the way the FDIC, OCC, FRB and NCUA do so for their financial institutions?  And trust me, whatever oversight exists for the insurance and health care industry is largely ineffective.   Why is my sensitive information considered more at risk within a banking infrastructure than it is within an insurance infrastructure?  Having been on site for both and examined their internal controls  I can&#8217;t answer that question, that&#8217;s for certain.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/regulatory-compliance/are-banks-unfairly-scrutinized/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<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>CFPB: Filling the regulatory void left by Sheila Bair</title>
		<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance/cfpb-filling-the-regulatory-void-left-by-sheila-bair/</link>
		<comments>http://itknowledgeexchange.techtarget.com/regulatory-compliance/cfpb-filling-the-regulatory-void-left-by-sheila-bair/#comments</comments>
		<pubDate>Sat, 21 Jul 2012 20:25:31 +0000</pubDate>
		<dc:creator>David Schneier</dc:creator>
				<category><![CDATA[Add new tag]]></category>
		<category><![CDATA[assess]]></category>
		<category><![CDATA[assessment]]></category>
		<category><![CDATA[assessments]]></category>
		<category><![CDATA[bank]]></category>
		<category><![CDATA[banking]]></category>
		<category><![CDATA[banking crisis]]></category>
		<category><![CDATA[banks]]></category>
		<category><![CDATA[community bank]]></category>
		<category><![CDATA[compliance]]></category>
		<category><![CDATA[compliance officer]]></category>
		<category><![CDATA[compliant]]></category>
		<category><![CDATA[control]]></category>
		<category><![CDATA[credit]]></category>
		<category><![CDATA[credit card]]></category>
		<category><![CDATA[data security]]></category>
		<category><![CDATA[Dodd-Frank]]></category>
		<category><![CDATA[economy]]></category>
		<category><![CDATA[enterprise risk]]></category>
		<category><![CDATA[enterprise risk management]]></category>
		<category><![CDATA[ERM]]></category>
		<category><![CDATA[exam]]></category>
		<category><![CDATA[examination]]></category>
		<category><![CDATA[examinations]]></category>
		<category><![CDATA[examiner]]></category>
		<category><![CDATA[examiners]]></category>
		<category><![CDATA[exams]]></category>
		<category><![CDATA[Federal Reserve Bank]]></category>
		<category><![CDATA[FFIEC]]></category>
		<category><![CDATA[financial]]></category>
		<category><![CDATA[financial institutions]]></category>
		<category><![CDATA[framework]]></category>
		<category><![CDATA[information security office]]></category>
		<category><![CDATA[lending]]></category>
		<category><![CDATA[LinkedIn]]></category>
		<category><![CDATA[mortgage]]></category>
		<category><![CDATA[NCUA]]></category>
		<category><![CDATA[NCUA Sheila Bair]]></category>
		<category><![CDATA[NPPI]]></category>
		<category><![CDATA[observations]]></category>
		<category><![CDATA[oversight]]></category>
		<category><![CDATA[personally identifiable informaiton]]></category>
		<category><![CDATA[PII]]></category>
		<category><![CDATA[policy]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[procedure]]></category>
		<category><![CDATA[regulation]]></category>
		<category><![CDATA[regulations]]></category>
		<category><![CDATA[regulations audit]]></category>
		<category><![CDATA[regulatory]]></category>
		<category><![CDATA[regulatory guidance]]></category>
		<category><![CDATA[risk assess]]></category>
		<category><![CDATA[risk assessment]]></category>
		<category><![CDATA[risk assessments]]></category>
		<category><![CDATA[risk management]]></category>
		<category><![CDATA[risk-based]]></category>
		<category><![CDATA[risks]]></category>
		<category><![CDATA[security PII]]></category>
		<category><![CDATA[Sheila Bair]]></category>
		<category><![CDATA[social security numbers]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[third party management]]></category>
		<category><![CDATA[third party oversight]]></category>
		<category><![CDATA[vendor]]></category>
		<category><![CDATA[Vendor Management]]></category>
		<category><![CDATA[vendor risk]]></category>
		<category><![CDATA[vendor risk assessment]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/regulatory-compliance/?p=935</guid>
		<description><![CDATA[I was an unabashed fan of Sheila Bair and made no secret of that fact.  She was a breath of fresh air in a line of work where everything is stale and always at least a little boring.  Not that Martin Gruenberg is any less effective running the FDIC, he&#8217;s just a whole lot less [...]]]></description>
				<content:encoded><![CDATA[<p>I was an unabashed fan of Sheila Bair and made no secret of that fact.  She was a breath of fresh air in a line of work where everything is stale and always at least a little boring.  Not that Martin Gruenberg is any less effective running the FDIC, he&#8217;s just a whole lot less interesting to pay attention to.  And in the time since Ms. Bair stepped down I&#8217;ve just not been finding much to blog about regarding things the government is doing.</p>
<p>Things are looking up a bit because I have a new favorite regulatory agency to follow, the Consumer Financial Protection Bureau (CFPB).  And here&#8217;s why:  They focus on things that impact my day-to-day life (and yours as well).</p>
<p>I started tracking what the CFPB was doing about five months ago by accident.  Someone I know who used to be an examiner for the FRB switched over to the newer agency right at its infancy and I noticed this courtesy of a LinkedIn update.  Because I consider the Fed to be the Big Kahuna of the regulatory agencies I was surprised (you don&#8217;t leave the Yankees to sign with an expansion team unless you have to, or so I thought).  Compelled a bit by the update I started poking around the CFPB website.  For the first few months of this year it seemed to have potential but was little more than brochure-ware.  But last month that all changed.</p>
<p>The first CFPB update that caught my attention was labeled <a title="CFPB Regulations" href="http://www.consumerfinance.gov/pressreleases/consumer-financial-protection-bureau-adopts-rule-for-the-protection-of-privileged-information/" target="_blank">12 CFR Part 1070</a> and it was all about the protection of consumer data, only with a slight twist.  Basically it was all about how any information they received as part of their field work would be protected exactly the same way that any third party vendor would be required to.  Despite their being a Federal agency they weren&#8217;t going to hide behind that as a means to simplify their lives.  They spearheaded an update to the underlying regulation that frames their charter so that consumers and their institutions can be assured that all PII and NPPI would be protected.  For me it was a rare win-win topic; protection of PII and NPPI combined with a reference to vendor management (these are a few of my favorite things).  And really for me it was that much more significant because I&#8217;ve known of a few situations where representatives of Federal and State regulatory agencies were responsible for the outright loss of confidential and/or restricted data.  Beyond a slap on the wrist there wasn&#8217;t much else done to the offending examiner or their agency.  And the affected institution couldn&#8217;t really complain too loudly because it&#8217;s always a bad idea to challenge your regulators, even when you&#8217;re in the right.  So I thought this was all at once a compelling and remarkably sensible update by a regulator, not something I&#8217;d expect to see.  That was the first points on the board for the CFPB.</p>
<p>The second set of points were scored almost on the same day.  I wanted to check one of the details related to the aforementioned update and noticed this one &#8220;<a title="Reverse Mortgage Report" href="http://www.consumerfinance.gov/pressreleases/consumer-financial-protection-bureau-report-finds-confusion-in-reverse-mortgage-market/" target="_blank">Consumer Financial Protection Bureau report finds confusion in reverse mortgage market</a>&#8220;.  Because I have a parent who is a senior citizen and who I think might one day soon be open to at least exploring a reverse mortgage I read with great interest.  The report was in plain English, was oriented in such a way that I could share it with my family and have them understand the issues and concerns detailed within and most importantly it made sense.  Reverse mortgages are growing in popularity and its main audience is the senior citizens segment of society.  Seniors tend to be  more easily misled, they&#8217;re under greater pressures to find new money sources (courtesy of our recession) at a time in their lives where going back to work is often not an option.  And because a parent would do almost anything rather than turn to their children for financial assistance they see a reverse mortgage as a way out of their predicament.  So for me having this content available was quite the relief.  I can caution and advise all day and night but the risks presented by a reverse mortgage are much more credible coming from an authorized source.  And so I celebrated July 4th this year by declaring the CFPB my new FDIC (the Sheila Bair inspired version, not the current blah one).</p>
<p>Here&#8217;s my really bizarro advice to any of you with even the slightest interest in regulatory oversight; if you haven&#8217;t already done so visit <a title="CFPB - Home" href="http://www.consumerfinance.gov/" target="_blank">www.cfpb.gov</a> and take a look around.  It&#8217;s oriented towards lay people, not just lawyers and regulators (and practitioners like me) and addresses topics and concerns that affect the majority of our population.  Basically it&#8217;s what I would expect from a regulator that still has that new agency smell but nothing like I&#8217;ve come to know from those that preceded it.  To those who have had a hand in defining its charter and organizing its content, great job!   Now repay my kind words by going out and getting me some juicy enforcement stories to write about.</p>
<p>&nbsp;</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/regulatory-compliance/cfpb-filling-the-regulatory-void-left-by-sheila-bair/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Hidden information security threats are still threats</title>
		<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance/hidden-security-threats-are-still-threats/</link>
		<comments>http://itknowledgeexchange.techtarget.com/regulatory-compliance/hidden-security-threats-are-still-threats/#comments</comments>
		<pubDate>Fri, 01 Oct 2010 19:41:53 +0000</pubDate>
		<dc:creator>David Schneier</dc:creator>
				<category><![CDATA[Audit]]></category>
		<category><![CDATA[bank]]></category>
		<category><![CDATA[banking]]></category>
		<category><![CDATA[compliance]]></category>
		<category><![CDATA[credit union]]></category>
		<category><![CDATA[CU]]></category>
		<category><![CDATA[FDIC]]></category>
		<category><![CDATA[FFIEC]]></category>
		<category><![CDATA[financial]]></category>
		<category><![CDATA[financial institutions]]></category>
		<category><![CDATA[personally identifiable informaiton]]></category>
		<category><![CDATA[regulations]]></category>
		<category><![CDATA[regulatory]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[security PII]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/regulatory-compliance/?p=494</guid>
		<description><![CDATA[We'll read about huge PCI-related disasters where millions of credit card numbers have potentially been stolen.  We'll see stories on the news about how a laptop has gone missing with hundreds of thousands of accounts containing social security numbers.  We'll read about how criminals are piggy-backing card reader devices on legitimate ATM's to grab your credit and bank card data.  But no one can ever recall hearing about any identity thefts cases where the information involved was found to be harvested from just such a device.  And odds are you're never going to]]></description>
				<content:encoded><![CDATA[<p>Growing up I was a huge fan of the sitcom &#8220;The Odd Couple.&#8221;  Some of my favorite catch phrases have in some part been influenced by lines of dialogue that I memorized.  One in particular serves as the best pure definition for a phenomenon I encounter frequently enough in my audit/compliance career: &#8220;What you don&#8217;t know can hurt you a whole lot.&#8221; I can still hear the line being uttered and remember laughing because even as child I thought the phrase that inspired the line, &#8220;What you don&#8217;t know can&#8217;t hurt you&#8221; was pretty dumb. All these years later, I&#8217;ve collected an impressive body of evidence to support my opinion.</p>
<p>So when the FDIC recently issued <a href="http://searchfinancialsecurity.techtarget.com/news/article/0,289142,sid185_gci1520280_mem1,00.html">new guidance</a> titled &#8220;<span>Guidance on Mitigating Risk Posed by Information Stored on Photocopiers, Fax Machines and Printers&#8221; (</span>FIL-56-2010),&#8221; I was reminded once again of this favorite phrase of mine.</p>
<p>It&#8217;s important to explain that my first foray into audit allowed me to work with arguably the best auditor I&#8217;ve ever met.  I was taught to question everything and assume it was in scope until proven otherwise, and I was encouraged to trust and follow my instincts.  And so fairly early in my regulatory career when I first started to search out the myriad threats to personally identifiable information (PII), all sorts of things landed on my radar screen.  Accordingly, for nearly a decade I&#8217;ve been advising clients on the threats posed by what are typically thought of as secondary devices or peripherals.  Financial institutions will spend all sorts of crazy money to protect servers and storage devices but completely ignore multifunction devices that copy, scan, fax and email just about any document imaginable and often retain those images in memory.  They&#8217;ll have surprise desktop audits where someone will spot check work spaces to see if PII has been properly secured but will walk past the copier room time and again and ignore what lays in the output trays.  Our practice has long advocated for related control activities to remove this remarkable blind spot but year over year we return to our clients and find that little has changed.</p>
<p>And so the question needs to be asked: Why?</p>
<p>The answer is very likely found in the fact that no known breaches or cases of identify theft have ever been tied back to information gleaned from a peripheral device.  We&#8217;ll read about huge PCI-related disasters where millions of credit card numbers were potentially stolen.  We&#8217;ll see stories on the news about how a laptop has gone missing with hundreds of thousands of accounts containing Social Security numbers.  We&#8217;ll read about how criminals are piggy-backing card reader devices on legitimate ATM&#8217;s to grab your credit and bank card data.  But no one can ever recall hearing about any identity thefts cases where the information involved was found to be harvested from just such a device.  And odds are you&#8217;re never going to.</p>
<p>The amount of information to be gleaned from peripheral devices is relatively small.  All but a few of them can only retain a modest amount of data and so you&#8217;re not going to find much more than a few dozen opportunities per device.  If someone within an office is aware of this treasure trove of information and is skimming it off and either using it or selling it how would you know?  How would you be able to develop the trend (remember that very few people file police reports when they discover that their identify has been stolen or accounts accessed).  So there isn&#8217;t a whole lot of investigating going on.  And if someone at either the equipment reseller or company warehouse is collecting the information and using it for illegal purposes how would anyone know?  We&#8217;re not talking about thousands of accounts or individuals from any one company or institution; it&#8217;s more like a patchwork collection.  You would only be able to find a trend if you went looking for it, and you would only go looking for it if you had a credible reason to do so.</p>
<p>But here&#8217;s the thing; I&#8217;ve thought about this information being readily available and difficult to trace and I&#8217;m an honest man and one of the good guys. Don&#8217;t you think the bad guys have this figured out as well?</p>
<p>So it will be interesting to see how or if the banking industry reacts to this bulletin.  It&#8217;s been my experience that these things go largely unheeded until an examiner applies a little pressure.  I suppose way too many financial institutions are happy enough to apply the &#8220;what you don&#8217;t know can&#8217;t hurt you&#8221; logic. Not me.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/regulatory-compliance/hidden-security-threats-are-still-threats/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
