Essay regarding Plan para Contingencia

Plan para Contingencia

NIST Special Publication 800-34 Rev. 1

Contingency Organizing Guide intended for

Federal Info Systems

Marianne Swanson

Pauline Bowen

Amy Wohl Phillips

Dean Gallup

David Lynes

NIST Unique Publication 800-34 Rev. one particular

Contingency Organizing Guide intended for

Federal Details Systems

Marianne Swanson

Pauline Bowen

Amy Wohl Phillips

Dean Terme conseille

David Lynes

May 2010

U. S i9000. Department of Commerce

Whilst gary Locke, Secretary

National Start of Requirements and Technology

Patrick Deb. Gallagher, Movie director

Certain business entities, gear, or supplies may be determined in this file in order to illustrate an trial and error procedure or perhaps concept effectively. Such identity is not intended to indicate recommendation or perhaps endorsement by the National Company of Specifications and Technology, nor is this intended to mean that the entities, materials, or perhaps equipment happen to be necessarily the best available for the reason.

There are referrals in this syndication to documents currently underneath development simply by NIST according to responsibilities designated to NIST under the Federal Information Security Management Action of 2002. The strategies in this document may be used even before the completion of such associate documents. Therefore, until such time because each doc is completed, current requirements, guidelines, and methods (where they will exist) stay operative. For planning and transition reasons, federal agencies may wish to closely follow the progress these new documents by NIST. Individuals are also motivated to review the public draft papers and offer their comments to NIST. Almost all NIST documents mentioned with this publication, other than the ones noted above, are available at http://csrc.nist.gov/publications.

Countrywide Institute of Standards and Technology Exceptional Publication 800-34 Natl. Inst. Stand. Technol. Spec. Publ. 800-34, 150 pages (May 2010) CODEN: NSPUE2

BACKUP PLANNING GUIDELINE FOR GOVERNMENT INFORMATION DEVICES

Reports in Computer Systems Technology

The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U. H. economy and public welfare by providing technical leadership intended for the nation's dimension and standards infrastructure. ITL develops assessments, test strategies, reference data, proof of principle implementations, and technical analysis to progress the development and productive make use of information technology. ITL's responsibilities are the development of specialized, physical, management, and management standards and guidelines for the budget-friendly security and privacy of sensitive unclassified information in federal computer systems. This Special Publication 800-series reports about ITL's research, guidance, and outreach efforts in laptop security and its collaborative activities with industry, government, and academic businesses.

ii

A CONTINGENCY PLANNING GUIDE FOR NATIONAL INFORMATION DEVICES

Authority

This document have been developed by the National Start of Standards and Technology (NIST) in furtherance of its statutory responsibilities underneath the Federal Details Security Administration Act (FISMA) of 2002, Public Regulation 107-347.

NIST is responsible for developing standards and guidelines, which include minimum requirements, for providing adequate details security for all agency functions and possessions, but such standards and guidelines will not apply to countrywide security systems. This guideline is usually consistent with the requirements of the Office of Management and Price range (OMB) Circular A-130, Section 8b(3), " Securing Company Information Systems, ” as analyzed in A-130, Appendix IV: Analysis of Important Sections. Additional information is usually provided in A-130, Appendix III.

This kind of guideline has become prepared for use by national agencies. It can be used by non-governmental organizations on the voluntary basis and is not subject to copyright. Attribution will be appreciated simply by NIST.

Practically nothing in this document should be taken to contradict...