<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.securityprocedure.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Business Impact Analysis</title>
 <link>http://www.securityprocedure.com/tag/business-impact-analysis</link>
 <description>The taxonomy view with a depth of 0.</description>
 <language>en</language>
<item>
 <title>Comparison between ISACA and DRII Business Continuity Plan</title>
 <link>http://www.securityprocedure.com/comparison-between-isaca-and-drii-business-continuity-plan</link>
 <description>&lt;p&gt;DRII vs ISACA Business Continuity Plan Comparison&lt;br /&gt;
&lt;IMG SRC=&quot;http://img187.imageshack.us/img187/5076/bcpzn7.png&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.isaca.org/&quot;&gt;ISACA (Information System Audit and Control Association)&lt;/a&gt; and &lt;a href=&quot;http://www.drii.org/&quot;&gt;DRII (Disaster Recovery Institute International)&lt;/a&gt; are the two organizations that have a competency to release the right procedure and step by step for Business Continuity Management. However, if you see each step from ISACA and DRII, you can find some small differences approach on it. Here is some example:&lt;/p&gt;
&lt;p&gt;ISACA Business Continuity&lt;br /&gt;
1. Project management and initiation&lt;br /&gt;
2. Business impact analysis&lt;br /&gt;
3. Recovery strategy&lt;br /&gt;
4. Plan design and development&lt;br /&gt;
5. Training and awareness&lt;br /&gt;
6. Implementation and testing&lt;br /&gt;
7. Monitoring and maintenance&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.securityprocedure.com/comparison-between-isaca-and-drii-business-continuity-plan&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.securityprocedure.com/comparison-between-isaca-and-drii-business-continuity-plan#comments</comments>
 <category domain="http://www.securityprocedure.com/tag/business-impact-analysis">Business Impact Analysis</category>
 <category domain="http://www.securityprocedure.com/tag/contingency">Contingency</category>
 <category domain="http://www.securityprocedure.com/tag/disaster-recovery">Disaster Recovery</category>
 <pubDate>Fri, 15 Aug 2008 21:51:04 -0500</pubDate>
 <dc:creator>root</dc:creator>
 <guid isPermaLink="false">260 at http://www.securityprocedure.com</guid>
</item>
<item>
 <title>Is America ready for business continuity</title>
 <link>http://www.securityprocedure.com/america-ready-business-continuity</link>
 <description>&lt;p&gt;&lt;img src=&quot;http://img401.imageshack.us/img401/1443/disasterrecoveryplanbb6.png&quot; alt=&quot;&quot; /&gt;&lt;/p&gt;
&lt;p&gt;According to latest research from &lt;a href=&quot;http://www.att.com/gen/press-room?pid=7922&quot;&gt;AT&amp;amp;T&lt;/a&gt; the answer are: &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Nearly 30 percent of U.S. businesses don&#039;t consider business continuity planning a priority.&lt;/li&gt;
&lt;li&gt;Two-thirds of IT executives predict that hacking will be the biggest threat in the next five years.&lt;/li&gt;
&lt;li&gt;The next most frequently mentioned threats are internal:&lt;br /&gt;Accidents &amp;mdash; 56 percent&lt;br /&gt;Sabotage &amp;mdash; 47 percent&lt;br /&gt;Remote workers &amp;mdash; 44 percent&lt;/li&gt;
&lt;p&gt;&lt;a href=&quot;http://www.securityprocedure.com/america-ready-business-continuity&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.securityprocedure.com/america-ready-business-continuity#comments</comments>
 <category domain="http://www.securityprocedure.com/tag/bs7799">BS7799</category>
 <category domain="http://www.securityprocedure.com/tag/business-impact-analysis">Business Impact Analysis</category>
 <category domain="http://www.securityprocedure.com/tag/disaster-recovery">Disaster Recovery</category>
 <pubDate>Thu, 19 Jun 2008 02:26:32 -0500</pubDate>
 <dc:creator>root</dc:creator>
 <guid isPermaLink="false">169 at http://www.securityprocedure.com</guid>
</item>
<item>
 <title>Review of Business Continuity Management Framework</title>
 <link>http://www.securityprocedure.com/review-business-continuity-management-framework</link>
 <description>&lt;p&gt;Recent natural disaster, such as earth quake or tsunami is true evidence that all business operation need appropriate business continuity management.  Today, there are a lot of world standard that could be followed to get the best implementation of business continuity management. From the US standard: NIST SP 800-34 to British Standard 25999. Here is simple comparison between to standard.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.securityprocedure.com/review-business-continuity-management-framework&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.securityprocedure.com/review-business-continuity-management-framework#comments</comments>
 <category domain="http://www.securityprocedure.com/tag/bs25999">BS25999</category>
 <category domain="http://www.securityprocedure.com/tag/business-impact-analysis">Business Impact Analysis</category>
 <category domain="http://www.securityprocedure.com/tag/contingency">Contingency</category>
 <category domain="http://www.securityprocedure.com/tag/nist-sp">NIST-SP</category>
 <pubDate>Wed, 05 Mar 2008 23:47:27 -0600</pubDate>
 <dc:creator>root</dc:creator>
 <guid isPermaLink="false">54 at http://www.securityprocedure.com</guid>
</item>
</channel>
</rss>
