 




<?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; business continuity</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/regulatory-compliance/tag/business-continuity/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>Hurricane Sandy: An epic storm and the ultimate DR test</title>
		<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance/hurricane-sandy-an-epic-storm-and-the-ultimate-dr-test/</link>
		<comments>http://itknowledgeexchange.techtarget.com/regulatory-compliance/hurricane-sandy-an-epic-storm-and-the-ultimate-dr-test/#comments</comments>
		<pubDate>Tue, 30 Oct 2012 15:09:04 +0000</pubDate>
		<dc:creator>David Schneier</dc:creator>
				<category><![CDATA[Audit]]></category>
		<category><![CDATA[audits]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[bank]]></category>
		<category><![CDATA[bank closing]]></category>
		<category><![CDATA[bank closings]]></category>
		<category><![CDATA[banking]]></category>
		<category><![CDATA[banks]]></category>
		<category><![CDATA[BIA]]></category>
		<category><![CDATA[business]]></category>
		<category><![CDATA[business continuity]]></category>
		<category><![CDATA[business continuity plan]]></category>
		<category><![CDATA[business impact analysis]]></category>
		<category><![CDATA[community bank]]></category>
		<category><![CDATA[disaster recovery]]></category>
		<category><![CDATA[DR]]></category>
		<category><![CDATA[examiners]]></category>
		<category><![CDATA[internal audit]]></category>
		<category><![CDATA[internal controls]]></category>
		<category><![CDATA[ITGC]]></category>
		<category><![CDATA[NCUA]]></category>
		<category><![CDATA[pandemic]]></category>
		<category><![CDATA[Pandemic Planning]]></category>
		<category><![CDATA[policy]]></category>
		<category><![CDATA[procedure]]></category>
		<category><![CDATA[risk assess]]></category>
		<category><![CDATA[risk assessment]]></category>
		<category><![CDATA[risk assessments]]></category>
		<category><![CDATA[risk management]]></category>
		<category><![CDATA[risks]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/regulatory-compliance/?p=1004</guid>
		<description><![CDATA[I&#8217;ve written similar posts in that past where I start off by apologizing for appearing opportunistic when leveraging a significant news event to generate site content.  However when considering roughly one-third of all my clients are dealing with Hurricane Sandy this represents a rare chance to drive home a point. I&#8217;ve personally reviewed and/or audited [...]]]></description>
				<content:encoded><![CDATA[<p>I&#8217;ve written similar posts in that past where I start off by apologizing for appearing opportunistic when leveraging a significant news event to generate site content.  However when considering roughly one-third of all my clients are dealing with Hurricane Sandy this represents a rare chance to drive home a point.</p>
<p>I&#8217;ve personally reviewed and/or audited somewhere close to fifty business continuity/disaster recovery (BCP/DR) plans over the past decade.  I&#8217;ve also written or edited several of those as well in the past five years since moving into professional services for financial institutions.   Furthermore I&#8217;ve participated in roughly a half-dozen tests while still working within the infrastructure during the first part of my career.  Suffice to say I have at least an informed opinion regarding the viability of any such BCP/DR strategies.</p>
<p>Fundamentally there are a few varieties of  BCP/DR plans:  Those that are current and viable, those that convince your examiner that it&#8217;s current and viable and those that may have been viable years ago but bear no resemblance to your current business profile.  And beyond those there&#8217;s the worst of BCP/DR realities, the non-existent one.  But really in the end what your current state of preparedness comes down to is this &#8211; either you&#8217;re ready for an event or you&#8217;re not.   And in the past forty-eight hours that&#8217;s been made abundantly clear in the form of how many of my clients affected by Hurricane Sandy have navigated through what&#8217;s now clearly one of the worst weather events in my lifetime.</p>
<p>Around noontime yesterday (October 29, 2012) as weather conditions worsened and major metropolitan areas were literally shutting down for business I started checking up on a few clients.  The first thing I did was visit the website of every client that my practice has assisted with their BCP/DR strategy &#8211; each of them had updated their website to announce that branches in the affected areas were closed.  Some had a pop-up window with the update, others had a message displayed in either bright red letters, bold font or both.  As a standard design consideration each of them also had phone numbers clearly displayed and when I called a sampling real people answered and were available to assist me.  I inquired of a few of them where they were physically located and they were all located remotely and not on site in affected areas (much to their credit they were reluctant to share too much information).   The second thing I did was visit the website for a few clients whose BCP/DR plans were tagged during an audit/assessment as either being deficient or missing.  The websites were not updated and in all but one case I only learned that they were closed for the day after calling into a branch (one had an 800 number that was redirected to a real person).</p>
<p>Now I know this wasn&#8217;t a very deep or meaningful test of anyone&#8217;s ability to continue operations in the event of a disaster.   But what it did prove is that those institutions who had plans that were current and whose management team knew to rely upon had already thought through the little things that make a difference.   Someone knew to update the website, management knew to reroute calls away from unmanned branch locations.  I can only assume that the appropriate parties desginated to do so also contacted their regulators to inform them of their closing and that a phone chain was initiated informing staff thus keeping them off the roads and safe.  And because an important part of the plan creation/update process is both training and testing stakeholders are able to navigate through the decision tree and take appropriate related steps without having to think through it &#8211; one of the biggest challenges confronting management during a crisis.  The very best part of having a viable and current plan is that all the thinking has been done in advance and has been reviewed and validated which greatly reduces the chances that something (or someone) will be missed.</p>
<p>Here&#8217;s a sanity test:  If you didn&#8217;t know exactly where to begin the decision-making process or who to engage you&#8217;re in need of a new plan.  And if you did know but can&#8217;t be absolutely certain that others would be able to do the same in your absence, you&#8217;re in need of a new plan.  One of the rebuttals I&#8217;ve heard all too often when identifying a deficient or missing BCP is that management knows what to do should some manner of disaster strike.  That may be true but what happens if key people are unavailable or can&#8217;t be reached?</p>
<p>Seriously, when something like Hurricane Sandy occurs it&#8217;s the best time to consider how you&#8217;re institution would fare when navigating such an event.  Block off an hour within the next week with your key people, pull out your BCP/DR documentation and try and step through how you&#8217;d handle things under similar circumstances.  In a very short time you&#8217;ll gain a sense of whether or not you&#8217;re prepared and if necessary afford you the opportunity to improve.</p>
<p>Trust me on this &#8211; you don&#8217;t want to be in the middle of a disaster scenario and find out that your plan doesn&#8217;t work.</p>
<p>&nbsp;</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/regulatory-compliance/hurricane-sandy-an-epic-storm-and-the-ultimate-dr-test/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Dodd-Frank Section 165(d) : Is this really what was needed?</title>
		<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance/dodd-frank-section-165d-is-this-really-what-was-needed/</link>
		<comments>http://itknowledgeexchange.techtarget.com/regulatory-compliance/dodd-frank-section-165d-is-this-really-what-was-needed/#comments</comments>
		<pubDate>Mon, 03 Oct 2011 22:39:11 +0000</pubDate>
		<dc:creator>David Schneier</dc:creator>
				<category><![CDATA[bcp]]></category>
		<category><![CDATA[business continuity]]></category>
		<category><![CDATA[business continuity plan]]></category>
		<category><![CDATA[compliance]]></category>
		<category><![CDATA[Dodd-Frank]]></category>
		<category><![CDATA[FDIC]]></category>
		<category><![CDATA[GLBA]]></category>
		<category><![CDATA[NCUA]]></category>
		<category><![CDATA[regulations]]></category>
		<category><![CDATA[regulatory]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[too big too fail]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/regulatory-compliance/?p=817</guid>
		<description><![CDATA[If they can't successfully design a viable BCP when that's something they've often enough desperately needed how are they supposed to design a viable plan to dissolve their business relying entirely on speculation and imagination?  Seriously, was the lack of such a plan one of the the primary reasons that the banking behemoths weren't allowed to fail or was it simply our leadership being fearful that if a Citi or Chase went belly-up the economy might never recover?]]></description>
				<content:encoded><![CDATA[<p>Ever since Dodd-Frank legislation first started rolling down the turnpike towards the banking industry I&#8217;ve been reading and listening to all manner of rhetoric about how none of it&#8217;s going to solve any problems, that it&#8217;s going to impede the business of banking and force money to be deposited and invested outside of the borders of the U.S.A.  And to be fair, most of what has been enacted seems more to be a nuisance rather than a solution.</p>
<p>So with the ratifying of the most recent bit of the legislation by the FDIC last month I&#8217;m all the more curious to see how the industry reacts.  For those of you who don&#8217;t know what it is I&#8217;m referring to it&#8217;s Section 165(d) &#8211; the new law that requires banks with non-banking assets in excess of $50B to draft a plan that would in effect put its sponsoring institution out of business in a neat and orderly fashion.  Or rather, as I&#8217;ve come to think of it, it&#8217;s a Business Continuity Plan of a whole &#8216;nother color (or perhaps it&#8217;s simply a Business Discontinuity Plan &#8211; BDP).</p>
<p>Think about what this law requires.  Banks that are in-scope for this now have to draft a plan that would allow regulators to step in and break off the various spokes of the wheel and either sell things off or shut them down in a way that is as minimally disruptive to the financial system as is possible.  What I don&#8217;t understand about this is how would that even be possible?</p>
<p>You&#8217;d have to make an awful lot of assumptions to even draft such a plan.  In 2007 when the banks started spiraling out of control you would have thought the very first thing to do was to divest themselves of the root cause of the problem, their consumer loan portfolio and primarily their mortgage business.  But who was buying that pile of rotting paper for anything other than pretend money (how&#8217;d Countrywide make out playing that market)?  So documenting in a plan that you&#8217;d sell off your various units assumes that there&#8217;s a market looking to buy them and you can&#8217;t really count on that, can you?  The truth of the matter is all you can really lay down on paper is a very high-level approach that specifies how each segment of the business needs to be evaluated to determine what if any value it possesses and than shop it to the market and see if there&#8217;s a buyer.   But how is that any different then how a business is dissolved in bankruptcy?  And we already have all sorts of laws on the books to guide <span style="text-decoration: underline">that </span>process.</p>
<p>How do you even test such a plan?  In order for this legislation to deliver on its promise the regulators would need to know that the plan would work somewhere close to as it&#8217;s designed to if ever it was needed.  How can you possibly step through it and know for sure?  Wouldn&#8217;t the various markets need to participate as well and how reliable would that be?  Wouldn&#8217;t everyone need to pretend that it was real?  Say Citi, would you be willing to buy BoA&#8217;s commercial loan portfolio and if so, how much would you be willing to pay for it?  If I&#8217;m Citi I&#8217;m thinking make the pretend offer high because it&#8217;s not binding and if a once in a lifetime disaster occurs again we can totally low-ball on the real offer if it ever comes to that.  So how reliable is that test?</p>
<p>But here&#8217;s the thing that keeps tap-tap-tapping away at the back of my mind &#8211; those who have to comply are the same institutions who can&#8217;t successfully design, implement and support a viable business continuity plan and that&#8217;s something they&#8217;ve had years to perfect and still haven&#8217;t even come close to doing.  And they&#8217;ve actually had disruptions where they needed to rely on these plans and still haven&#8217;t quite gotten them done right.  If they can&#8217;t successfully design a viable BCP when that&#8217;s something they&#8217;ve often enough desperately needed how are they supposed to design a viable plan to dissolve their business relying entirely on speculation and imagination?  Seriously, was the lack of such a plan one of the the primary reasons that the banking behemoths weren&#8217;t allowed to fail or was it simply our leadership being fearful that if a Citi or Chase went belly-up the economy might never recover?</p>
<p>Lewis Black loves to poke fun at the whole banking mess and about how banks were instructed by Capital Hill shortly after things got ugly to make sure that before making a loan they needed to be certain the person has the financial wherewithal to repay it.  He suggested that the next piece of direction should have been to remind the banking leaders to breath occasionally because it was about as simplistic and obvious.  Well perhaps the lawmakers should have kept things simple here as well.  Rather than require a BDP, let the FDIC oversee things as they have for many, many years and shepherd a failing institution through the various stages of liquidation finding suitable buyers for the pieces that are worth selling off or that need to be absorbed.  Sure the bigger institutions would present some issues and complexities that would require a certain degree of creative thinking but isn&#8217;t that better than trying to rely on a plan that was conceived of pure speculation and whimsy?</p>
<p>The real problem wasn&#8217;t that any of the monster banks couldn&#8217;t fail, it was that they weren&#8217;t allowed to.  Even if any of them had something drafted that specified how they should be dismantled the government wouldn&#8217;t have let it happen.  Much like a financial institution tends to look at their BCP well after the disruption occurred (happens all the time) I suspect a BDP would serve in much the same capacity.  And if I was an examiner and was going to hold the feet of one of my institutions to the fire for something I&#8217;d rather they focus on having an actual, honest-to-goodness BCP that would help them navigate the next hurricane, earthquake, blizzard, blackout, etcetera rather than preparing for something that may never happen again.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/regulatory-compliance/dodd-frank-section-165d-is-this-really-what-was-needed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A new twist on regulatory guidance.</title>
		<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance/a-new-twist-on-regulatory-guidance/</link>
		<comments>http://itknowledgeexchange.techtarget.com/regulatory-compliance/a-new-twist-on-regulatory-guidance/#comments</comments>
		<pubDate>Wed, 14 Sep 2011 06:27:31 +0000</pubDate>
		<dc:creator>David Schneier</dc:creator>
				<category><![CDATA[assessment]]></category>
		<category><![CDATA[Audit]]></category>
		<category><![CDATA[bcp]]></category>
		<category><![CDATA[business]]></category>
		<category><![CDATA[business continuity]]></category>
		<category><![CDATA[business continuity planning]]></category>
		<category><![CDATA[compliance]]></category>
		<category><![CDATA[disaster recovery]]></category>
		<category><![CDATA[DR]]></category>
		<category><![CDATA[GLBA]]></category>
		<category><![CDATA[NCUA]]></category>
		<category><![CDATA[regulation]]></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>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/regulatory-compliance/?p=805</guid>
		<description><![CDATA[What if the examiners created a list of findings and issues culled directly from their reports and compiled them in a repository?  They could make the verbiage appropriately anonymous to avoid any privacy issues but share with the public what it is they're finding out in the field.  The findings can be sortable based on the related requirement and or size/complexity of the institution so that any institution that shares the regulator can figure out where they may have issues. ]]></description>
				<content:encoded><![CDATA[<p>One of the oddity&#8217;s of my career is how some issues present themselves in a wide range of my clients despite the fact that there&#8217;s often no meaningful way to compare them in size.  Some have a single compliance person who is part Compliance Officer and part Information Security Officer and some have true CISO&#8217;s, Chief Compliance Officers and even Chief Risk Officers who themselves have teams of resources reporting into them.  And so you&#8217;d think that many of the challenges that confront them would look about as different.  Sometimes they do but many times (and more than you&#8217;d likely believe) they&#8217;re all staring down the same exact problems.</p>
<p>Most of what I do falls under GLBA-defined requirements and what that really means is that any institution I work with has identical goals.  The designs of the related programs and procedures certainly can look different because everything that falls under the guidance of FFIEC is supposed to be adjusted based on the size and complexity of your institution.  But they all need to conduct risk assessments, they all need to have current, up-to-date and recently tested business continuity plans, they all need to have viable vendor management programs and so on and so on&#8230; And I have many years of experience building out and/or supporting these very activities and know quite clearly what works, what doesn&#8217;t, what presents well to the examiners and what falls well short of expectations.</p>
<p>Sometimes though I&#8217;m caught off guard when a client rejects my advice because they&#8217;re confidant that what they&#8217;re doing or intending to do is consistent with their examiners expectations.  I&#8217;m a fan of confidence, I sort of dabble a bit in the discipline myself and appreciate how it can be very effective when trying to sell something to the audience.  But with regards to compliance there&#8217;s really not a whole lot of wiggle room.  In fact sometimes it can be interpreted as binary &#8211; either you&#8217;re compliant or you&#8217;re not.  So when I encounter a client who hasn&#8217;t updated or tested their BCP in years (if ever) and tell them that&#8217;s going to be a problem with their regulator I recoil when their reply is the dreaded &#8220;well the examiners haven&#8217;t had anything to say about it&#8221;.   &#8220;Yet&#8221;, I typically reply, &#8220;they haven&#8217;t had anything to say about it yet.&#8221;  All because the examiners haven&#8217;t dinged you for something doesn&#8217;t mean that you&#8217;re in good shape, it often means that they simply had bigger issues to focus on and haven&#8217;t quite gotten to it.  I have a list longer than my arm regarding vendor management and the common mistakes most institutions make and how those mistakes are going to lead to trouble with the examiners.  But when I bring this to the attention of the appropriate stakeholders I&#8217;m often treated as if though I&#8217;m simply trying to sell them my services and not giving them solid advice.  It can be very frustrating particularly because our practice was built on giving out solid and oft times free advice.  We&#8217;re willing to make the trade-off between generating revenue and doing right by our clients.  However you can lead a horse to water, but, well y&#8217;know.</p>
<p>I have an idea, maybe a great idea that might help solve the problem.  What if the examiners created a list of findings and issues culled directly from their reports and compiled them in a repository?  They could make the verbiage appropriately anonymous to avoid any privacy issues but share with the public what it is they&#8217;re finding out in the field.  The findings can be sortable based on the related requirement and or size/complexity of the institution so that any institution that shares the regulator can figure out where they may have issues.  Remember, the purpose of compliance and the regulators charged with ensuring that it&#8217;s being addressed satisfactorily is to protect us, the customer.  So it&#8217;s a very good thing to use all available resources to make sure that everything that can be done to make that happen is being done.  If your bank or credit union is able to access such a repository and use that information to identify where they&#8217;re weak or deficient doesn&#8217;t that help protect all of our sensitive information?  And it also removes the thin veil of ignorance associated with the logic that all because your examiner hasn&#8217;t documented any issues with a particular activity that must mean that you&#8217;re doing things right.  And when a client tells me that they don&#8217;t need to conduct a periodic review of all high risk vendors I can show them where that&#8217;s recently been an issue in a report.  Or when they tell me that testing their DR plan satisfies the need to test the BCP it&#8217;s part of I can show them how that logic failed to hold up under recent scrutiny.</p>
<p>Really in the end this isn&#8217;t so different than what happens now.  All of us practitioners gather information from the field regarding what the examiners are focusing on and use that information to update our own guidance and advice.  For example, when we recently heard that examiners are looking for greater scrutiny to be placed on SLA tracking as part of the vendor management program we made sure to include that advice in any of our audit and assessment reports.  But why should the industry need to rely on an informal approach?  Why not make it formal, take ownership and put the right information in the right hands to affect the desired results?</p>
<p>Is this idea a bit self-serving?  Sure, at least a little.  But really in the end if it helps get the right things done and in place who really cares?  If I can prove to a client that a Red Flags program that&#8217;s recorded only a handful of incidents during the previous twelve months is likely ineffective and be able to get them to do something about it everybody wins.  And can something like the proposed repository actually happen?  Maybe.  I&#8217;m sure the lawyers would weigh in with all kinds of issues.   But it&#8217;s difficult to argue against the merits of such an offering and in this age of greater accountability this would potentially be well received.</p>
<p>Anyone have any better ideas?</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/regulatory-compliance/a-new-twist-on-regulatory-guidance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Will Hurricane Irene reveal your BCP&#8217;s strengths or weaknesses?</title>
		<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance/will-hurricane-irene-reveal-your-bcps-strengths-or-weaknesses/</link>
		<comments>http://itknowledgeexchange.techtarget.com/regulatory-compliance/will-hurricane-irene-reveal-your-bcps-strengths-or-weaknesses/#comments</comments>
		<pubDate>Sun, 28 Aug 2011 15:17:45 +0000</pubDate>
		<dc:creator>David Schneier</dc:creator>
				<category><![CDATA[Audit]]></category>
		<category><![CDATA[auditor]]></category>
		<category><![CDATA[bcp]]></category>
		<category><![CDATA[business continuity]]></category>
		<category><![CDATA[business continuity plan]]></category>
		<category><![CDATA[compliance]]></category>
		<category><![CDATA[disaster]]></category>
		<category><![CDATA[disaster recovery]]></category>
		<category><![CDATA[DR]]></category>
		<category><![CDATA[exam]]></category>
		<category><![CDATA[examiner]]></category>
		<category><![CDATA[GLBA]]></category>
		<category><![CDATA[NCUA]]></category>
		<category><![CDATA[regulations]]></category>
		<category><![CDATA[regulatory]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/regulatory-compliance/?p=799</guid>
		<description><![CDATA[The worst time to discover that you need a viable plan and don't have one is, well, when you actually need it.  If enduring both an epic hurricane and your first earthquake don't inspire you to action nothing will.]]></description>
				<content:encoded><![CDATA[<p>I&#8217;m violating my own standards by using such an easy topic to blog about but it&#8217;s too big to ignore.  With the increasing insanity being inspired by 2011&#8242;s first true hurricane I&#8217;d be remiss if I didn&#8217;t at least explore the impact this is going to have on the business community.</p>
<p>I just heard that Mayor Bloomberg is evacuating low-lying areas in New York City and that mass transit will more or less be cut off tomorrow (Saturday) sometime around mid-day.  New York&#8217;s Governor Cuomo also discussed the possibility of closing the bridges as well if weather conditions become so severe that using them might be dangerous.  Upon hearing this my first thought was &#8220;how the heck are key stakeholders going to get to their disaster sites if they&#8217;re called in?&#8221;  The obvious answer is that many companies will likely require that the important people go to their DR sites tonight so that they&#8217;re already there &#8220;just in case&#8221;.  How wonderful for these people to have to leave their families in the midst of a potentially epic natural disaster.  I can&#8217;t help but wonder how many are willing to comply and how many are going to insist that they can&#8217;t make it.  Did any BCP/DR test ever take into consideration the possibility that key stakeholders would simply refuse to show up?</p>
<p>And with the enormous range of Hurricane Irene is it at all possible that certain recovery sites might not be able to provide the proper services, resources and support to meet such a potentially large demand?  I know that they all claim that they&#8217;ve factored that in to their models and are able to provide sufficient capacity.  But until they know for sure how do they really know for sure?  Who among us has yet to witness any BCP/DR plan that didn&#8217;t start experiencing hiccups and delays during testing?</p>
<p>One element of a BCP that I&#8217;m also now wondering about is the day-after scenario.  I&#8217;ve reviewed dozens of plans during my career and upon reflection cannot recall any that placed significant attention on what happens after the official disruption is at an end.  I&#8217;m looking at pictures of severe flooding from Irene from those places already affected and have to wonder how many business are going to be able to open on Monday despite the fact that the roads are clear and the skies sunny and blue.  In thinking about some of the more common disruptions over the years (e.g. heavy snow, ice, etc.) it was somewhat obvious that once the roads were passable it was safe to head back to the office.  But that may not be the case this time around.  How many plans are designed to accommodate that?  Is someone from facilities charged with the responsibility of conducting a site inspection on Sunday night to see if their buildings are ready to open the next day?</p>
<p>Admittedly I&#8217;m picking on the entire concept of a business continuity plan but you can&#8217;t blame me, Hurricane Irene is only one reason.  Middle of last week I was in the Northeast and experienced my very first earthquake event.  Now I realize that anyone from California or Japan would chuckle at that statement because what I personally experienced was little more than an overloaded truck driving past me on a pothole-ridden street to those who deal with the phenomenon regularly.  But still, for me it was a big deal.  In the aftermath I asked around to see what happened in other places where the tremors were felt to see if anyone was formally evacuated from their building &#8211; no one was.  I expected in the days following to read about how companies had dedicated time and resources to inspect their structures to ensure that everything was as it should be and that there were no signs of damage from the unexpected movements &#8211; again, almost nothing to be found.  Well for all those BCP&#8217;s that I&#8217;ve reviewed where the likely threats were documented and addressed as part of their plan, how many think that maybe they should update their documentation to cover earthquakes?  They can no longer justify leaving it out because it&#8217;s not a likely threat, it just happened.  And now that they know it happened once they need to accept that it not only could happen again but likely will. But I&#8217;m willing to bet that a year from now I won&#8217;t find a single plan that has been modified to include what should happen in the event of an earthquake.</p>
<p>I&#8217;m just thinking that regulators and auditors need to stop rewarding those they&#8217;re responsible for monitoring for simply having a plan in place.  At some point they&#8217;ll need to shift their focus from simply checking off that a plan exists and start digging into it a bit more.  The same degree of scrutiny that emerged in 2009 because of the &#8220;Great Swine Flu&#8221; threat and making sure that BCP&#8217;s had a thorough pandemic response component now needs to become standard fare for the overall plan.  Companies need to conduct more than tacit testing exercises and really start thinking things through.  Between companies having antiquated and irrelevant plans, to those who have partially baked plans and worse yet, those who don&#8217;t even have one in place it&#8217;s time to do something about it.</p>
<p>The worst time to discover that you need a viable plan and don&#8217;t have one is, well, when you actually need it.  If enduring both an epic hurricane and your first earthquake don&#8217;t inspire you to action nothing will.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/regulatory-compliance/will-hurricane-irene-reveal-your-bcps-strengths-or-weaknesses/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Hard Lesson Learned in Japan&#8217;s Disaster</title>
		<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance/a-hard-lesson-learned-in-japans-disaster/</link>
		<comments>http://itknowledgeexchange.techtarget.com/regulatory-compliance/a-hard-lesson-learned-in-japans-disaster/#comments</comments>
		<pubDate>Fri, 25 Mar 2011 14:48:38 +0000</pubDate>
		<dc:creator>David Schneier</dc:creator>
				<category><![CDATA[business continuity]]></category>
		<category><![CDATA[business continuity plan]]></category>
		<category><![CDATA[business continuity planning]]></category>
		<category><![CDATA[disaster]]></category>
		<category><![CDATA[disaster recovery]]></category>
		<category><![CDATA[FFIEC]]></category>
		<category><![CDATA[GLBA]]></category>
		<category><![CDATA[NCUA]]></category>
		<category><![CDATA[regulations]]></category>
		<category><![CDATA[regulatory]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/regulatory-compliance/?p=670</guid>
		<description><![CDATA[But under either scenario it's almost entirely likely that the person(s) who stole the money had an idea about what to do and took advantage of the situation.  I mean, they obviously entered the bank after the disasters struck and they weren't likely looking for survivors if they were of a mindset to grab what had to be a sizable physical haul.]]></description>
				<content:encoded><![CDATA[<p>There will be no shortage of industry articles and analysis that will emerge from the horrific events in Japan over these past few weeks, that&#8217;s for certain.  This is arguably the most significant event to hit a major regional economy since World War II and it&#8217;s important to learn as many lessons from this tragedy as is possible.  My family are fans of the television show &#8220;Seconds from Disaster&#8221; and one thing it strives to illuminate is that by understanding what went wrong it&#8217;s often possible to make sure it won&#8217;t happen again.</p>
<p>Japan&#8217;s tragedy will serve as a fertile source of both proving and disproving the myriad business continuity and disaster recovery techniques being used around the world today.  The most prepared and best trained companies will have very likely fared about as well as could be expected while those who weren&#8217;t, those who either had partially baked plans or no plans at all will be lucky to survive in any measurable way.  And it&#8217;s hard to imagine that most companies didn&#8217;t have plans to deal with earthquakes and tsunami&#8217;s because they&#8217;re credible and consistent threats in the region.  But after a quarter century in corporate life and little more than half those years focusing on audit and compliance I&#8217;m no longer surprised by anything I encounter.</p>
<p>However there was one story to emerge from Japan this week that I found to be quite shocking.  It was about how a banks vault came open during the series of events and someone stole forty million yen (about $500k USD).  It happened in the prefecture of Myagi in a town known as <span>Kesennuma</span> and police said that <span>between the wave’s power and the ensuing power outages, the vault came open.  What with all the flooding and chaos it took more than a week for someone to get back into the building and discover what had happened.</span></p>
<p>For many the story seemed plausible if not mildly amusing because who wouldn&#8217;t love to wander into a bank and be able to scoop up all the cash floating around.  And because in this particular situation no one died or was hurt as a result it&#8217;s benign enough to be more entertaining than tragic.  It sort of reminded me of a scene in the movie &#8220;Ground Hog Day&#8221; where Bill Murray&#8217;s character figured out the perfect timing to be able to steal a bag of cash out of the back of an armored truck.</p>
<p>But I sort of have a problem with this story because I don&#8217;t think it happened the way it&#8217;s being portrayed.  My very first thought upon reading the details was that either someone left the vault door open as they were fleeing the bank or someone who knows a thing or two about how to open a vault went back in after the fact and exploited the situation to their advantage.  The odds that a vault door simply flew open due to what was really a massive flood at that point just doesn&#8217;t hold up under scrutiny.</p>
<p>Have you ever actually seen what a door on a bank vault looks like?  I have and I&#8217;ve probably seen about three dozen or more since I started working in the banking sector and I couldn&#8217;t think of how any one of them, if closed properly would ever just come open due to rushing water for a relatively short period of time.  First of all they&#8217;re all seated within a metal frame and so for the rods or pistons that create the seal to come undone the metal itself would need to have been bent or twisted.  Second, they weigh a ton (not as much of an exaggeration as you might think).  Even the weakest vaults I&#8217;ve encountered have doors that have some serious density to them and would not likely bend under most natural forces.  I would sooner believe that the walls that the door and its frame were attached to failed then believe that the door simply &#8220;flew open&#8221;.</p>
<p>If I had to put on my most skeptical mindset to use I would venture a guess that the person responsible for making sure the vault was properly closed before safely exiting the building rushed through the procedure, didn&#8217;t properly lock the vault and in their heightened state of panic just didn&#8217;t think about it.  While that&#8217;s the most likely scenario the second most likely version is that someone who knows how to open the vault door and who knew after a day or so that no one would ever be concerned with theft while there were still lives to save made their way into the crippled building with its security systems down and manually opened the door and had at it.  But under either scenario it&#8217;s almost entirely likely that the person(s) who stole the money had an idea about what to do and took advantage of the situation.  I mean, they obviously entered the bank after the disasters struck and they weren&#8217;t likely looking for survivors if they were of a mindset to grab what had to be a sizable physical haul.</p>
<p>And the thing is that there&#8217;s no viable lesson to be learned from a story such as this.  I&#8217;m certain the bank had a procedure in place that specified how all cash drawers were to be placed in the vault and that the vault itself should be locked upon exiting during a disaster.  While in certain physical disaster scenarios it&#8217;s possible to install an individual to monitor the facility during and after the event this wasn&#8217;t one of those times as everyone needed to flee the area.  And having someone come back the next day to keep an eye on things was probably the last thing anyone associated with the bank was concerned with (and rightfully so) as they had lives to save and keep safe.</p>
<p>So no usable lesson to learn and probably no way to ever find out what really happened.  For my money I hope they find the people behind this because it makes me angry to think that while so many people struggled to search for survivors or to recover bodies there were people looking to profit from the situation.</p>
<p>And if there&#8217;s anything for the BCP community to glean from this story it&#8217;s that no plan can truly account for every possible scenario.  It&#8217;s a hard lesson to learn but perhaps one that serves a purpose if for no other reason than to underscore the need for adequate insurance coverage.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/regulatory-compliance/a-hard-lesson-learned-in-japans-disaster/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Are you GLBA compliant and ready for year-end?</title>
		<link>http://itknowledgeexchange.techtarget.com/regulatory-compliance/are-you-glba-compliant-and-ready-for-year-end/</link>
		<comments>http://itknowledgeexchange.techtarget.com/regulatory-compliance/are-you-glba-compliant-and-ready-for-year-end/#comments</comments>
		<pubDate>Wed, 25 Aug 2010 16:07:02 +0000</pubDate>
		<dc:creator>David Schneier</dc:creator>
				<category><![CDATA[Audit]]></category>
		<category><![CDATA[business continuity]]></category>
		<category><![CDATA[business continuity planning]]></category>
		<category><![CDATA[compliance]]></category>
		<category><![CDATA[FDIC]]></category>
		<category><![CDATA[GLBA]]></category>
		<category><![CDATA[NCUA]]></category>
		<category><![CDATA[penetration test]]></category>
		<category><![CDATA[penetration testing]]></category>
		<category><![CDATA[regulatory]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[risk]]></category>
		<category><![CDATA[risk assessment]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[security awareness]]></category>
		<category><![CDATA[social engineering]]></category>
		<category><![CDATA[Vendor Management]]></category>
		<category><![CDATA[vulnerability test]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/regulatory-compliance/?p=447</guid>
		<description><![CDATA[You'd be surprised by how many financial institutions routinely reach this point in the calendar year having deferred scheduling much (if not all) of their compliance work.  You can't go an entire year without having conducted both an audit and a risk assessment, you can't.]]></description>
				<content:encoded><![CDATA[<p>Summer at home officially ended this morning as my children returned to school.  Beyond the fact that I consider it cruel and inhuman punishment to resume academic activities before Labor Day, it also serves as a wake-up call that we&#8217;re well past mid-year on the traditional calendar and eying the home stretch for 2010; before we know it we&#8217;ll be moving into Q4.  So why is that on my mind today?  Because I&#8217;m mindful of all those institutions that have yet to address their obligations specific to GLBA and NCUA regulations.</p>
<p>This is something of an annual post that I&#8217;ve been issuing over the years where I bang the proverbial spoon on the proverbial pot trying to warn everyone that there&#8217;s work to be done.  I&#8217;m not talking about running through the paces to prepare for an exam but rather having work done that ensures the protection of your customer/member information.  I used to work for a company whose primary sales approach was to  tell current and prospective clients that they had to conduct all manner of tests and assessments because of the regulations.  The firm&#8217;s angle was that in order to be compliant you &#8220;must do this work,&#8221; which not coincidentally dovetailed with services we offered.</p>
<p>I always thought that the &#8220;because I said so&#8221; logic was flawed.  My thinking then and now was that we should educate clients  on why they need to have regular audits and assessments: How scheduling the work at proper intervals and coordinated activities so that they flow naturally into one another greatly reduces their risk of exposure and improves their reputation as a bank or credit union that can be trusted.   But  what if an institution&#8217;s basic strategy is to wait until an exam is a week away and then pull long hours and work all weekend to update what&#8217;s needing updating?</p>
<p>The regulatory compliance trinity is fairly simple and straightforward at its highest level:  You document your controls and related activities (the infamous policies and procedures collection), periodically assess your risk factors to determine if you need to add or modify those controls and related activities, and then  test the controls to determine if they&#8217;re in place and effective.  GLBA at its core is actually that simple and really quite effective.  It&#8217;s GRC 101 and there&#8217;s no doubt that by complying with its basic tenets you&#8217;re doing the right thing to protect your account holders.</p>
<p>And yet you&#8217;d be surprised by how many financial institutions routinely reach this point in the calendar year having deferred scheduling much (if not all) of their compliance work.  You can&#8217;t go an entire year without having conducted both an audit and a risk assessment.  No business infrastructure goes through a 12-month period without something significant changing, without risk factors emerging that haven&#8217;t been present before that need to be managed.  By extending your compliance work to align with your exam cycle, you&#8217;re opening up a huge gap through which a truckload of problems is likely going to drive.  Based on the size and complexity of your institution, you can arrange your compliance program so that not everything needs to occur annually.  I&#8217;ve worked with clients where their program called for a risk assessment and audit to occur in alternate years and where only the ongoing programs (e.g. vendor management, penetration testing, business continuity planning, etc.) needed to be addressed and validated annually.  And while it&#8217;s true that you don&#8217;t need to shoehorn everything into a 12-month period, you do need to have a clearly defined plan on how your institution complies with the various regulations.  You simply can&#8217;t get two-thirds of the way through the year without having conducted or scheduled any manner of testing or assessments.</p>
<p>We&#8217;re about to turn another page on the calendar and enter September.  While you may count that as four months to year-end and think there&#8217;s plenty of time to get things done you need to consider that it&#8217;s more like three months.  Between the major holidays, the minor holidays and people taking time off as the year winds down you&#8217;re going to find it hard to secure resources to conduct the work and even harder to have them complete tasks while people are constantly out of the office.  So with three effective months of working time left in the year, you need to move quickly to come up with a plan.  What are you committed to accomplishing by year end and how are you going to succeed?  Remember, there&#8217;s no more obvious red flag to an examiner than finding a pile of documentation where the ink is still wet or the update/completion dates are suspiciously recent.</p>
<p>And don&#8217;t come back at me with the logic that it doesn&#8217;t clearly state anywhere in GLBA/NCUA regulations that you need to conduct an audit, a risk assessment or any manner of security-based testing.  As I&#8217;ve stated here in my blog several times, FFIEC <a title="FFIEC Examination Handbooks" href="http://www.ffiec.gov/ffiecinfobase/html_pages/it_01.html" target="_blank">guidance </a>clearly indicates a need to have a recently conducted risk assessment available.  FFIEC <a title="FFIEC Examination Handbooks" href="http://www.ffiec.gov/ffiecinfobase/html_pages/it_01.html" target="_blank">guidance </a>also clearly specifies the need to conduct an audit at a frequency appropriate for the size and complexity of an institution.  All you need to do is look at the <a title="FFIEC Master Table of Contents" href="http://www.ffiec.gov/ffiecinfobase/html_pages/toc_book_frame.htm" target="_blank">Master Table of Contents</a> in the FFIEC examination handbooks to see which parts of your infrastructure need to be tested periodically (why do you think the agency authored the handbooks?).  Considering that both the FDIC and NCUA rely on FFIEC guidance to support their examination process, there&#8217;s little doubt (actually no doubt) that&#8217;s where you need to look to figure out what work to schedule.</p>
<p>Three months to go, what&#8217;s your plan?</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/regulatory-compliance/are-you-glba-compliant-and-ready-for-year-end/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
