Read the Business Continuity in Real Life case found in Chapter 3 of the textbook. Address the following business continuity plan components below for a business with which you are familiar. Each response should be 1–2 paragraphs in length submitted in MS Word. The submission is not to exceed three pages.
Risk Assessment: Address what events might affect the company, how much of an outage each could cause, the most likely events, which events can be ignored, and the business and technical factors used to evaluate the risk.
Business Impact Analysis: Explain the cost of each potential outage described in the risk assessment, how long the business could sustain the outage, including partial and full outages, as well as considerations for the loss of applications, staff and data.
Continuity Requirement: Describe which systems have to come online, how quickly, including justification for the best choice between a continuity provided by an offsite backup data or a cold system.
Business Continuity Plan: Address physical security of offsite storage facilities, staff authorized and expected to participate in post disaster operations, which staff shall participate in securing and obtaining damaged equipment from a disaster, and staff command-control ï»¿communication procedures during restoration efforts.
Criticality and Redundancy: Prioritize functions which require redundancy based on business criticality considering the cost effectiveness for the organization using multiple redundant active sites, and the distribution of more resilient network segments.
This course requires the use of Strayer Writing Standards. For assistance and information, please refer to the Strayer Writing Standards link in the left-hand menu of your course.
” Read the Business Continuity in Real Life case found in Chapter 3 of the textbook”
Business Continuity in Real Life
Stories abound of business failure because of technology failures. In one situation, a company had two data centers within a couple of miles of each other. A hurricane hit the city, and both data centers were taken offline. One was severely damaged by the storm. The other was located on a high floor in the building, so it escaped with little damage, but the fuel tanks for the generators were in the basement, and those fuel tanks floated away. The company was able to get that data center functioning again when fuel was available a few days later, but had to operate for months on just one data center until power and WAN links were fully restored. In another instance, two senior engineers sat idle while outsourced contractors attempted to bring up an IPsec tunnel to restore operations worth millions of dollars a minute. Why weren’t the senior engineers engaged? Because the terms of the outsourcing contract forbade anyone but an employee of the outsourcer to touch device configurations. And let’s not even think about the impact of a network outage in a medical facility, or at a construction site where a failure could cost lives rather than money.
With all the apocryphal stories that abound, why don’t managers and network engineers pay more attention to failure modes and business continuity? Why aren’t geodiversity and diversity of power, telecom, and road grids top-of-mind subjects? There seem to be a number of reasons.
Many engineers just don’t think it could happen “here.” There is little sense of the urgency or importance of this system from a business perspective, so there is little planning around failures. Or perhaps IT staff are too busy with the day-to-day tasks to have time to worry about how a failure will impact the network, and hence the business. Much of the time it’s a lack of understanding and appreciation of the complexity and interdependence of the IT systems we build and maintain. Our ability to abstract, although required to help us focus on solving one specific problem at one specific point in time, is also our enemy when it comes to failures and failure modes. We need to seek out the interconnections between systems and try to understand them so we can really understand all the different areas that would be impacted by an outage.