 




<?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; vendor risk</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/regulatory-compliance/tag/vendor-risk/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>CFPB: Dodd-Frank at its best.</title>
		<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance/cfpb-dodd-frank-at-its-best/</link>
		<comments>http://itknowledgeexchange.techtarget.com/regulatory-compliance/cfpb-dodd-frank-at-its-best/#comments</comments>
		<pubDate>Wed, 19 Dec 2012 13:51:59 +0000</pubDate>
		<dc:creator>David Schneier</dc:creator>
				<category><![CDATA[bank]]></category>
		<category><![CDATA[banking]]></category>
		<category><![CDATA[banking crisis]]></category>
		<category><![CDATA[banks]]></category>
		<category><![CDATA[compliance]]></category>
		<category><![CDATA[compliant]]></category>
		<category><![CDATA[Dodd-Frank]]></category>
		<category><![CDATA[economy]]></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[FRB]]></category>
		<category><![CDATA[mortgage]]></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[requirements]]></category>
		<category><![CDATA[risk]]></category>
		<category><![CDATA[SOX]]></category>
		<category><![CDATA[third party management]]></category>
		<category><![CDATA[third party oversight]]></category>
		<category><![CDATA[too big too fail]]></category>
		<category><![CDATA[vendor]]></category>
		<category><![CDATA[Vendor Management]]></category>
		<category><![CDATA[vendor risk]]></category>
		<category><![CDATA[vendor risk assessment]]></category>
		<category><![CDATA[vendor risk rating]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/regulatory-compliance/?p=1013</guid>
		<description><![CDATA[The campaign season that ended with last month’s presidential elections generated more debate and rhetoric than any other in my lifetime.  As I&#8217;m an outspoken person who has never shied away from a good argument I routinely found myself engaged in exchanges with a remarkably broad range of people from middle schooler’s to octogenarians (and [...]]]></description>
				<content:encoded><![CDATA[<p>The campaign season that ended with last month’s presidential elections generated more debate and rhetoric than any other in my lifetime.  As I&#8217;m an outspoken person who has never shied away from a good argument I routinely found myself engaged in exchanges with a remarkably broad range of people from middle schooler’s to octogenarians (and that was just within my own family) that delved into an even broader range of issues.  I was amazed by how much misinformation was being spread about both candidates, what their platforms were, what their agendas were (both published and hidden) and how voting for one or the other was guaranteeing the downfall of our great nation.  Generally I took most of what I heard with a grain of salt and tried to work patiently through things to get as close to the truth as possible.  On a few occasion’s though I was presented with an assertion or opinion that required a little less patience and a bit more slapping upside the head.</p>
<p>Right after one of the debates I found myself knee deep in a debate about Dodd-Frank.  A close personal friend of mine, a very bright bulb who I’ve never found a reason to disagree with brought up Dodd-Frank as an example of horrible legislation that’s crippling banks and contributing to our horrible economic conditions.  Whoa, whoa, whoa…. rail against taxes, complain about government spending, assail the current administration for the dramatic escalation of our national debt.  But leave Dodd-Frank out of it because that’s not one of our bigger problems.  I can offer a five thousand word defense of the best parts of Dodd-Frank without even pausing to organize my thoughts but I don&#8217;t need to go that far.  I can sell it&#8217;s virtues in a single, simple sentence:  Any legislation that created the Consumer Financial Protection Bureau is instantly more effective than anything that&#8217;s come before it in my lifetime.</p>
<p>No, seriously&#8230; in my lifetime.</p>
<p>I&#8217;ve already screamed from the rooftops about how much I like the CFPB.  In my own geeky, nerdy way I&#8217;m proud to admit that I look forward to getting their regular updates and announcements because they always seem either ridiculously relevent or illuminate how they&#8217;re hot on the heels of yet another predatory business practice.  In barely a years time they&#8217;ve pushed deeper into the heart of the issues that crashed Wall Street in 2008 than anyone could have hoped (that&#8217;s my opinion but one I&#8217;m willing to defend).  And their examiners appear to be freaky efficient.  I&#8217;ve been hearing from our banking clients that they&#8217;re drilling in on details and covering more territory than was expected and that they&#8217;re discussing issues much closer to protecting customers (and members).   Our practice recently issued a bulletin to our clients alerting them to the fact that CFPB examiners are expecting related oversight to be pushed down to external business parters and vendors.  This is not a new consideration, it&#8217;s exactly the same as what&#8217;s supposed to happen with regards to GLBA (and one of the reasons we developed our related software and services for same) but still, we anticipated this would take several exam cycles to surface.  CFPB cut right to that chase in a heartbeat, which is stunning for such things.  It&#8217;s almost like someone told them where to look and what to look for which to a certain extent is true.</p>
<p>The CFPB didn&#8217;t start as most new agencies do.  They didn&#8217;t recruit green examiners and place them under the management of a few practiced hands.  What they apparently have done is to hire well seasoned examiners from related regulatory agencies (e.g. FDIC, FRB, OCC) have them contribute to creating the necessary procedures and then send them out to bring it all to life.  So on Day One they already know where the bodies are likely to be buried and what to do about it.  It&#8217;s brilliant, it&#8217;s efficient and it&#8217;s the very best example of  your government doing its job.</p>
<p>Here are some snippets from my in-box:</p>
<ul>
<li>Regarding the three main credit reporting agencies, the CFPB released a report that said &#8220;Among the key takeaways in the report, which is one of the most comprehensive studies of credit reporting to date, are that credit card history dominates the information in credit reports and that debt collection items  generate the highest rate of disputes&#8221;.  This becomes important for consumers who are trying to either establish or repair respectable credit ratings.  The news release further explained about the report that it &#8220;will help educate regulators and consumers about how this important industry works,” said CFPB Director Richard Cordray. &#8220;If consumers know how these companies handle their credit histories, they can make better decisions on how to handle their financial lives.&#8221;</li>
<li>This was another headline &#8220;CONSUMER FINANCIAL PROTECTION BUREAU HALTS ALLEGED NATIONWIDE MORTGAGE LOAN MODIFICATION SCAMS&#8221;.  The news release explained that the CFPB is  “taking on schemes that prey on consumers who are struggling to pay their mortgages or facing foreclosure,” said CFPB Director Richard Cordray. &#8220;We are especially concerned with those who misrepresent government programs or websites to divert distressed homeowners from needed assistance.&#8221;</li>
<li>And even still, another headline &#8220;CONSUMER FINANCIAL PROTECTION BUREAU PROPOSES ALLOWING COMPANIES TO RUN TRIAL DISCLOSURE PROGRAMS&#8221;.  And while this may seem dry to so many not close to the related issue this is signficant because right now most of us ignore all the small print.  The CFPB is trying to figure out better ways to present disclousre information so that us consumers both think to read it and, more importantly, understand what it&#8217;s telling us.  Rather than try and stuff a once-sized-fits-all solution down the industries throat they&#8217;re opening it up and authorizing institutions and lenders to explore different approaches.</li>
</ul>
<p>And the kicker about these three items?  This was all issued this month (December 2012) and we&#8217;re not even quite halfway through it.</p>
<p> </p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/regulatory-compliance/cfpb-dodd-frank-at-its-best/feed/</wfw:commentRss>
		<slash:comments>0</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>Risk: The core issue behind regulatory requirements</title>
		<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance/risk-the-core-issue-behind-regulatory-requirements/</link>
		<comments>http://itknowledgeexchange.techtarget.com/regulatory-compliance/risk-the-core-issue-behind-regulatory-requirements/#comments</comments>
		<pubDate>Fri, 06 Jul 2012 03:18:40 +0000</pubDate>
		<dc:creator>David Schneier</dc:creator>
				<category><![CDATA[assess]]></category>
		<category><![CDATA[assessment]]></category>
		<category><![CDATA[assessments]]></category>
		<category><![CDATA[Audit]]></category>
		<category><![CDATA[audits]]></category>
		<category><![CDATA[bank]]></category>
		<category><![CDATA[banking]]></category>
		<category><![CDATA[banks]]></category>
		<category><![CDATA[compliance]]></category>
		<category><![CDATA[compliant]]></category>
		<category><![CDATA[control]]></category>
		<category><![CDATA[credit union]]></category>
		<category><![CDATA[credit unions]]></category>
		<category><![CDATA[CU]]></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[exams]]></category>
		<category><![CDATA[FDIC]]></category>
		<category><![CDATA[Federal Reserve Bank]]></category>
		<category><![CDATA[FFIEC]]></category>
		<category><![CDATA[financial institutions]]></category>
		<category><![CDATA[framework]]></category>
		<category><![CDATA[FRB]]></category>
		<category><![CDATA[general controls]]></category>
		<category><![CDATA[GLBA]]></category>
		<category><![CDATA[governance]]></category>
		<category><![CDATA[GRC]]></category>
		<category><![CDATA[guidance]]></category>
		<category><![CDATA[information security]]></category>
		<category><![CDATA[information security office]]></category>
		<category><![CDATA[infrastructure]]></category>
		<category><![CDATA[NCUA]]></category>
		<category><![CDATA[PII]]></category>
		<category><![CDATA[policy]]></category>
		<category><![CDATA[procedure]]></category>
		<category><![CDATA[regulation]]></category>
		<category><![CDATA[regulations]]></category>
		<category><![CDATA[regulations audit]]></category>
		<category><![CDATA[risk assessment]]></category>
		<category><![CDATA[risk assessments]]></category>
		<category><![CDATA[Risk IT]]></category>
		<category><![CDATA[risk management]]></category>
		<category><![CDATA[risk rating]]></category>
		<category><![CDATA[risk-based]]></category>
		<category><![CDATA[risks]]></category>
		<category><![CDATA[threats]]></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=923</guid>
		<description><![CDATA[There&#8217;s a joke of sorts within my personal circle of family and friends regarding what it is that I do these days.  Ask me and I&#8217;ll tell you that I&#8217;m a regulatory compliance expert who advises financial institutions on how to comply with the myriad rules and regulations governing information security.  Ask my immediate family [...]]]></description>
				<content:encoded><![CDATA[<p>There&#8217;s a joke of sorts within my personal circle of family and friends regarding what it is that I do these days.  Ask me and I&#8217;ll tell you that I&#8217;m a regulatory compliance expert who advises financial institutions on how to comply with the myriad rules and regulations governing information security.  Ask my immediate family and they&#8217;ll tell you that I work with computers.  Ask my extended circle and they&#8217;ll tell you that I do a lot of work with banks and credit unions.  For those who aren&#8217;t in the banking business it&#8217;s difficult to understand exactly what it is that I do and so they find it easier to keep it simple; I do a lot of work with computers for places where people deposit their money.</p>
<p>Of course the truth is much more complicated.  I don&#8217;t just focus on computers, my scope expands to include anything that involves sensitive information.  While that always includes a variety of devices it also includes paper-based and people processes as well.  I frequently share stories about the enormous amount of printed content that&#8217;s to be found throughout an institutions physical locations.  I occasionally tell stories about how careless people can be when on the phone or in conversation and sharing all manner of sensitive information.  It&#8217;s never just about computers, it is however always about information and how it needs to be protected.</p>
<p>Truthfully though what I really do is search for controls that protect information, identify those that I find and try and measure their effectiveness and more importantly identify where controls are missing and work with my clients to remedy that.  At the heart of the regulatory requirements I focus on it&#8217;s all about the risk introduced by the presence of information, from personally identifiable (PII) to non-public personally identifiable (NPPI).  Risk: It&#8217;s what drives every single project I work on, it&#8217;s what drives every product and process I help develop.  And really, if you take the time to read through the literature, it&#8217;s what&#8217;s behind just about every piece of regulation known to the banking world.  Risk, risk, risk and risk.</p>
<p>One of the reasons I&#8217;ve enjoyed spending so much time working with the community banking and credit union sector over the past few years is that it&#8217;s a simple enough argument to make with fewer people to convince; everything you do to comply with the regulations should be risk-based.  It doesn&#8217;t really make a difference if it&#8217;s complicated to do or time consuming, you prioritize based on where they are found and make decisions accordingly.  But that gets much more difficult to do as the institutions grow in size and complexity.  Over the fifteen years I&#8217;ve been building and supporting compliance initiatives I&#8217;ve worked with Fortune 50&#8242;s, 100&#8242;s and 500&#8242;s and a whole lot of financial institutions that merely read Fortune magazine.  But while their overall size varies widely risk is still risk and that never changes.</p>
<p>I wish more practitioners embraced this simple concept.  While some do, many still don&#8217;t.  There&#8217;s often a rush to come up with a standard set of decision criteria to drive the work based on factors not necessarily aligned with risk factors.   Those who have worked with or for me will tell you that when presented with questions about which vendors or applications to assess or what to look for when conducting any type of assessment my first line of logic is to try and figure out where the greatest possible exposures to be found.   Assessing a low risk application yields little value  no matter how complete it may be.  And reviewing a vendor where the dollar spend is high but the risk factors are low does little to protect the institution.</p>
<p>Beware the practitioner who wields a hammer for they only know to look for nails.</p>
<p>Your regulator doesn&#8217;t want you to blindly implement compliance programs, they want you to identify and manage risks, real risks.  They want to be able to understand the logic and approach being used and find credible evidence that you&#8217;re focusing your efforts on the right things.   Go back and read through the library of FFIEC documentation and pay close attention to the hooks inserted throughout where they talk about conducting assessments and talk about using approaches which are appropriate for the size and complexity of your institution.  Then scan through your related program inventory and figure out if you&#8217;ve designed things accordingly.  Are they actually protecting your institution from credible threats and risks or are they just filling binders on your compliance officers shelves?</p>
<p>For me, professionally I&#8217;d prefer to always only do meaningful work and in the audit and assurance world meaningful is code for risk-based.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/regulatory-compliance/risk-the-core-issue-behind-regulatory-requirements/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>BITS Shared Assessment &#8211; No Free Lunch.</title>
		<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance/bits-shared-assessment-no-free-lunch/</link>
		<comments>http://itknowledgeexchange.techtarget.com/regulatory-compliance/bits-shared-assessment-no-free-lunch/#comments</comments>
		<pubDate>Thu, 16 Feb 2012 17:49:30 +0000</pubDate>
		<dc:creator>David Schneier</dc:creator>
				<category><![CDATA[BITS]]></category>
		<category><![CDATA[COBIT]]></category>
		<category><![CDATA[compliance]]></category>
		<category><![CDATA[GLBA]]></category>
		<category><![CDATA[ISACA]]></category>
		<category><![CDATA[ITGI]]></category>
		<category><![CDATA[NCUA]]></category>
		<category><![CDATA[regulatory]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[Shared Assessement]]></category>
		<category><![CDATA[SIG]]></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=876</guid>
		<description><![CDATA[Since first encountering the Shared Assessment a few years back I've always thought of it as bloated, difficult to effectively apply and all at once redundant and oddly vague.  The very first time I reviewed the content I immediately thought that whoever was behind creating it must be people who get paid by the hour because any attempt at relying on it was going to be major league time consuming.]]></description>
				<content:encoded><![CDATA[<p>On Monday the BITS Shared Assessment was free, on Tuesday it cost $5,000 per year (at a minimum).</p>
<p>My first thought was that it was just like what drug dealers do &#8211; they give you free product until you&#8217;re hopelessly addicted and then start making you pay to feed that addiction.  My second thought was that I couldn&#8217;t imagine anyone actually wanting to pay for the content.  While it&#8217;s better than nothing as a framework it&#8217;s not that much better.  I&#8217;m sure there are certain pockets in the GRC industry who think that the Shared Assessment is to vendor management what COBIT is to IT governance but I certainly don&#8217;t.</p>
<p>Since first encountering the Shared Assessment a few years back I&#8217;ve always thought of it as bloated, difficult to effectively apply and all at once redundant and oddly vague.  The very first time I reviewed the content I immediately thought that whoever was behind creating it must be people who get paid by the hour because any attempt at relying on it was going to be major league time consuming.  And of course once I started investigating the companies behind developing the questionnaire(s) I realized I was spot on.  I once commented to a colleague that the questionnaire looked as if though the purpose of the collective assignment was to think of every possible question you might ever want to ask a vendor, throw it into a spreadsheet and then try and organize it after the fact.  If I&#8217;ve ever truly liked it in any meaningful way it&#8217;s as a reference source when considering questions to include in customized questionnaires and assessment.</p>
<p>The folks running the show have made strides to truly make the questionnaire into a framework with accompanying methodology but in my experiences most companies simply want to leverage the content of the questionnaires and use it how they see fit.  Some have made the effort to dig through the massive pile of questions and whittle it down to something more manageable while others pretty much ship it out as is to their vendors including both the lite and full versions.  As someone whose practice often has to complete due diligence questionnaires I have to tell you that if we needed to fill out even the lite version it might be a deal breaker due to time constraints.</p>
<p>As I alluded to earlier, I think many practitioners who use the Shared Assessment think of it as being something more like COBIT.  I know COBIT and you sir are no COBIT.  It&#8217;s really intended to be used by large vendors who provide services to multiple clients as something akin to a SAS 70/SSAE 16 report.  They pay someone to complete it for them and sign off on it and when their customers look for annual proof that they&#8217;re properly controlled they can send along a copy of the completed questionnaire with managements approval stamped on the cover.  In theory it&#8217;s a good idea but I&#8217;d still prefer a proper audit instead.</p>
<p>And it&#8217;s heavily geared towards technology vendors and to a lesser extent those who host services.  When you try and use the Shared Assessment for non-technology vendors it becomes that much more difficult to apply and sort of forces your hand into coming up with something else.  Trying to whittle 900+ questions down to something smaller only to discover you need to write a bunch of new questions on top of that has to be something between depressing and outrageous I would think.</p>
<p>What I really don&#8217;t understand is why this was even needed to begin with.  My vendor management experience goes back several years and I&#8217;ve always been satisfied working with content from existing sources.  I think that when you combine content from COBIT and FFIEC you can adequately  cover what needs to be covered to assess vendors.  I would go so far as to say that most examiners would agree with me based mostly on the fact that there are more than 100 institutions using some version of a vendor management program my practice has designed and they always do well on that front, always.</p>
<p>For those of you who are going to stay the course, cough up the money and continue along with the Shared Assessment I wish you good luck.  I hope you&#8217;re able to glean something meaningful from the process and I pray you never wind up working for a vendor that needs to complete one of the resulting questionnaires.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/regulatory-compliance/bits-shared-assessment-no-free-lunch/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why vendor management is a big GLBA deal.</title>
		<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance/why-vendor-management-is-a-big-glba-deal/</link>
		<comments>http://itknowledgeexchange.techtarget.com/regulatory-compliance/why-vendor-management-is-a-big-glba-deal/#comments</comments>
		<pubDate>Fri, 18 Nov 2011 12:22:17 +0000</pubDate>
		<dc:creator>David Schneier</dc:creator>
				<category><![CDATA[assessment]]></category>
		<category><![CDATA[Audit]]></category>
		<category><![CDATA[compliance]]></category>
		<category><![CDATA[FDIC]]></category>
		<category><![CDATA[Federal Reserve Bank]]></category>
		<category><![CDATA[FRB]]></category>
		<category><![CDATA[GLBA]]></category>
		<category><![CDATA[NCUA]]></category>
		<category><![CDATA[OCC]]></category>
		<category><![CDATA[OTC]]></category>
		<category><![CDATA[regulations]]></category>
		<category><![CDATA[regulatory]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[risk]]></category>
		<category><![CDATA[risk assessment]]></category>
		<category><![CDATA[vendor]]></category>
		<category><![CDATA[Vendor Management]]></category>
		<category><![CDATA[vendor risk]]></category>
		<category><![CDATA[vendor risk rating]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/regulatory-compliance/?p=836</guid>
		<description><![CDATA[Vendor management is seldom a thinking exercise but rather an attempt to standardize on what artifacts are required in order to prove compliance with the program.  It blows me away how this important activity gets boiled down to something little better than a baseball card collection.]]></description>
				<content:encoded><![CDATA[<p>I don&#8217;t think I&#8217;m due to post about vendor management again at least until January 2012 (I try to limit topics to twice a year) but I&#8217;ve had something kicking around my head for a few days now and it needs a proper vetting.</p>
<p>Does anyone know why vendor management is such a big issue for banking regulators?  I mean, I&#8217;ve long advocated that most of what GLBA covers makes sense and should be part of a healthy business strategy anyway.  But when working with clients I&#8217;m often surprised to discover that they just see it as another something they have to do and don&#8217;t fully appreciate why that is.  So does anyone know?</p>
<p>One of the basic tenets of GLBA, perhaps the MOST basic goal is to protect customers sensitive data.  Sure you can make the argument that it has hooks into disaster recovery and business continuity planning, both also covered by regulatory requirements.  And you can also claim it has to do with service level agreements and gauging the vendors performance.  But really in the end the primary driver behind why your regulator wants you to do a better job of managing your vendors is to make sure they&#8217;re protecting your customers where applicable.  Think about it, it&#8217;s so simple it&#8217;s almost too simple.</p>
<p>Which is why I&#8217;m always amazed how so many institutions fail to not only figure out what they need to do but also never really seem to get where they need to be.  It so often becomes about the document collecting game; do they have a SAS 70?  Do they have an Information Security Program?  Who cares?  That&#8217;s not what vendor management is intended to address.  What you&#8217;re really supposed to do is step back and assess the nature of the relationship, the types of products and/or services the vendor provides and try and identify where threats to your customers sensitive information may exist.  Vendor management is seldom a thinking exercise but rather an attempt to standardize on what artifacts are required in order to prove compliance with the program.  It blows me away how this important activity gets boiled down to something little better than a baseball card collection.</p>
<p>I offer for example my favorite blind spot in every vendor management program I&#8217;ve ever conducted a first ti me review of.  Where&#8217;s the information for the vendor who cleans the facilities? It&#8217;s almost always contracted out and the vendor who owns the contract is responsible for staffing the work.  Where&#8217;s proof that they properly screen the people they&#8217;re sending into your allegedly secure facilities to make sure they&#8217;re not convicted felons?  Where&#8217;s proof that they properly police their crews to make sure they&#8217;re not behaving in a reckless manner and perhaps letting their friends and family into your secured facilities to drop off dinner or stop by and say &#8220;hello&#8221;?  When I challenge the clients on this relationship they look at me like I&#8217;m nuts.  Almost all of them fail to even include that particular vendor (and those who do tend to include every single vendor they&#8217;ve ever done any business with &#8211; another big issue).  But all you&#8217;ll ever need to do in order to see why this is a potentially huge threat is to walk around the office after hours and see what&#8217;s been left out on desks, in printer and fax queues and examine what sort of documentation has been tossed in with the regular trash.</p>
<p>And because vendor management is never truly approached from the right angle it fails to address the very spirit of the exercise and why the three senators who authored GLBA wanted you to pay more attention to it.  But it really reveals a fundamentally bigger issue with most of the compliance domain &#8211; no one really approaches most of the work with a true risk oriented perspective.  Compliance isn&#8217;t simply about creating checklists and ticking off all the to-do&#8217;s &#8211; it&#8217;s about really trying to identify relevant risks and make sure your institution has controls in place to manage them properly.  And I know for those of you who read my blog with any regularity you&#8217;re thinking I&#8217;ve written about this before.   That&#8217;s true, I bring this up every chance I get because it&#8217;s still a huge issue and those of us who have any practitioners attention need to constantly bang on this particular drum.</p>
<p>This is one of the reasons why whenever I&#8217;m given a chance to discuss how any of my clients approaches vendor management I try never to tell them what they need to do but rather try and instead have a conversation about what they think they should be doing.  The back-and-forth often helps them expand on their thinking and come up with better, more effective ways in which they can properly categorize and assess their business relationships.</p>
<p>Oh and as for my &#8220;Who cares&#8221; comment about collecting documentation, there&#8217;s a place for that to be sure.  But when you tell your examiner or auditor that you&#8217;re OK because the vendor provided a recent SAS 70 and can&#8217;t really discuss any of the details you&#8217;ve fallen way short of what you needed to do.  Waving documentation in my face never convinces me you&#8217;ve done your job and it absolutely never proves that your customers sensitive information is protected.  Remember, SAS 70&#8242;s (and now SSAE 16) are subjective and what each one covers can vary wildly from one to another.  And it absolutely does not prove that they&#8217;ve successfully addressed all the items in your checklist either.  One of my favorite cut-through-the-weeds tricks is to pick a single checklist item and ask the person waving the report to show me where that&#8217;s addressed in the report.  I&#8217;ve met a few who could do it and prove to me they&#8217;ve actually read the thing but most just start flipping through pages like a poorly prepared student during an open book exam.</p>
<p>Why is this so hard for so many to do a reasonable job on?</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/regulatory-compliance/why-vendor-management-is-a-big-glba-deal/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
