<?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>Disaster Recovery</title>
 <link>http://www.securityprocedure.com/tag/disaster-recovery</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>Business Continuity Management Guidelines from The Institute of Internal Auditors</title>
 <link>http://www.securityprocedure.com/business-continuity-management-guidelines-institute-internal-auditors</link>
 <description>&lt;p&gt;The Institute of Internal Auditors recently releases Business Continuity Management Guidelines. This GTAG focuses on how business continuity management (BCM) is designed to enable business leaders to manage the level of risk the organization could encounter in the case of a natural or man-made disruptive event that affects the extended operability of the organization.&lt;/p&gt;
&lt;p&gt;The guide includes:&lt;br /&gt;
- Disaster recovery planning for continuity of critical information technology infrastructure, and&lt;br /&gt;
- Business application systems.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.theiia.org/guidance/technology/gtag/gtag10/&quot;&gt;Download Page&lt;/a&gt;&lt;/p&gt;
</description>
 <comments>http://www.securityprocedure.com/business-continuity-management-guidelines-institute-internal-auditors#comments</comments>
 <category domain="http://www.securityprocedure.com/tag/disaster-recovery">Disaster Recovery</category>
 <category domain="http://www.securityprocedure.com/tag/download">Download</category>
 <pubDate>Thu, 31 Jul 2008 17:40:59 -0500</pubDate>
 <dc:creator>root</dc:creator>
 <guid isPermaLink="false">251 at http://www.securityprocedure.com</guid>
</item>
<item>
 <title>Disaster Recovery Planning, Seven simple step</title>
 <link>http://www.securityprocedure.com/disaster-recovery-planning-seven-simple-step</link>
 <description>&lt;p&gt;&lt;b&gt;Step 1 – Admit the possibility of disaster&lt;/b&gt;&lt;br /&gt;
Just as the first step to personal recovery is admitting one has a problem, so the first step in BCDR planning is to admit the organization faces tangible threats that could jeopardize its prosperity – or its survival. Until this first step is taken at a senior leadership level, go no further.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Step 2 – List and categorize likely threats to the organization&lt;/b&gt;&lt;br /&gt;
The nature of the business and its physical and social environment will influence the types of threats an organization might face. Once the threats are listed, they should be categorized according to their likely impact on various systems. The cost of the response should be balanced against the tolerance for system downtime -- the less downtime that can be tolerated, the more it will cost to create an appropriate response. Some systems must be functioning again within minutes or seconds, while others can be down a few hours, and still others can be down for a few days without serious consequences.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Step 3 – Outline the organization’s BCDR technology infrastructure&lt;/b&gt;&lt;br /&gt;
The key technology elements&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.securityprocedure.com/disaster-recovery-planning-seven-simple-step&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.securityprocedure.com/disaster-recovery-planning-seven-simple-step#comments</comments>
 <category domain="http://www.securityprocedure.com/tag/computer-security">Computer Security</category>
 <category domain="http://www.securityprocedure.com/tag/configuration-management">Configuration Management</category>
 <category domain="http://www.securityprocedure.com/tag/disaster-recovery">Disaster Recovery</category>
 <pubDate>Sun, 06 Jul 2008 04:16:48 -0500</pubDate>
 <dc:creator>root</dc:creator>
 <guid isPermaLink="false">196 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>Levels of assurance in Disaster Recovery Plan</title>
 <link>http://www.securityprocedure.com/levels-assurance-disaster-recovery-plan</link>
 <description>&lt;p&gt;There is a propensity for the leader of every business unit to have an inflated sense of the criticality of the systems, services and contribution of their area. In order to sort out the priorities it is necessary to determine a level of assurance that is appropriate. An organized, defined set of assurance levels can be developed in terms of the following five standards, with a rough correspondence to maximum tolerable outages:&lt;/p&gt;
&lt;p&gt;1. Platinum (five stars) – maximum tolerable outage less than hours;&lt;br /&gt;
2. Gold (four stars) – maximum tolerable outage up to one day;&lt;br /&gt;
3. Silver (three stars) – maximum tolerable outage up to one week;&lt;br /&gt;
4. Bronze (two stars) – maximum tolerable outage up to one month;&lt;br /&gt;
5. No standard – no defined tolerable outage.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.securityprocedure.com/levels-assurance-disaster-recovery-plan&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.securityprocedure.com/levels-assurance-disaster-recovery-plan#comments</comments>
 <category domain="http://www.securityprocedure.com/tag/disaster-recovery">Disaster Recovery</category>
 <pubDate>Sat, 24 May 2008 08:30:49 -0500</pubDate>
 <dc:creator>root</dc:creator>
 <guid isPermaLink="false">147 at http://www.securityprocedure.com</guid>
