Drotos Engineering: Disaster Recovery and Business Continuity

profilearmman
NTC300_v6_wk3_DRBC_Playbook_template.docx

NTC/300 v6

Drotos Engineering Week 3 DR/BC Playbook Procedure Template

NTC/300 v6

Page 2 of 2

C:\Users\djshirey\OneDrive - University of Phoenix\F_Drive\Style Guides\UPX Logos\Horizontal format\UOPX_Sig_Hor_Black_Medium.pngDrotos Engineering DR/BC Playbook Procedure Template

Event

[Enter the name and description of the event.]

For example: Hacking: A specific application has been hacked.

Disaster Recovery

Responsibilities

[Identify who is involved in diagnosing and resolving the issues.]

Name

Title/Role

Emergency Number

Email

Responsibilities

Initial Plan of Action

[Describe what needs to be done to stop the damage, prevent further damage, and provide a current workaround or work process for employees to follow.]

For example: If the event is that an application has been hacked, the initial plan of action could be:

· Implement manual downtime protocol.

· Shut down all internet access.

· Shut down internal and external email.

Troubleshooting and Resolution

[Identify the troubleshooting steps along with referencing or naming potential procedures.]

For example: Using the example above, define the technical approach to bringing the application back online.

· Segment the applications.

· Scrub the application while off the internet, and refer to the antivirus/malware policy.

· Check the open firewall ports, and refer to the firewall configuration documentation.

· Ensure secure user access.

Business Continuity

Define your approach to ensure the business teams within the organization have a plan to conduct business while the disaster recovery process is in progress.

Responsibilities

[Identify who is involved in managing the business effects of the event while disaster recovery is in progress.]

Name

Title/Role

Emergency Number

Email

Responsibilities

Initial Plan of Action

[Describe what needs to be done to enable business to continue.]

For example, if the event is that an application has been hacked, the initial plan of action could be:

· Use manual downtime protocol.

· Access internet and email via smartphones or alternate business locations.

· Determine and execute internal and external communications regarding service limitations.

Troubleshooting and Resolution

[Identify the troubleshooting and resolution steps the internal business partners execute to support the technical resolution to the problem and the interim emergency protocols.]

For example:

Test access to the application (local and remote and with different devices)

· User test

· Administrator test

Copyright© 2018 by University of Phoenix. All rights reserved.

Copyright© 2018 by University of Phoenix. All rights reserved.