Business Continuity and Disaster Recovery for InfoSec Managers

1.5 Endnotes 21

Chapter 1

project should begin with a kick-off meeting where the team can establish

project objectives and define the required deliverables. It is important to set

key milestones and define a timeline for accomplishment of those mile-

stones. Establishing reporting requirements and documentation require-

ments is recommended at this kick-off meeting.

Adhering to the aforementioned will create a solid foundation from

which to work and help you better protect your enterprise. The ideas and

methods presented herein should provide you with all of the fundamental

concepts necessary to develop a BCP and implement it into your work

environment. In the next chapter, we will discuss risk—what it is, how to

determine risk, and how to assess its impact on your organization. It is just

the next step you must take in implementing all of the necessary measures

to protect your company.

1.5 Endnotes

1. Texas Department of Information Resources, Business Continuity

Planning Guidelines.

2. The reader is encouraged to visit

http://news.findlaw.com/legalnews/lit/enron/

for more information on the downfall of Enron.

3. National Institute of Standards and Technology, Special Publica-

tion 800-34: Contingency Planning Guide for Information Technol-

ogy Systems. June 2002. Section 2.2, p. 11.

4. Malicious software is often referred to as malware.

5. National Institute of Standards and Technology, Special Publica-

tion 800-12: An Introduction to Computer Security: The NIST

Handbook. October 1995. Chapter 11, Preparing for Contingen-

cies and Disasters.

6. U.S. Public Law 100-235. 100

th

Cong., 40 U.S. Code 759, 101

Stat. 1724-1730, January 8, 1988. The Computer Security Act of

1987.

This Page Intentionally Left Blank