In this article, the writer notes that in today's society, organizations need to have a plan in place in event of an attack or failure to recover data that is lost, stolen, or destroyed. In this essay, the writer presents a step-by-step plan of how to recover such data and discusses the strengths and weaknesses of any methodologies or technologies designed to protect the data in information systems. The writer concludes that although no plan provides 100% protection, a company has to be ready to protect what it has and react to information system threats as they take place.
From the Paper:
" Backup is reacting to what to do to repair the situation after it happened. Processing will continue either at the main data center or at the selected hot site, depending on the outcomes of the assessment of damage to equipment. However, if the damaged area entails a longer time of reconstruction, then the second stage of back up begins. If the database is misplaced, examining the last system checkpoint does not recover it. The system log can tell what modifications have taken placed, but without the original database itself, recovery can be impossible. The organization should backup message queues, online changes, and make new backup copies at regular intervals. The more current the backup copies, the smaller amount of log change records to be processed during recovery, and as a result the time needed for recovery is decreased."
Sample of Sources Used:
Action Plan for Information Systems Protection against Cyber-threats. (2000). Retrieved December 10, 2007, from http://www.nisc.go.jp/en/sisaku/h1201action.html
Disaster Recovery Planning. (2004). Retrieved December 10, 2007, from http://www.blueclaw-db.com/disaster_recovery_plan.htm
Internet Security Systems. (2001). Retrieved December 10, 2007, from http://cc.msnscache.com/cache.aspx?q=72399317175731&mkt=en-US&lang=en-US&w=ebca5eb6&FORM=CVRE
MIT Business Continuity Plan. (1995). Retrieved December 10, 2007, from http://web.mit.edu/security/www/pubplan.htm
Operation Guide. (2006). Retrieved December 10, 2007, from http://publib.boulder.ibm.com/infocenter/dzichelplv2r2/topic/com.ibm.ims9.doc.pdf/dfsog1g3.pdf?noframes=true