Date Published: May 2010
Supersedes:
SP 800-34 (06/13/2002)
Author(s)
Marianne Swanson (NIST), Pauline Bowen (NIST), Amy Phillips (BAH), Dean Gallup (BAH), David Lynes (BAH)
This publication assists organizations in understanding the purpose, process, and format of information system contingency planning development through practical, real-world guidelines. This guidance document provides background information on interrelationships between information system contingency planning and other types of security and emergency management-related contingency plans, organizational resiliency, and the system development life cycle. This document provides guidance to help personnel evaluate information systems and operations to determine contingency planning requirements and priorities.
This publication assists organizations in understanding the purpose, process, and format of information system contingency planning development through practical, real-world guidelines. This guidance document provides background information on interrelationships between information system...
See full abstract
This publication assists organizations in understanding the purpose, process, and format of information system contingency planning development through practical, real-world guidelines. This guidance document provides background information on interrelationships between information system contingency planning and other types of security and emergency management-related contingency plans, organizational resiliency, and the system development life cycle. This document provides guidance to help personnel evaluate information systems and operations to determine contingency planning requirements and priorities.
Hide full abstract
Keywords
contingency planning; resilience; information system contingency plan; incident response plan; disaster recovery plan
Control Families
Contingency Planning; Maintenance; Planning; Risk Assessment; System and Services Acquisition
) or https:// don't prove our archive is authentic, only that you securely accessed it. Note that we are working to fix that :)