</item>
<item>
 <title>14 step for family Disaster Recovery Plan</title>
 <link>http://www.securityprocedure.com/14-step-family-disaster-recovery-plan</link>
 <description>&lt;ol&gt;
&lt;li&gt;Meet with everyone in your household and discuss the types of disasters that are most likely to occur in your area. Work together to decide what to do in each case. Write your plan down on paper, and keep it in your family files.&lt;/li&gt;
&lt;li&gt;Since disasters often strike entire communities rather than just a single home, share your plan with neighbors and encourage them to develop their own plan. Share your plan with family members or friends living outside your town.&lt;/li&gt;
&lt;li&gt;Select two places to meet if an emergency strikes. In case of sudden emergencies, such as a fire, pick a spot in the neighborhood outside your home. In a widespread emergency when you can&#039;t get back home, pick a spot outside your neighborhood. Make sure everyone knows the address and phone number.&lt;/li&gt;
&lt;p&gt;&lt;a href=&quot;http://www.securityprocedure.com/14-step-family-disaster-recovery-plan&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.securityprocedure.com/14-step-family-disaster-recovery-plan#comments</comments>
 <category domain="http://www.securityprocedure.com/tag/disaster-recovery">Disaster Recovery</category>
 <pubDate>Wed, 26 Mar 2008 08:33:51 -0500</pubDate>
 <dc:creator>root</dc:creator>
 <guid isPermaLink="false">94 at http://www.securityprocedure.com</guid>
</item>
<item>
 <title>Nine type of IT Disaster</title>
 <link>http://www.securityprocedure.com/nine-type-it-disaster</link>
 <description>&lt;p&gt;There are nine type of IT Disaster that could be happen every day in IT environment, from user error to hardware failure. This article discussed how IT Disaster happened and how we could prepare against this matter. The original list taken from Unix Backup and Recovery by W. Curtis Preston&lt;/p&gt;
&lt;h3&gt;1. User error&lt;/h3&gt;
&lt;p&gt;This has been, by far, the biggest percentage of restores in every environment that I have seen. &quot;Hey, I was sklocking my flambality file, and I accidentally pressed the jankle button. Can you restore it, please?&quot; This one is pretty easy, right? What about the common question: &quot;Can you restore it as of about an hour ago?&quot; &lt;/p&gt;
&lt;h3&gt;2. System-staff error&lt;/h3&gt;
&lt;p&gt;This is less common than user error (unless your users have root), but when it happens, oh boy, does it happen! What happens when you newfs your Informix raw device or delete a user&#039;s home directory? These restores need to go really fast, since they&#039;re your fault. As far as protecting yourself from this type of error, the same is true here as for user errors-either typical nightly backups or snapshots can protect you from this.&lt;/p&gt;
&lt;h3&gt;3. Hardware failure&lt;/h3&gt;
&lt;p&gt;Most books talk about protecting yourself from hardware failure, but they usually don&#039;t mention that hardware failure can come in two forms: disk drive failure and system-wide failure. It is important to mention this, because it takes two entirely different methods to protect yourself from these failures. Many people do not take this into consideration when planning their data protection plan.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.securityprocedure.com/nine-type-it-disaster&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.securityprocedure.com/nine-type-it-disaster#comments</comments>
 <category domain="http://www.securityprocedure.com/tag/disaster-recovery">Disaster Recovery</category>
 <pubDate>Fri, 21 Mar 2008 19:56:17 -0500</pubDate>
 <dc:creator>root</dc:creator>
 <guid isPermaLink="false">92 at http://www.securityprocedure.com</guid>
</item>
<item>
 <title>ISO 24762 IT Disaster Recovery, New ISO released</title>
 <link>http://www.securityprocedure.com/iso-24762-it-disaster-recovery-new-iso-released</link>
 <description>&lt;p&gt;New ISO/IEC 24762:2008 provides guidance on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Implementing, operating, monitoring and maintaining the necessary facilities and services necessary for disaster recovery.&lt;/li&gt;
