<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Security Manager&#8217;s Journal: Budget ax falls on disaster recovery</title>
	<atom:link href="http://www.rothstein.com/blog/security-managers-journal-budget-ax-falls-on-disaster-recovery/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rothstein.com/blog/security-managers-journal-budget-ax-falls-on-disaster-recovery/</link>
	<description>A Business Continuity Weblog</description>
	<lastBuildDate>Wed, 18 Aug 2010 09:58:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: travisk</title>
		<link>http://www.rothstein.com/blog/security-managers-journal-budget-ax-falls-on-disaster-recovery/comment-page-1/#comment-67</link>
		<dc:creator>travisk</dc:creator>
		<pubDate>Thu, 22 Jan 2009 14:51:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.rothstein.com/blog/?p=1876#comment-67</guid>
		<description>JF -Thanks for sharing your story. I liked the fact that your are including  disaster recovery considerations  as part of the project management process. I believe that&#039;s the perfect spot, however  I would add to that  by performing a mini-BIA and risk assessment process with the  the Business process owners (BPOs) as part of the initial requirements definition part of project management process.  Get the facts and let the BPOs define their business recovery  requirements and justify their business continuity  in their business terms.  Let the BPO  make the decision as to how to classify their system (tier recovery). Remember there is a cost to do DR (preparedness) and the is a cost for not (Impact and consequences).  As long as the Executive Management gets the right information, then its up to them to make the right business decision.  IT is just the means to an end.  I would recommend an ongoing annual refresh of  a company-wide   BIA and Risk assessment .   Once you have the base information for each business unit - they would be responsible for reviewing for updates and changes, your just administering the process.  To me, its always about making the business case. Once management knows the risks its a business decision to either accept the risk or remediate the risk.  My experience is that if you can make the business case, then you will get the money. Ken Travis</description>
		<content:encoded><![CDATA[<p>JF -Thanks for sharing your story. I liked the fact that your are including  disaster recovery considerations  as part of the project management process. I believe that&#8217;s the perfect spot, however  I would add to that  by performing a mini-BIA and risk assessment process with the  the Business process owners (BPOs) as part of the initial requirements definition part of project management process.  Get the facts and let the BPOs define their business recovery  requirements and justify their business continuity  in their business terms.  Let the BPO  make the decision as to how to classify their system (tier recovery). Remember there is a cost to do DR (preparedness) and the is a cost for not (Impact and consequences).  As long as the Executive Management gets the right information, then its up to them to make the right business decision.  IT is just the means to an end.  I would recommend an ongoing annual refresh of  a company-wide   BIA and Risk assessment .   Once you have the base information for each business unit &#8211; they would be responsible for reviewing for updates and changes, your just administering the process.  To me, its always about making the business case. Once management knows the risks its a business decision to either accept the risk or remediate the risk.  My experience is that if you can make the business case, then you will get the money. Ken Travis</p>
]]></content:encoded>
	</item>
</channel>
</rss>
