Incorporating Disaster Recovery into the Organization Ecosystem

In today’s world; people, governments, private and public sector organizations are not immune to various types of disasters. The rare but most catastrophic take form as environmental, less frequent are deliberate attacks, while the majority of “disasters” cause disruption of services or are the direct result of equipment failure. My semester in residence project will take a closer look at DR and contrast the differences between business continuity. Turning a page, to examine the balance between operations and security best practices, I will touch on the effects of the disaster on business continuity “BC”. This project takes a direction to stress the importance of preparedness and paying careful consideration to the tangible approaches available to identify security vulnerabilities and how to measure them in terms of risk using industry frameworks. The project tantalizes one’s appetite the defining requirements phase that make up the system design. I also give my audience a brief overview of key milestones to develop the implementation and I part with a discussion of the composition of recovery plan. The compilation of these aspects will make up primary context of the disaster recovery implementation discussed herein and serve as underlayment to cohere audiences understanding of BC/DR preparedness concepts to recover from technological disasters of an unplanned nature. We begin our journey, by conveying the following theme throughout the project “An unplanned interruption in business can have an adverse impact on finances, operations or other sources” (Moore, 2016). The goal of Disaster recovery “DR” is to serve as an area of security planning that centers around helping an organization continue operating as close to normal as possible. The DR process includes planning and testing, and may involve a separate physical or virtual site for restoring operations (TechTarget, 2015).