&lt;li&gt;Fallback and recovery support for the organization&amp;rsquo;s ICT systems.&lt;/li&gt;
&lt;li&gt;The capabilities which outsourced ICT disaster recovery service providers should possess and the practices they should follow, so as to provide basic secure operating environments and facilitate the organizations&#039; recovery efforts.&lt;/li&gt;
&lt;li&gt;The selection of a recovery site (e.g. considering factors such as environmental stability, good infrastructure, etc.), and&lt;/li&gt;
&lt;li&gt;Requirements for ICT DR service providers to continuously improve their ICT DR services.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a href=&quot;http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=41532&quot;&gt;view standard here&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
</description>
 <comments>http://www.securityprocedure.com/iso-24762-it-disaster-recovery-new-iso-released#comments</comments>
 <category domain="http://www.securityprocedure.com/tag/disaster-recovery">Disaster Recovery</category>
 <category domain="http://www.securityprocedure.com/tag/iso-standard">ISO Standard</category>
 <category domain="http://www.securityprocedure.com/tag/news">News</category>
 <category domain="http://www.securityprocedure.com/tag/standard">Standard</category>
 <pubDate>Sun, 09 Mar 2008 20:56:42 -0500</pubDate>
 <dc:creator>root</dc:creator>
 <guid isPermaLink="false">66 at http://www.securityprocedure.com</guid>
</item>
<item>
 <title>Six step to develop Disaster Recovery Plan</title>
 <link>http://www.securityprocedure.com/six-step-develop-disaster-recovery-plan</link>
 <description>&lt;p&gt;How to develop Disaster Recovery Plan for your company? This simple guidance from W. Curtis Preston in his book Unix Backup and Recovery tell us six step to develop Disaster Recovery Plan. Here is the list.&lt;/p&gt;
&lt;h3&gt;1. Define (un)acceptable loss / Risk Assessment&lt;/h3&gt;
&lt;p&gt;“…Before you develop a disaster recovery plan, decide how much you will lose if you don&#039;t. That will help you decide how much time, effort, and money to spend on a disaster/recovery plan…”&lt;/p&gt;
&lt;p&gt;Curtis give pressure on define unacceptable loss, or in the other ways perform a Risk Assessment for entire scenario. As we know that risk could be transferred (insurance), mitigated (by control it) or even accept the risk.&lt;/p&gt;
&lt;h3&gt;2. Back up everything.&lt;/h3&gt;
&lt;p&gt;“…You have to make sure that everything is backed up-including data, metadata, and the instructions you&#039;ll need to get them back…”&lt;/p&gt;
&lt;p&gt;Curtis said to backup everything, (as long as you can have it), the basic principle is we could protect any kind of asset that we have.&lt;/p&gt;
&lt;h3&gt;3. Organize everything.&lt;/h3&gt;
&lt;p&gt;You have everything on backup volumes. But can you find the volume you need when disaster strikes? The key to being able to find your backups is organization.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.securityprocedure.com/six-step-develop-disaster-recovery-plan&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.securityprocedure.com/six-step-develop-disaster-recovery-plan#comments</comments>
 <category domain="http://www.securityprocedure.com/tag/backup-restore">Backup Restore</category>
 <category domain="http://www.securityprocedure.com/tag/disaster-recovery">Disaster Recovery</category>
 <pubDate>Sun, 09 Mar 2008 01:04:37 -0600</pubDate>
 <dc:creator>root</dc:creator>
 <guid isPermaLink="false">64 at http://www.securityprocedure.com</guid>
</item>
<item>
 <title>Top 10 deadliest Earthquake in the world</title>
 <link>http://www.securityprocedure.com/top-10-deadliest-earthquake-world</link>
 <description>&lt;p&gt;During business impact analysis, IS auditor should make an regular analysis with each environmental exposures such as earthquake. And here is the list&lt;br&gt;  Top 10 deadliest earthquake in the world&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.securityprocedure.com/top-10-deadliest-earthquake-world&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.securityprocedure.com/top-10-deadliest-earthquake-world#comments</comments>
 <category domain="http://www.securityprocedure.com/tag/disaster-recovery">Disaster Recovery</category>
 <category domain="http://www.securityprocedure.com/tag/environmental-exposures">Environmental Exposures</category>
 <pubDate>Fri, 07 Mar 2008 09:20:25 -0600</pubDate>
 <dc:creator>root</dc:creator>
 <guid isPermaLink="false">57 at http://www.securityprocedure.com</guid>
</item>
</channel>
</rss>
