It 240 Week 8

The first thing to do when implementing a recovery plan for a potential disaster is easy. It is also crucial to do this before any equipment is purchased, and any data is moved. This, of course, is going to be assessing the situation and documenting the current resources available. Resources such as money, staffing, and current hardware, as well as other important factors such as local weather, likelihood of another disaster, and as a worst-case scenario, an alternate site should all be taken into consideration, and ranked in terms of threat level (high, moderate, and low) before making any unnecessary purchases. Once resources are assessed, you can then move on to addressing threats that can and will present themselves in the given scenario.

In this particular case, XYZ Computers, recently suffered a flood due to heavy rains that severely damaged their servers. Being on the first floor put XYZ Computers at a disadvantage as to where their physical back-ups can be placed, which can explain why the water had such an easy time getting to the machines. Information that is stored on the current backup medium, the tapes, have the potential to become permanently damaged due to such external forces like water.

Another key flaw in XYZ's initial setup, is that there is no firewall present to stop an intruder from poking around in the files, deleting things, changing payroll, and causing limitless amounts of havoc. This can be just as disastrous as a flooded tape, and can take even longer to fix depending on what was done. Simply put, a firewall must be immediately implemented and the necessary access parameters set.

So with our scenario understood, is it time to figure the likelihood of it happening again, and what to do about it. Assuming that it will is also the best thing to do. Expect the unexpected and you won't be sorry. As for what to do, This is also the point in time where we will stand to think about costs What will it cost for new...