 




<?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; fraud</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/regulatory-compliance/tag/fraud/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>Metrics Reporting: Are pretty colors always pretty accurate?</title>
		<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance/metrics-and-regulatory-reporting-are-pretty-colors-always-pretty-accurate/</link>
		<comments>http://itknowledgeexchange.techtarget.com/regulatory-compliance/metrics-and-regulatory-reporting-are-pretty-colors-always-pretty-accurate/#comments</comments>
		<pubDate>Wed, 08 Aug 2012 18:21:42 +0000</pubDate>
		<dc:creator>David Schneier</dc:creator>
				<category><![CDATA[Audit]]></category>
		<category><![CDATA[auditor]]></category>
		<category><![CDATA[audits]]></category>
		<category><![CDATA[bank]]></category>
		<category><![CDATA[banking]]></category>
		<category><![CDATA[banks]]></category>
		<category><![CDATA[Board]]></category>
		<category><![CDATA[Board of Directors]]></category>
		<category><![CDATA[BoD]]></category>
		<category><![CDATA[business]]></category>
		<category><![CDATA[community bank]]></category>
		<category><![CDATA[compliance]]></category>
		<category><![CDATA[control]]></category>
		<category><![CDATA[controls]]></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[financial institutions]]></category>
		<category><![CDATA[fraud]]></category>
		<category><![CDATA[governance]]></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[SOX]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/regulatory-compliance/?p=952</guid>
		<description><![CDATA[I have an odd relationship with management reporting.  I know it&#8217;s a necessity and quite often see clear value in what&#8217;s packaged for senior management and board review.  But a significant piece of the reporting content comes in the form of metrics and, well, whenever I hear the term it conjures up this ghastly image of [...]]]></description>
				<content:encoded><![CDATA[<p>I have an odd relationship with management reporting.  I know it&#8217;s a necessity and quite often see clear value in what&#8217;s packaged for senior management and board review.  But a significant piece of the reporting content comes in the form of metrics and, well, whenever I hear the term it conjures up this ghastly image of good and decent people sinking slowly to their deaths in the quicksand that such efforts often become.</p>
<p>Now I&#8217;ve designed and supported more than my fair share of related content.  I understand that sometimes the best way to tell a story is to paint it in the form of a picture; I get that part.  But way too many times I&#8217;ve witnessed such initiatives spiral out of control to the point where it takes an army of people working ridiculous hours to pull together a deck of metrics that either fails to answer anyone&#8217;s questions or, even worse, generates requests for more metrics to provide clarity.  And once a metric becomes a standard part of any reporting package it often stays there until management changes, and sometimes even beyond.</p>
<p>But I think there&#8217;s a bigger issue with metrics that exceeds my simply not thinking they&#8217;re &#8220;all that and a bag of chips&#8221;.  Where are the controls around generating them?</p>
<p>Seriously, we have this vastly complex framework wrapped around financial reporting (SOX) to provide reasonable assurances that what management is reporting to its investors is accurate.  We have industry, federal and state legislation requiring all manner of controls around sensitive information.  There are auditors (internal and external) and regulators from all over the place that comb over everything with a fine tooth comb (or at least claim to) to make sure everything being done is done right &#8211; but in my nearly fifteen years in the audit/assurance industry I have never heard of a finding or issue regarding the veracity of metrics.  Which is only a problem if the people running an institution or company rely on them to make decisions.</p>
<p>The reason why it&#8217;s a problem is because so much of the metrics out in circulation is pulled together from disparate sources, cobbled together in spreadsheets or non-production databases and manually generated.  There&#8217;s no easy way to verify the source data, or know that it&#8217;s unaltered in any way or even know if it&#8217;s the right information.  And even if the data source used is from a secured production-like environment, still there&#8217;s no real auditing conducted to ensure the information is accurate or better yet, is even the right information.</p>
<p>I once took over a change management process and assumed responsibility for a series of reports that were generated for the Managing Director who in turn used that as part of his reporting package shared with the CIO.  One of the key metrics being reported on was scheduled releases and the IT departments on-time implementation percentage.  The numbers looked great showing that they were on-time more than ninety-five percent of the time over a two year period.  The only problem I could see with the metric was that it was misleading to the point where it was almost a lie.  The scheduled release date was being pulled from the system used to migrate changes into production and that date was only determined once the development team had completed all of their work.  So the scheduled implementation date was chosen once they knew they were ready to move into production.   Of course the on-time numbers looked great, they always knew they were ready before committing to it.  The Managing Director incorrectly assumed that there was a legitimate release schedule with forecasted dates and that the on-time numbers reflected on a well run process; wrong.   No one ever questioned the numbers or their source and had I not inserted myself into what was described as a well honed, efficient process the problem might have never been identified; and there a few more just like it.  My trust in metrics was permanently altered after that.</p>
<p>Metrics represents an excellent way for decision makers to quickly understand status and identify problems.  I&#8217;ve quoted here before about how someone I respect quite a bit was fond of asking her team &#8220;If you can&#8217;t measure it, how can you manage it&#8221; and she&#8217;s absolutely right.  Metrics is the ultimate management means of measuring key activities and issues within their world.  But how far do you go and how much effort do you expend pulling the related reports together?  And even if you&#8217;re able to automate the process and shorten the time necessary to generate the reports, how do you know that you&#8217;re either measuring the right things or that the underlying data is unaltered?  Ultimately I think that senior managers should be provided with something akin to a cost-benefit analysis for each metric they&#8217;re given.  Have them understand the degree of complexity and the amount of effort required to generate a number before deciding whether or not it&#8217;s worth it.  Perhaps I&#8217;m being naive but I&#8217;d like to think that most C-level executives would eliminate a significant amount of their reporting if they could see how much it was really costing them.</p>
<p>Here&#8217;s the part that should really concern you the most though: Metrics is a key component of Board reporting, they make all sorts of decisions based on what these reports tell them.  How can that be allowed unless the process used to generate them is locked down and audited?  Where are the regulators in all of this?</p>
<p>&nbsp;</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/regulatory-compliance/metrics-and-regulatory-reporting-are-pretty-colors-always-pretty-accurate/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Something smells phishy</title>
		<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance/something-smells-phishy/</link>
		<comments>http://itknowledgeexchange.techtarget.com/regulatory-compliance/something-smells-phishy/#comments</comments>
		<pubDate>Tue, 02 Mar 2010 20:18:30 +0000</pubDate>
		<dc:creator>David Schneier</dc:creator>
				<category><![CDATA[email]]></category>
		<category><![CDATA[fraud]]></category>
		<category><![CDATA[GLBA]]></category>
		<category><![CDATA[phish]]></category>
		<category><![CDATA[phishing]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[scam]]></category>
		<category><![CDATA[scammer]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[spam]]></category>
		<category><![CDATA[theft]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/regulatory-compliance/?p=305</guid>
		<description><![CDATA[P.T. Barnum was often credited with having said that "There's a sucker born every minute" and apparently online there are somewhere between two and too many scammers waiting to take 'em.]]></description>
				<content:encoded><![CDATA[<p>I received an email from Rebecca Keen this morning asking for help.  You see, Rebecca took an unexpected trip to the UK and while there lost her wallet and all of her financial resources and was hoping I could help.  She asked if I could float her a temporary loan of $1,540 so she could settle her hotel bill and make it back home safely.  It turns out that all of her other possible avenues for assistance have failed her and I&#8217;m something of a last resort.</p>
<p>Of course I don&#8217;t know anyone by the name Rebecca Keen and knew instantly that it was a phishing scam. It&#8217;s not the email by itself that made this a blog-worthy item.  What made Rebecca&#8217;s email this week&#8217;s topic was the reaction of someone close to me and their attitude about how to handle it.</p>
<p>At the risk of embarrassing anyone, I won&#8217;t go into specifics as to who the person is, but when I told them about the email as a way of educating them on how to identify and manage phishing attempts, they asked me how I knew it wasn&#8217;t legitimate.  Beyond the obvious fact that I don&#8217;t know now and have never known anyone by that name I&#8217;m not sure what else I&#8217;d need as proof this was a scam.</p>
<p>Here was the ensuing exchange:</p>
<p>&#8220;That may be true but what if they sent you the email by accident?  What if they misspelled the email address?&#8221;</p>
<p>To which I replied, &#8220;Still not my problem and I won&#8217;t respond because that establishes a dialogue which will only encourage the person further.&#8221;</p>
<p>&#8220;But shouldn&#8217;t you at least let the person know they reached the wrong person,&#8221; I was asked with a tinge of real concern.</p>
<p>&#8220;If I reply, that will send the message that they reached the right person. They&#8217;ll think I care, which will only open me up to additional pressures from the scammer&#8221;.</p>
<p>&#8220;People are so mistrusting these days.  I&#8217;d at least want to make sure this wasn&#8217;t someone who needed my help&#8221;.</p>
<p>And therein lies the problem: Despite this being a very obvious phishing attempt, it was only obvious to me. Despite the endless stories about people being exploited and robbed by an endless array of online and email scams, there are still people who respond favorably to these sort of things because of their basic decency. The person to whom I was talking wasn&#8217;t lacking in intelligence and isn&#8217;t typically naive, but when presented with these situations uses a different set of rules.</p>
<p>To make matters worse, the email from Rebecca Keen was properly formatted without spelling errors and actually looked like something I might receive from a legitimate source.  As a matter of fact, it presented itself so well that I actually opened it, which is a step further along than these things usually get.  But of course I knew instantly that it was just the latest example of how people are using the Internet to try and steal money.  And while the scam was obvious to me, there is at least one person I know who might actually have taken action upon receiving something similar.</p>
<p>You know what occurred to me today?  The reason that scammers continue to send out phishing emails is because they still generate the desired results.  Despite the endless marketing campaigns by a wide range of financial institutions to educate online users, there are still a large enough number of people who are victims waiting to happen.   And as long as even one person responds favorably to a phishing campaign, it&#8217;s considered a success.</p>
<p>I&#8217;m thinking that as a former New Yawker I should create a program for the FDIC based on my experiences growing up in New York City.</p>
<ul>
<li>Do not engage in any dialogue with anyone you don&#8217;t know about money in an unusual or inappropriate setting e.g. street corners, subway platforms, etc.</li>
<li>If someone is selling something, offering to buy something or trying to distract you somehow when in an unusual or inappropriate setting (e.g. stopping you on the street, walking up to your table at a restaurant, etc.) immediately disengage and continue on your way or return to what you were doing without allowing the conversation to develop and/or continue.</li>
<li>And if at any time your instincts tell you that something is wrong, amiss, out of place or odd err on the side of caution and do everything and anything to remove yourself from that situation.</li>
</ul>
<p>P.T. Barnum was often credited with having said that &#8220;There&#8217;s a sucker born every minute&#8221; and apparently online there are somewhere between two and too many scammers waiting to take &#8216;em.</p>
<p>P.S. As I was about to publish this post I received an email update from Rebecca Keen letting me know that someone temporarily stole her email account and that there&#8217;s no emergency whatsoever.   Glad to hear it but I still have no clue who she is.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/regulatory-compliance/something-smells-phishy/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>IT audit reports: Why you can&#8217;t handle the truth</title>
		<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance/audits-and-why-you-cant-handle-the-truth/</link>
		<comments>http://itknowledgeexchange.techtarget.com/regulatory-compliance/audits-and-why-you-cant-handle-the-truth/#comments</comments>
		<pubDate>Fri, 12 Feb 2010 23:38:03 +0000</pubDate>
		<dc:creator>David Schneier</dc:creator>
				<category><![CDATA[Audit]]></category>
		<category><![CDATA[corruption]]></category>
		<category><![CDATA[fraud]]></category>
		<category><![CDATA[GLBA]]></category>
		<category><![CDATA[Information Technology General Controls]]></category>
		<category><![CDATA[infrastructure]]></category>
		<category><![CDATA[IT]]></category>
		<category><![CDATA[IT General Controls]]></category>
		<category><![CDATA[ITGC]]></category>
		<category><![CDATA[NCUA]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/regulatory-compliance/?p=280</guid>
		<description><![CDATA[One of the oldest tricks in the business book when it comes to audits is to start questioning the quality and veracity of reports that are perceived as not being favorable.]]></description>
				<content:encoded><![CDATA[<p>I was reading the local newspaper this morning and was surprised to find a front page story ripped from the headlines of my professional life (ironic, I know).</p>
<p>Right there on the front page of today&#8217;s News and Observer was a story about how a recent audit claimed corruption at a local college (North Carolina Central University).  I&#8217;m sort of trained in a Pavlovian sort of way to notice anything having to do with audit and so I gave it a cursory read.  Cursory turned into focused when I reached the part about how the school&#8217;s chancellor Charlie Nelms called the report draft &#8220;sloppy&#8221; and went on to say that some of its harshest accusations might not be true.</p>
<p>One of the oldest tricks in the business book when it comes to audits is to start questioning the quality and veracity of reports that are perceived as not being favorable.  Instead of focusing on the audits findings and trying to validate them (because a good audit is your best friend if you really want to do things right) the auditee goes into a series of tactical maneuvers to deflect attention away from the report&#8217;s contents and feigns disgust and outrage.</p>
<p>The school chancellor went on to say that, after firing the auditor who produced the report, he &#8220;ordered his staff to gather more information before he releases a final version to the public.&#8221;   He went on to say that the &#8220;draft audit was so poor that he doesn&#8217;t trust it, and he does not want to damage the reputations of people who might not have done anything wrong&#8221;.</p>
<p>A few years ago, I conducted a risk assessment for a client with an odd configuration of infrastructure pieces that clearly defied anything close to typical, so it was difficult to measure them against the norm.  Just the same, I tried.  I took a step back after conducting all of my interviews and gathering as much information as was available and filtered it through the lenses of an examiner.  I surfaced gaps and issues that were likely to be viewed in a negative light, explained why that was and offered clear and concise remedial steps.  Senior management went bonkers (for lack of a better word) when they received the report.</p>
<p>They were outraged because the report was delivered a week late (which was true), they were insulted that there were typos (not factual errors, just a few grammatical/spelling hiccups which are common in draft versions) and charged that some of the issues listed were completely false.  In summary, they called into question the accuracy and reliability of the entire report.  It was startling for me because in my more than two decades working in the business world with more than 10 years conducting audits and assessment, I&#8217;d never had a client react anywhere near this way before.</p>
<p>But it was really more about using diversionary tactics intended to gain a negotiating advantage.  Their end game was to soften the report&#8217;s contents so that it looked better when the examiners came back around; by pushing us back into a defensive position, they were almost successful.  Fortunately, I&#8217;m stubborn when it comes to standing behind my findings and need incontrovertible proof that I was wrong about something before changing or removing things.  I may not be the best auditor but I have well honed instincts around IT, the myriad processes necessary to support the infrastructure, and I know good from bad.  I never put anything into my reports that doesn&#8217;t resonate with me and my peers (and typically the report&#8217;s audience).</p>
<p>So you can imagine where my head was at while reading the story today.  Mr. Nelms also said, &#8220;I want to see the source documents, and I want to see the field notes from the audit, because I want it to be accurate.  I don&#8217;t want it to be hearsay, because some of the allegations are just mind-boggling.&#8221;</p>
<p>Well that&#8217;s good to hear because any audit worth its weight in paper needs to be supported by solid work papers.  But considering that he fired the auditor, I&#8217;m hoping someone in his office thought to secure that beforehand.  And I&#8217;d need to understand why he&#8217;s gathering more information when all he really needs to do is use the work papers and have another independent auditor re-perform the tests.</p>
<p>Oh and another thing, who hired the auditor to begin with?</p>
<p>Also, now that the report&#8217;s findings are semi-public (it&#8217;s available despite not having been formally released), where&#8217;s the value in conducting a follow-up audit?  Anyone involved with any alleged wrongdoings now has a clear roadmap in front of them on how to cover their tracks.</p>
<p>Here&#8217;s my thinking on all of this: The audit is likely somewhere close to 100% accurate but far from perfect (I know that&#8217;s a contradiction).  If the chancellor was really interested in handling this properly, he&#8217;d quietly set about having independent people digging into the findings, not as a CYA exercise but simply to get to the bottom of things and deal with whatever is found.  I&#8217;m not saying that where there&#8217;s smoke there&#8217;s always fire but unless Mr. Nelms can offer a credible explanation why he would think that the fired auditor would fabricate stories or offer poorly formed conclusions I&#8217;d have no choice but to question his position on all of this.  I guess what I&#8217;m asking for is a credible explanation as to where the smoke is coming from and an explanation why he thinks it&#8217;s benign.</p>
<p>What I&#8217;d like is to hear the auditor&#8217;s side of the story.  I&#8217;m betting that would be an enlightening conversation.  But if Mr. Nelms was successful in his very public tongue lashing of this auditor, he/she will do anything and everything to avoid having their name outed.  And so the diversionary tactics score another point.</p>
<p>And the best part of this?  I almost never read the paper.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/regulatory-compliance/audits-and-why-you-cant-handle-the-truth/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IT Security: Something has to give.</title>
		<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance/it-security-something-has-to-give/</link>
		<comments>http://itknowledgeexchange.techtarget.com/regulatory-compliance/it-security-something-has-to-give/#comments</comments>
		<pubDate>Wed, 20 May 2009 19:31:05 +0000</pubDate>
		<dc:creator>David Schneier</dc:creator>
				<category><![CDATA[Audit]]></category>
		<category><![CDATA[FDIC]]></category>
		<category><![CDATA[FFIEC]]></category>
		<category><![CDATA[fraud]]></category>
		<category><![CDATA[GLBA]]></category>
		<category><![CDATA[NCUA]]></category>
		<category><![CDATA[phishing]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/regulatory-compliance/?p=113</guid>
		<description><![CDATA[My practice has been busy lately helping a number of clients catch up on required tasks before their scheduled exams (it&#8217;s a case of the old &#8220;if it wasn&#8217;t for the last minute nothing would ever happen&#8221; philosophy).  And in authoring some of our reports we&#8217;re identifying issues and gaps that are in some cases [...]]]></description>
				<content:encoded><![CDATA[<p>My practice has been busy lately helping a number of clients catch up on required tasks before their scheduled exams (it&#8217;s a case of the old &#8220;if it wasn&#8217;t for the last minute nothing would ever happen&#8221; philosophy).  And in authoring some of our reports we&#8217;re identifying issues and gaps that are in some cases minor but in others are big enough to drive a car through.  This is nothing new.</p>
<p>What is new is the ambivalence we&#8217;re experiencing from management.  It seems that a little known byproduct of our currently sad economic state is that keeping the doors open seems to be the only goal that really matters.  Management is not particularly concerned with much else, or so it would seem.  Not that this by itself is a new phenomenon either but there&#8217;s almost a reckless undertone emerging.</p>
<p>We&#8217;ve encountered some glaring issues recently that underscore a fundamental problem that I&#8217;ve struggled with for a long time: The FDIC and NCUA examiners just don&#8217;t pay enough attention to IT-based risks.  In some instances they touch on high-level issues and in rare instances can get a bit more granular, but we&#8217;ve collected empirical evidence that an in-depth review hasn&#8217;t been conducted for the vast majority of institutions that we&#8217;ve worked with.</p>
<p>Forget about industry best practices and forget about the fact that financial institutions are required by law to implement and maintain certain basic safeguards.  We live in an age where identify theft and credit card fraud are rampant.  Every day we are presented with more stories, more guidance and more information about how the criminal element is finding newer and more insidious ways to get at our money and credit.  My senior citizen mother and my grade-school aged children are all aware of the term phishing, have all been coached as to which email is safe to open versus which isn&#8217;t and know not to share personal information.  If I can convince them of the threats out there in the great digital void you have to think it&#8217;s fairly obvious, right?</p>
<p>So why is it that the examiners aren&#8217;t paying more attention to the IT infrastructure?  I had a chance to ask someone from the NCUA office a few months back that very question and while I didn&#8217;t like his answer, it made sense particularly considering the more pressing issues banks and credit unions are currently dealing with.  It comes down to resource availability.  Only so many hours are allocated to an exam  based on their size.  And so for the smaller institutions, the examiners prioritize the work based on risk.  Can anyone argue that scrutinizing the books is less important than auditing the IT infrastructure?</p>
<p>Even so, some of the institutions we&#8217;ve worked with and which I&#8217;ve personally reviewed have had issues for what has to be several years.  How is it possible that in the past five years not one examiner has ever noticed the absence of a business continuity plan?  Or any form of security around the firewall (and an unusually permissive firewall at that)?  Or the lack of strong (or even reasonable)  password controls?</p>
<p>Something has to give.  When you combine the lack of proper examiner supervision with a less than concerned management mindset the potential for serious issues becomes much greater (and likely).  Somehow the various entities that are responsible for providing oversight for those places we trust with our money need to figure out a way to provide reasonable assurances that at least the bare minimums are being met when it comes to IT controls.  With all the money being spent to keep the banking industry afloat can&#8217;t someone figure out a way to slice off a little bit in order to hire enough IT people to conduct the necessary examinations?  Congressman?  Senator?  Mr. President?  Anyone?</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/regulatory-compliance/it-security-something-has-to-give/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
