4115 0 obj <> endobj What are you going to do about it?

2.3.2 DR Procedures for Management Members of the management team will keep a hard copy of the names and contact numbers of each employee in their departments. ___________ Preparing the Business Recovery Report Form On completion of business recovery activities the BRT leader should prepare a report on the activities undertaken and completed.

Business Recovery Team Leader Name: ________________________________________ Signature: ________________________________________________________________ Date: __________________________ (Any relevant comments by the BRT leader in connection with the return of this business process should be made here.) [Content_Types].xml ( k0^1F>tZX{sV.mO3:Nx`NX7h=3VH,2#J@. 2.3.1 Emergency Alert The person discovering the incident calls a member of the Emergency Response Team in the order listed: Emergency Response Team _________ _________ _________ If not available try: _________ _________ The Emergency Response Team (ERT) is responsible for activating the DRP for disasters identified in this plan, as well as in the event of any other occurrence that affects the companys capability to perform normally. 1.2 Plan Documentation Storage Copies of this Plan, CD, and hard copies will be stored in secure locations to be defined by the company. Successful DR plans launch into action smoothly and effectively when they are needed. All employees must be issued a Quick Reference card containing ERT contact details to be used in the event of a disaster. Note: A priority sequence must be identified although, where possible, activities will be carried out simultaneously. : Technical Specifications: Network Interfaces: Power Requirements; System Serial #: DNS Entry: IP Address: Other:HOT SITE EQUIPMENTProvide detailsSPECIAL APPLICATIONSASSOCIATED DEVICES KEY CONTACTSHardware VendorProvide detailsSystem OwnersProvide detailsDatabase OwnerProvide detailsApplication OwnersProvide detailsSoftware VendorsProvide detailsOffsite StorageProvide detailsNetwork ServicesProvide details BACKUP STRATEGY for SYSTEM TWODailyProvide detailsMonthlyProvide detailsQuarterlyProvide details SYSTEM TWO DISASTER RECOVERY PROCEDURE Scenario 1 Total Loss of Network Provide details Scenario 2 Total Loss of HW Provide details ADDENDUM CONTACTS Support Systems Support system Critical network assets Critical interfacesCritical files to restoreCritical network services to restoreOther services Disaster Recovery Plan for Voice Communications SYSTEM OVERVIEW EQUIPMENTLocation: Device Type: Model No. 2.2 Disaster Recovery Team The team will be contacted and assembled by the ERT. Policy Statement Corporate management has approved the following policy statement: The company shall develop a comprehensive IT disaster recovery plan. The disaster recovery plan is to be kept up to date to take into account changing circumstances. The strategy chosen is for a fully mirrored recovery site at the companys offices in _____. Report to the emergency response team. WAN redundancy, voice network resilience Probability: 1=Very High, 5=Very Low Impact: 1=Total destruction, 5=Minor annoyance 2 Emergency Response 2.1 Alert, escalation and plan invocation 2.1.1 Plan Triggering Events Key trigger issues at headquarters that would lead to activation of the DRP are: Total loss of all communications Total loss of power Flooding of the premises Loss of the building 2.1.2 Assembly Points Where the premises need to be evacuated, the DRP invocation plan identifies two evacuation assembly points: Primary Far end of main parking lot; Alternate Parking lot of company across the street 2.1.3 Activation of Emergency Response Team When an incident occurs the Emergency Response Team (ERT) must be activated. PK ! 1.3 Backup Strategy Key business processes and the agreed backup strategy for each are listed below. A separate form should be used for each recovered business process. Hot site staffing will consist of members of the disaster recovery team only for the first 24 hours, with other staff members joining at the hot site as necessary. 4 Insurance As part of the companys disaster recovery and business continuity strategies a number of insurance policies have been put in place. Each member of senior management will be issued a CD and hard copy of this plan to be filed at home. I confirm that above business process is now acceptable for normal working conditions. E F n o p q $a$gd # $a$ $a$ q r s t u v w x y z { | } ~  &. : Technical Specifications: Network Interfaces: Power Requirements; System Serial #: DNS Entry: IP Address: Other:HOT SITE EQUIPMENTProvide detailsSPECIAL APPLICATIONSASSOCIATED DEVICES KEY CONTACTSHardware VendorProvide detailsSystem OwnersProvide detailsDatabase OwnerProvide detailsApplication OwnersProvide detailsSoftware VendorsProvide detailsOffsite StorageProvide detailsNetwork ServicesProvide details BACKUP STRATEGY for SYSTEM TWODailyProvide detailsMonthlyProvide detailsQuarterlyProvide details SYSTEM TWO DISASTER RECOVERY PROCEDURE Scenario 1 Total Loss of Network Provide details Scenario 2 Total Loss of HW Provide details ADDENDUM CONTACTS Support Systems Support system Critical network assets Critical interfacesCritical files to restoreCritical network services to restoreOther services Disaster Recovery Plan for Remote Connectivity SYSTEM OVERVIEW EQUIPMENTLocation: Device Type: Model No. 0 Loss of cash 5.2 Financial Requirements The immediate financial needs of the company must be addressed. }4h 4133 0 obj <>stream UPSs also remotely monitored.Loss of communications network services 44Two diversely routed T1 trunks into building. : Technical Specifications: Network Interfaces: Power Requirements; System Serial #: DNS Entry: IP Address: Other:HOT SITE EQUIPMENTProvide detailsSPECIAL APPLICATIONSASSOCIATED DEVICES KEY CONTACTSHardware VendorProvide detailsSystem OwnersProvide detailsDatabase OwnerProvide detailsApplication OwnersProvide detailsSoftware VendorsProvide detailsOffsite StorageProvide detailsNetwork ServicesProvide details BACKUP STRATEGY for SYSTEM TWODailyProvide detailsMonthlyProvide detailsQuarterlyProvide details SYSTEM TWO DISASTER RECOVERY PROCEDURE Scenario 1 Total Loss of Switch Provide details Scenario 2 Total Loss of Network Provide details ADDENDUM CONTACTS Support Systems Support system Critical network assets Critical interfacesCritical files to restoreCritical network services to restoreOther services Appendix B Suggested Forms Damage Assessment Form Key Business Process AffectedDescription Of ProblemExtent Of Damage _____________ Management of DR Activities Form During the disaster recovery process all activities will be determined using a standard structure; Where practical, this plan will need to be updated on a regular basis throughout the disaster recovery period; All actions that occur during this phase will need to be recorded. 3.3 Media Team ____________________________________________ ____________________________________________ ____________________________________________ 3.4 Rules for Dealing with Media Only the media team is permitted direct contact with the media; anyone else contacted should refer callers or in-person media representatives to the media team. Fire and smoke detectors on all floors. Since difficulties experienced by one group could significantly affect other dependent tasks it is important to ensure that each task is adequately resourced and that the efforts required to restore normal business operations have not been underestimated. ! " Additional objectives include the following: The need to ensure that all employees fully understand their duties in implementing such a plan The need to ensure that operational policies are adhered to within all planned activities The need to ensure that proposed contingency arrangements are cost-effective The need to consider implications on other company sites Disaster recovery capabilities as applicable to key customers, vendors and others Key Personnel Contact Info Name, TitleContact OptionContact NumberWorkAlternateMobileHomeEmail AddressAlternate EmailWorkAlternateMobileHomeEmail AddressAlternate EmailWorkAlternateMobileHomeEmail AddressAlternate EmailWorkAlternateMobileHomeEmail AddressAlternate EmailWorkAlternateMobileHomeEmail AddressAlternate EmailWorkAlternateMobileHomeEmail AddressAlternate Email Notification Calling Tree External Contacts Name, TitleContact OptionContact NumberLandlord / Property Manager Account Number NoneWorkMobileHomeEmail AddressPower Company Account Number WorkMobileHomeEmail AddressTelecom Carrier 1 Account Number WorkMobileFaxHomeEmail AddressTelecom Carrier 2Account Number WorkMobileHomeEmail AddressHardware Supplier 1Account Number WorkMobileEmergency ReportingEmail AddressServer Supplier 1 Account Number.Work MobileFaxEmail Address Workstation Supplier 1 Account Number WorkMobileHomeEmail AddressOffice Supplies 1Account Number C3095783WorkMobileHomeEmail AddressInsurance Name Account Number WorkMobileHomeEmail AddressSite Security Account Number WorkMobileHomeEmail AddressOff-Site Storage 1Account NumberWorkMobileHomeEmail AddressOff-Site Storage 2 Account Number User IDPasswordHomeEmail AddressHVAC Account Number WorkMobileHomeEmail AddressPower Generator Account NumberWorkMobileHomeEmail AddressOther Account NumberWorkMobileHomeEmail Address External Contacts Calling Tree 1 Plan Overview 1.1 Plan Updating It is necessary for the DRP updating process to be properly structured and controlled. The information given to all parties must be accurate and timely. One of the tasks during the early stages of the emergency is to notify the Disaster Recovery Team (DRT) that an emergency has occurred. Procedures have been addressed to ensure that communications can be quickly established while activating disaster recovery. 2.3.8 Personnel and Family Notification If the incident has resulted in a situation which would cause concern to an employees immediate family such as hospitalization of injured persons, it will be necessary to notify their immediate family members quickly. It is also very important that only authorized personnel deal with media queries.

This will involve the use of formalized change control procedures under the control of the IT Director. 2.3.5 Recorded Messages / Updates For the latest information on the disaster and the organizations response, staff members can call a toll-free hotline listed in the DRP wallet card. These can include: Cash flow position Temporary borrowing capability Upcoming payments for taxes, payroll taxes, Social Security, etc. The plan should also be validated by simulating the circumstances within which it has to work and seeing what happens. The focus here is on the level of business disruption which could arise from each type of disaster. This event log should be started at the commencement of the emergency and a copy of the log passed on to the business recovery team once the initial dangers have been controlled. The assessment should include: Loss of financial documents Loss of revenue Theft of check books, credit cards, etc. Description of Disaster:Commencement Date:Date/Time DR Team Mobilized: Activities Undertaken by DR TeamDate and TimeOutcomeFollow-On Action Required Disaster Recovery Team's Work Completed: Event Log Passed to Business Recovery Team: _________________ Disaster Recovery Activity Report Form On completion of the initial disaster recovery response the DRT leader should prepare a report on the activities undertaken. Objectives The principal objective of the disaster recovery program is to develop, test and document a well-structured and easily understood plan which will help the company recover as quickly and effectively as possible from an unforeseen disaster or emergency which interrupts information systems and business operations. The disaster recovery plan should be periodically tested in a simulated environment to ensure that it can be implemented in emergency situations and that the management and staff understand how it is to be executed. The report will also contain an assessment of the impact to normal business operations. Suppliers of critical goods and services will continue to support recovery of business operations as the company returns to normal operating mode. In particular, any estimate of the timing to return to normal working operations should be announced with care. The report should be given to business recovery team leader, with a copy to senior management, as appropriate. ; Decide which elements of the DR Plan should be activated; Establish and manage disaster recovery team to maintain vital services and return to normal operation; Ensure employees are notified and allocate responsibilities and activities as required. A master protected copy will be stored on specific resources established for this purpose. hbbd``b`kA5{DqUW4`lL@bO0 Hmf_:lrk4b jV}-3K]y$RVT0}4VnZru,)8]mvT&'g1C6{) e0vYfxChUtqu@kE%8h=0|0k]]!n )". 2.3.3 Contact with Employees Managers will serve as the focal points for their departments, while designated employees will call other employees to discuss the crisis/disaster and the companys immediate plans. The DR plan will rely principally on key members of management and staff who will provide the technical and management skills necessary to achieve a smooth technology and business recovery. How did it happen? The Business Recovery Team (BRT) will consist of senior representatives from the main business departments. 4125 0 obj <>/Filter/FlateDecode/ID[<35FCC891D2EBAF458897B7D259D8A695><437157FFB5828140AC2468B128288816>]/Index[4115 19]/Info 4114 0 R/Length 64/Prev 225986/Root 4116 0 R/Size 4134/Type/XRef/W[1 2 1]>>stream The report should contain information on the disruptive event, who was notified and when, action taken by members of the BRT together with outcomes arising from those actions. > T V M N O P Q R S bjbj[[ 9 9 ; [ J Z Z Z n n n 8 2" d n Q 0 8 8 8 8 TU B [ b] $ ! Z J^ M U @ J^ J^ 8 8 j_ j_ j_ J^ t 8 Z 8 j_ J^ j_ j_ 0 f 4 8 fLQ ^ R $ ! 0 Q @ *_ @ H 4 Z 4 J^ J^ j_ J^ J^ J^ J^ J^ j_ J^ J^ J^ Q J^ J^ J^ J^ J^ J^ J^ J^ J^ J^ J^ J^ J^ : IT Disaster Recovery Plan Template By Paul Kirvan, CISA, CISSP, FBCI, CBCP Revision History revisiondatenamedescriptionOriginal 1.0 Table of Contents TOC \o "1-4" \h \z HYPERLINK \l "_Toc241554706"Information Technology Statement of Intent PAGEREF _Toc241554706 \h 5 HYPERLINK \l "_Toc241554707"Policy Statement PAGEREF _Toc241554707 \h 5 HYPERLINK \l "_Toc241554708"Objectives PAGEREF _Toc241554708 \h 5 HYPERLINK \l "_Toc241554709"Key Personnel Contact Info PAGEREF _Toc241554709 \h 6 HYPERLINK \l "_Toc241554710"Notification Calling Tree PAGEREF _Toc241554710 \h 7 HYPERLINK \l "_Toc241554711"External Contacts PAGEREF _Toc241554711 \h 8 HYPERLINK \l "_Toc241554712"External Contacts Calling Tree PAGEREF _Toc241554712 \h 10 HYPERLINK \l "_Toc241554713"1 Plan Overview PAGEREF _Toc241554713 \h 11 HYPERLINK \l "_Toc241554714"1.1 Plan Updating PAGEREF _Toc241554714 \h 11 HYPERLINK \l "_Toc241554715"1.2 Plan Documentation Storage PAGEREF _Toc241554715 \h 11 HYPERLINK \l "_Toc241554716"1.3 Backup Strategy PAGEREF _Toc241554716 \h 11 HYPERLINK \l "_Toc241554717"1.4 Risk Management PAGEREF _Toc241554717 \h 11 HYPERLINK \l "_Toc241554718"2 Emergency Response PAGEREF _Toc241554718 \h 12 HYPERLINK \l "_Toc241554719"2.1 Alert, escalation and plan invocation PAGEREF _Toc241554719 \h 12 HYPERLINK \l "_Toc241554720"2.1.1 Plan Triggering Events PAGEREF _Toc241554720 \h 12 HYPERLINK \l "_Toc241554721"2.1.2 Assembly Points PAGEREF _Toc241554721 \h 12 HYPERLINK \l "_Toc241554722"2.1.3 Activation of Emergency Response Team PAGEREF _Toc241554722 \h 12 HYPERLINK \l "_Toc241554723"2.2 Disaster Recovery Team PAGEREF _Toc241554723 \h 13 HYPERLINK \l "_Toc241554724"2.3 Emergency Alert, Escalation and DRP Activation PAGEREF _Toc241554724 \h 13 HYPERLINK \l "_Toc241554725"2.3.1 Emergency Alert PAGEREF _Toc241554725 \h 13 HYPERLINK \l "_Toc241554726"2.3.2 DR Procedures for Management PAGEREF _Toc241554726 \h 14 HYPERLINK \l "_Toc241554727"2.3.3 Contact with Employees PAGEREF _Toc241554727 \h 14 HYPERLINK \l "_Toc241554728"2.3.4 Backup Staff PAGEREF _Toc241554728 \h 14 HYPERLINK \l "_Toc241554729"2.3.5 Recorded Messages / Updates PAGEREF _Toc241554729 \h 14 HYPERLINK \l "_Toc241554730"2.3.7 Alternate Recovery Facilities / Hot Site PAGEREF _Toc241554730 \h 14 HYPERLINK \l "_Toc241554731"2.3.8 Personnel and Family Notification PAGEREF _Toc241554731 \h 14 HYPERLINK \l "_Toc241554732"3 Media PAGEREF _Toc241554732 \h 15 HYPERLINK \l "_Toc241554733"3.1 Media Contact PAGEREF _Toc241554733 \h 15 HYPERLINK \l "_Toc241554734"3.2 Media Strategies PAGEREF _Toc241554734 \h 15 HYPERLINK \l "_Toc241554735"3.3 Media Team PAGEREF _Toc241554735 \h 15 HYPERLINK \l "_Toc241554736"3.4 Rules for Dealing with Media PAGEREF _Toc241554736 \h 15 HYPERLINK \l "_Toc241554737"4 Insurance PAGEREF _Toc241554737 \h 15 HYPERLINK \l "_Toc241554738"5 Financial and Legal Issues PAGEREF _Toc241554738 \h 16 HYPERLINK \l "_Toc241554739"5.1 Financial Assessment PAGEREF _Toc241554739 \h 16 HYPERLINK \l "_Toc241554740"5.2 Financial Requirements PAGEREF _Toc241554740 \h 16 HYPERLINK \l "_Toc241554741"5.3 Legal Actions PAGEREF _Toc241554741 \h 16 HYPERLINK \l "_Toc241554742"6 DRP Exercising PAGEREF _Toc241554742 \h 16 HYPERLINK \l "_Toc241554743"Appendix A Technology Disaster Recovery Plan Templates PAGEREF _Toc241554743 \h 17 HYPERLINK \l "_Toc241554744"Disaster Recovery Plan for PAGEREF _Toc241554744 \h 17 HYPERLINK \l "_Toc241554745"Disaster Recovery Plan for PAGEREF _Toc241554745 \h 19 HYPERLINK \l "_Toc241554746"Disaster Recovery Plan for Local Area Network (LAN) PAGEREF _Toc241554746 \h 21 HYPERLINK \l "_Toc241554747"Disaster Recovery Plan for Wide Area Network (WAN) PAGEREF _Toc241554747 \h 23 HYPERLINK \l "_Toc241554748"Disaster Recovery Plan for Remote Connectivity PAGEREF _Toc241554748 \h 25 HYPERLINK \l "_Toc241554749"Disaster Recovery Plan for Voice Communications PAGEREF _Toc241554749 \h 27 HYPERLINK \l "_Toc241554750"Appendix B Suggested Forms PAGEREF _Toc241554750 \h 29 HYPERLINK \l "_Toc241554751"Damage Assessment Form PAGEREF _Toc241554751 \h 29 HYPERLINK \l "_Toc241554752"Management of DR Activities Form PAGEREF _Toc241554752 \h 29 HYPERLINK \l "_Toc241554753"Disaster Recovery Event Recording Form PAGEREF _Toc241554753 \h 29 HYPERLINK \l "_Toc241554754"Disaster Recovery Activity Report Form PAGEREF _Toc241554754 \h 30 HYPERLINK \l "_Toc241554755"Mobilizing the Disaster Recovery Team Form PAGEREF _Toc241554755 \h 31 HYPERLINK \l "_Toc241554756"Mobilizing the Business Recovery Team Form PAGEREF _Toc241554756 \h 31 HYPERLINK \l "_Toc241554757"Monitoring Business Recovery Task Progress Form PAGEREF _Toc241554757 \h 32 HYPERLINK \l "_Toc241554758"Preparing the Business Recovery Report Form PAGEREF _Toc241554758 \h 32 HYPERLINK \l "_Toc241554759"Communications Form PAGEREF _Toc241554759 \h 33 HYPERLINK \l "_Toc241554760"Returning Recovered Business Operations to Business Unit Leadership PAGEREF _Toc241554760 \h 33 HYPERLINK \l "_Toc241554761"Business Process/Function Recovery Completion Form PAGEREF _Toc241554761 \h 33 Information Technology Statement of Intent This document delineates our policies and procedures for technology disaster recovery, as well as our process-level plans for recovering critical technology platforms and the telecommunications infrastructure. Appendix A Technology Disaster Recovery Plan Templates Disaster Recovery Plan for SYSTEM OVERVIEW PRODUCTION SERVERLocation: Server Model: Operating System: CPUs: Memory: Total Disk: System Handle: System Serial #: DNS Entry: IP Address: Other:HOT SITE SERVERProvide detailsAPPLICATIONS (Use bold for Hot Site)ASSOCIATED SERVERS KEY CONTACTSHardware VendorProvide detailsSystem OwnersProvide detailsDatabase OwnerProvide detailsApplication OwnersProvide detailsSoftware VendorsProvide detailsOffsite StorageProvide details BACKUP STRATEGY FOR SYSTEM ONEDailyProvide detailsMonthlyProvide detailsQuarterlyProvide details SYSTEM ONE DISASTER RECOVERY PROCEDURE Scenario 1 Total Loss of Data Provide details Scenario 2 Total Loss of HW Provide details ADDENDUM CONTACTS File Systems File System as of Minimal file systems to be created and restored from backup: Filesystem kbytes Used Avail %used Mounted on Other critical files to modifyNecessary directories to createCritical files to restoreSecondary files to restoreOther files to restore Disaster Recovery Plan for SYSTEM OVERVIEW PRODUCTION SERVERLocation: Server Model: Operating System: CPUs: Memory: Total Disk: System Handle: System Serial #: DNS Entry: IP Address: Other:HOT SITE SERVERProvide detailsAPPLICATIONS (Use bold for Hot Site)ASSOCIATED SERVERS KEY CONTACTSHardware VendorProvide detailsSystem OwnersProvide detailsDatabase OwnerProvide detailsApplication OwnersProvide detailsSoftware VendorsProvide detailsOffsite StorageProvide details BACKUP STRATEGY for SYSTEM TWODailyProvide detailsMonthlyProvide detailsQuarterlyProvide details SYSTEM TWO DISASTER RECOVERY PROCEDURE Scenario 1 Total Loss of Data Provide details Scenario 2 Total Loss of HW Provide details ADDENDUM CONTACTS File Systems File System as of Minimal file systems to be created and restored from backup: Filesystem kbytes Used Avail %used Mounted on Other critical files to modifyNecessary directories to createCritical files to restoreSecondary files to restoreOther files to restore Disaster Recovery Plan for Local Area Network (LAN) SYSTEM OVERVIEW SERVERLocation: Server Model: Operating System: CPUs: Memory: Total Disk: System Handle: System Serial #: DNS Entry: IP Address: Other:HOT SITE SERVERProvide detailsAPPLICATIONS (Use bold for Hot Site)ASSOCIATED SERVERS KEY CONTACTSHardware VendorProvide detailsSystem OwnersProvide detailsDatabase OwnerProvide detailsApplication OwnersProvide detailsSoftware VendorsProvide detailsOffsite StorageProvide details BACKUP STRATEGY for SYSTEM TWODailyProvide detailsMonthlyProvide detailsQuarterlyProvide details SYSTEM TWO DISASTER RECOVERY PROCEDURE Scenario 1 Total Loss of Data Provide details Scenario 2 Total Loss of HW Provide details ADDENDUM CONTACTS File Systems File System as of Minimal file systems to be created and restored from backup: Filesystem kbytes Used Avail %used Mounted on Other critical files to modifyNecessary directories to createCritical files to restoreSecondary files to restoreOther files to restore Disaster Recovery Plan for Wide Area Network (WAN) SYSTEM OVERVIEW EQUIPMENTLocation: Device Type: Model No.