**Disaster Recovery**: The assessment and recovery procedures for responding to a man-made or natural event that significantly disrupts or eliminates business and technology operations, yet does not threaten the existence of the enterprise. This includes sabotage, theft or corruption of resources, successful large scale hacker/virus attacks, building damage, fire, flood, and electrical outages. Two time-related aspects of disaster recovery need to be immediately and continually evaluated: (1) the method for recovery, and (2) the affect on mission accomplishment. Both of these may change as the amount of time increases from the moment the disaster occurred (e.g., facilities considerations, system and data restore procedures and the affect on business services will probably be different for 2-minute, 2-hour, 2-day, and 2-week outages). Security and privacy issues in this area affect all levels of the architecture. **Continuity of Operations**: This refers to procedures that are invoked if all or part of the enterprise are unexpectedly destroyed or forced to disband. In this scenario, the enterprise is unable to conduct any business or IT operations for a period of time. The recovery response is scripted in a Continuity of Operations Plan (COOP) that identifies where, how, and when business and IT functions would be restored. Security and privacy issues in this area affect all levels of the architecture.
Category: Security and Privacy