The following procedures are provided for recovery of at the original or established alternate location. Recovery procedures are outlined per team and must be executed in the sequence presented to maintain an efficient recovery effort. Instruction: Provide general procedures for the recovery of the system from backup media. Specific keystroke-level procedures may be provided in an appendix. If specific procedures are provided in an appendix, a reference to that appendix must be included in this section. Teams or persons responsible for each procedure must be identified. Delete this instruction from your final version of this document. Notifications during recovery include problem escalation to leadership and status awareness to system owners and users. This section describes the procedures for handling escalation notices that define and describe the events, thresholds, or other types of triggers that may require additional action. Instruction: Provide appropriate procedures for escalation notices during the recovery efforts. Teams or persons responsible for each escalation/awareness procedure must be identified. Delete this instruction from your final version of this document. Reconstitution is the process by which recovery activities are completed and normal system operations are resumed. If the original facility is unrecoverable, the activities in this phase can also be applied to preparing a new permanent location to support system processing requirements. A determination must be made whether the system has undergone significant change and will require reassessment and reauthorization. The phase consists of two major activities: (1) validating successful reconstitution and (2) deactivation of the plan. Concurrent processing is the process of running a system at two separate locations concurrently until there is a level of assurance that the recovered system is operating correctly and securely. Validation data testing is the process of testing and validating data to ensure that data files or databases have been recovered completely at the permanent location. Instruction: Describe procedures for testing and validation of data to ensure that data is correct and up to date as of the last available backup. Teams or persons responsible for each procedure must be identified. An example of a validation data test for a moderate-impact system would be to compare a database audit log to the recovered database to make sure all transactions were properly updated. Detailed data test procedures may be provided in F Appendix System – Validation Test Plan. Delete this instruction from your final version of this document.
The following procedures are provided for recovery of at the original or established alternate location. Recovery procedures are outlined per team and must be executed in the sequence presented to maintain an efficient recovery effort. Instruction: Provide general procedures for the recovery of the system from backup media. Specific keystroke-level procedures may be provided in an appendix. If specific procedures are provided in an appendix, a reference to that appendix must be included in this section. Teams or persons responsible for each procedure must be identified. Delete this instruction from your final version of this document. Notifications during recovery include problem escalation to leadership and status awareness to system owners and users. This section describes the procedures for handling escalation notices that define and describe the events, thresholds, or other types of triggers that may require additional action. Instruction: Provide appropriate procedures for escalation notices during the recovery efforts. Teams or persons responsible for each escalation/awareness procedure must be identified. Delete this instruction from your final version of this document. Reconstitution is the process by which recovery activities are completed and normal system operations are resumed. If the original facility is unrecoverable, the activities in this phase can also be applied to preparing a new permanent location to support system processing requirements. A determination must be made whether the system has undergone significant change and will require reassessment and reauthorization. The phase consists of two major activities: (1) validating successful reconstitution and (2) deactivation of the plan. Concurrent processing is the process of running a system at two separate locations concurrently until there is a level of assurance that the recovered system is operating correctly and securely. Validation data testing is the process of testing and validating data to ensure that data files or databases have been recovered completely at the permanent location. Instruction: Describe procedures for testing and validation of data to ensure that data is correct and up to date as of the last available backup. Teams or persons responsible for each procedure must be identified. An example of a validation data test for a moderate-impact system would be to compare a database audit log to the recovered database to make sure all transactions were properly updated. Detailed data test procedures may be provided in F Appendix – System Validation Test Plan. Delete this instruction from your final version of this document.
A06-FedRAMP-IS-Contingency-Plan-Temp-2016-05-18-v03-00.docx