Exhibit4b_TRAP_Contingency_Plan.docx

TOTAL FORCE INFORMATION TECHNOLOGY SYSTEMS (TFITS)

TOTAL FORCE INFORMATION TECHNOLOGY SYSTEMS REQUESTS FOR PROPOSALS (RFP) ASSESSMENT PROGRAM

(TRAP)

CONTINGENCY PLAN

TRAP

Product Manager, Total Force Information Technology Systems (PdM TFITS) PMM 110, Information Systems and Infrastructure Marine Corps Systems Command 2200 Lester Street Quantico, Virginia 22134

Nov 1, 2013 Version 1.0

Distribution Statement: Distribution authorized to the Department of Defense (DoD) and United States (U.S.) DoD staff and contractors only. Questions concerning technical content or any other request for this document shall be referred to the PdM TFITS, PMM 110, IS&I MCSC, 2200 Lester Street, Quantico, VA 22134

Warning: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U. S. C. Sec 2751 et seq.) or the Export Administration Act of 1979, as amended (Title 50, U. S. C. App 2401 et seq.). Violators of these export laws are subject to severe criminal penalties. Dissemination of this document is controlled under DoD Directive 5230.25.

Handling and Destruction Notice: Comply with distribution statement and destroy by any method that will prevent disclosure of contents or reconstruction of the document

This document contains information exempt from mandatory disclosure under the Freedom of Information Act (FOIA). Exemption 2 applies.

TRAP Contingency Plan Approval Page

The signatures below constitute US Government acceptance of this plan.

NAME

TRAP Project Manager

Date

NAME

TRAP Production Team Lead

Date

NAME

TRAP Information Assurance Manager (IAM)

Date

Table of Contents

EXECUTIVE SUMMARY

Total Force Information Technology Systems (TFITS) RFP (Request For Proposals) Assessment Program (TRAP) is an enterprise system that provides daily accountability and status of all Marines, other Service members and affiliated personnel under Marine Corps administrative and operational control. TRAP is a web based common access card (CAC) enabled application with an Unclassified but Sensitive Internet Protocol (IP) Router Network (NIPRNet) and Secret Internet Protocol Router Network (SIPRNet) instance. The application consists of custom and tailored commercial-off-the-shelf (COTS) software.

It is vital to maintain the sustained execution of mission critical processes and information technology systems for TRAP in the event of an extraordinary event that causes these systems to fail minimum production requirements. The TRAP Contingency Plan will assess the needs and requirements so that TRAP may be prepared to respond to the event in order to efficiently regain operation of the systems that are made inoperable from the event. The Contingency Plan encompasses the processes and procedures to maintain TRAP viability in the event of a disaster or cyber incident that may impose risk to TRAP application data.

In the event of a disaster or other circumstances which bring about the need for contingency operations, the normal organization of TRAP will shift into that of the contingency organization. The TRAP Incident Response Team (IRT) will maintain operations through five Protection Conditions (PROCON) that will guide the team through the activities of response, resumption, recovery, and restoration of the TRAP system. The IRT is divided into teams comprised of individuals with specific responsibilities or tasks, which must be completed to fully execute the plan. The sub-teams are structured to provide dedicated, focused support in the areas of their particular experience and expertise for specific response, resumption and recovery tasks, responsibilities, and objectives. A high degree of interaction among all teams will be required to execute the plan. Each team’s eventual goal is the resumption/ recovery and the return to stable and normal business operations and technology environments. Status and progress updates will be reported by each team leader to the Emergency Management Team Lead, who is the plan owner.

Overall, the focus of this plan is to restore essential business functionality to the TRAP application with minimal impact to the customer base.

1. INTRODUCTION

This document contains the Contingency Plan for the Total Force Information Technology Systems (TFITS) RFP (Request For Proposals) Assessment Program (TRAP). It is intended to serve as the central repository for the information, tasks, and procedures that would be necessary to facilitate the TRAP management’s decision-making process and its timely response to any disruptive or extended interruption of normal business operations and services. This is especially important if the cause of the interruption is such that a prompt resumption of operations cannot be accomplished by employing only normal daily operating procedures.

In terms of personnel and financial resources, the information, tasks and procedures detailed in this plan represent the TRAP management’s demonstrated commitment to response, resumption, recovery, and restoration planning. Therefore, it is essential that this plan remain viable and current in order to ensure the accuracy of its contents.

The TRAP Contingency Plan is intended to provide a framework for constructing procedures to ensure the safety of employees and the resumption of time-sensitive operations and services in the event of an emergency, such as a fire, power or communications blackout, tornado, hurricane, flood, earthquake, civil disturbance, or a cyber incident to include a virus, malicious code, denial of service, or social engineering attack.

The TRAP Contingency Plan is an on-going, funded business activity, budgeted to provide resources required to:

· Develop and revise application policies and functional procedures

· Exercise strategies, procedures, team and resource requirements

· Evaluate unattained test events

· Research processes and technologies to improve resumption and recovery efficiency

· Perform plan maintenance activities This Contingency Plan encompasses a consistent planning methodology necessary to create a viable, repeatable and verifiable continuity capability that includes:

· Implementing accurate and continuous data backup and off-site storage

· Implementing capabilities for rapid switching of voice and data communication circuits to alternate site(s) (to be implemented in the future)

· Providing alternate sites for business operations

· Constructing a contingency organization

· Implementing contingency strategies

PURPOSE

The Contingency Plan is intended to serve as the centralized repository for the information, tasks, and procedures that would be necessary to facilitate the TRAP application management’s decision-making process and its timely response to any disruptive or extended interruption of normal business operations and services.

SCOPE – DISASTER AND INCIDENT RESPONSE

The Contingency Plan encompasses the processes and procedures to maintain TRAP minimally required functionality in the event of a disaster or cyber incident until normal functionality is restored.

CONTINGENCY PLAN OVERVIEW

APPLICABLE PROVISIONS AND DIRECTIVES

The TRAP Contingency Plan was developed in accordance with the following executive decisions, regulatory mandates, provisions, and directives:

· Office of Management and Budget Circular A–130, Revised (Transmittal Memorandum No. 4), Appendix III, Security of Federal Automated Information Resources, November 2000.

· Computer Security Act of 1987, Public Law 100-235, January 1988.

· Presidential Decision Directive 63, Critical Infrastructure Protection, May 1998.

· Presidential Decision Directive 67, Enduring Constitutional Government and Continuity of Government Operations, October 1998.

· Executive Order 12656, Assignment of Emergency Preparedness Responsibilities, November 1988.

· Federal Information Processing Standards (FIPS) Publication 87, Guidelines for ADP Contingency Planning, March 1981.

· DOJ Order 2640.2D, Information Technology Security, July 12, 2001.

· National Institute of Standards and Technology (NIST) Special Publication 800-12, An Introduction to Computer Security: The NIST Handbook, Dec 28, 1997

· NIST Special Publication 800-34, Contingency Planning Guide for Information Technology Systems, May 2010

· NIST Special Publication 800-53, Recommended Security Controls for Federal Information Systems, August 2009

· DoD Directive 3020.26, Defense Continuity Program, January 9, 2009

· Department of Defense (DOD) Directive 8500.1, Information Assurance, November 21, 2003

· Department of Defense (DOD) Instruction 8500.2, Information Assurance (IA) Implementation, 6 February 2003

OBJECTIVES

It is important that the TRAP application develop contingency plans to minimize the impact of vulnerabilities that cannot be prevented.

The contingency plan seeks to accomplish the following objectives:

· Minimize the decision making timeframe

· Identify the resources needed to execute the actions defined by this plan

· Identify actions and methods of communication to be taken by pre-designated teams

· Identify critical data in conjunction with customers that will be restored during recovery phase of operations

· Define the process for testing and maintaining this plan and training for contingency teams

ORGANIZATION

In the event of a disaster, cyber incident, or other circumstance which require execution of contingency operations, the TRAP Incident Response Team members shall revert to contingency operations. The TRAP Incident Response Team is comprised of multiple sub-teams and will operate through five Protection Conditions (PROCON) that guide the team through the activities contained in each phase. Each team is comprised of a plan owner, a primary team lead, and an alternate team lead. All stakeholders have been assigned specific responsibilities and tasks that must be completed to fully execute this plan.

Figure 2-1, TRAP Incident Response Team, shows the base organizational structure. The sub-teams are structured to provide dedicated, focused support in the areas of their particular experience and expertise. A high degree of interaction among all teams will be required to execute the plan. Status and progress updates will be reported by each team lead (or alternate) as directed by the Emergency Management Team Lead.

The TRAP Incident Response Team’s responsibilities are:

· To ensure that a viable capability exists to respond to an incident.

· To manage all response, resumption, recovery, and restoration activities.

· To support and communicate with system administrators, security officers, and managers.

· To ensure regulatory requirements are satisfied.

· To exercise resumption and recovery expenditure decisions.

Figure 21 TRAP Incident Response Team

CONTINGENCY PLAN PROCESS

INCIDENT RESPONSE OVERVIEW

The TRAP Contingency Plan employs a five-step process to respond to a disaster or cyber incident. Disasters are natural or man-made events that pose a risk to the TRAP primary site. Cyber incidents are information security attacks that pose a risk to TRAP data such as malicious code or social engineering. If such risks are encountered, the Emergency Management Team (EMT) Lead assembles the team to assess the situation and take action. The goal throughout the process is to preserve TRAP data and maintain support to the user community with minimal interruption.

As the risk to the TRAP data increases, the EMT Lead moves the TRAP PROCON level higher to address the situation appropriately. As the risk subsides, the EMT Lead moves the TRAP PROCON downward ultimately back to normal operations. The TRAP PROCON system is intended to closely resemble and support the Department of Defense Information Condition (INFOCON) system. The INFOCON system provides a framework of prescribed actions necessary for reestablishing the confidentiality, availability, integrity and security of information systems. The PROCON system gives the TRAP application owner maximum flexibility to safeguard personnel and to continue the mission.

PROCON 5 –TRAP Normal Operations There is no apparent hostile activity against the TRAP system. Operational performance of all TRAP systems and sub-systems are monitored.

PROCON 4 – Disaster/ Attack Watch TRAP is under an increased risk of a disaster or cyber attack. Increased monitoring of all systems and sub-systems is mandated. Web access may be restricted to government sites only, and backing up files to removable media should be considered.

· Disaster Response: Conduct Damage Assessment.

· Cyber Attack Response Increase vigilance in TRAP monitoring.

PROCON 3 – Impending Disaster/ Attack Identified The TRAP EMT team has identified an impending disaster or a cyber attack. Security review on important systems is a priority, and TRAP EMT team member’s alertness is increased.

· Disaster Response: Prepare to move TRAP to alternate site.

· Cyber Attack Response: Investigate extent of the attack.

PROCON 2 – Evacuate or Restore/ Isolate Attack A disaster or a cyber attack has taken place but the TRAP EMT team is not at its highest alertness. Non-essential systems/ sub-systems may be degraded or taken offline to facilitate movement or to prevent further attack.

· Disaster Response: Move TRAP to alternate site/ back to primary site.

· Cyber Attack Response: Work with local G-6/ Marine Corp Network Operations and Security Command (MCNOSC) to prevent further damage.

PROCON 1 – TRAP alternate operations/ TRAP reconfigured A disaster is ongoing or attacks are continuing to take place and the TRAP EMT team is at maximum alertness. In the case of a disaster, TRAP is active at the alternate site. In the case of a cyber attack, any compromised systems or sub- systems are isolated from the rest of the network and the TRAP EMT team has reconfigured TRAP for normal operations.

· Disaster Response: TRAP Active in Alternate Site.

· Cyber Attack Response: TRAP reconfigured to reduce threat.

CRITICAL SUCCESS FACTORS AND ISSUES

This section addresses the factors and issues that specifically apply to the TRAP Contingency Plan that have been identified to be critical to the successful implementation of the Contingency Plan. These factors are as follows:

· Absolute commitment by senior management (both Government and System Integrator) to Contingency Planning and Disaster Recovery.

· Budgetary commitment to Disaster Recovery.

· Modifications and improvements to the current scheduling procedures for the retention and transportation of back up files to the offsite storage facility.

· Development and execution of the necessary Memorandums of Agreement (MOAs), Memorandums of Understanding (MOUs), and Service Level Agreements (SLAs).

MISSION CRITICAL SYSTEMS/ APPLICATIONS/ SERVICES

The following essential mission critical systems/ applications/ services that must be recovered at the time of disaster in the following order due to critical interdependencies:

· TRAP web services

· TRAP web site/ portal application

· TRAP Data Entry Forms

· TRAP User Maintenance Module

· TRAP Unit Maintenance Module

· TRAP User Activity Module

· TRAP Report Module

· TRAP Email Notification In developing strategies for the TRAP Contingency Plan, the team considered a range of probable and possible threats that present a risk. From that range of threats, likely scenarios were considered and appropriate strategies developed.

PROBABLE THREATS

Table 2-1 below depicts the threats most likely to impact TRAP and its sub-systems.

Climate Control

X

Aircraft Accident

X

Blackmail

X

Bomb Threats

X

HazMat Incident

X

Cold/ Frost/ Snow

X

Data Destruction

X

Earthquakes

X

Fire

X

Nuclear Mishaps

X

Sabotage/ Terrorism

X

Vandalism/ Rioting

X

Social engineering

X

Malicious code

X

Denial of service

X

Worm

X

Virus

X

Table 21 Probable Threats

SYSTEM DESCRIPTION

In accordance with DoD Instruction 5000.2 Enclosure 4.1, TRAP is a United States Marine Corps system – Mission Assurance Category (MAC) II. Authorized individuals worldwide depend on the accuracy and timeliness of TRAP data when making critical decisions that affect both the wartime and peacetime readiness of the Marine Corps. If the TRAP application ever becomes unreliable, the confidence in the quality, accuracy, and timeliness of the TRAP data will be lost and the ability to accurately ascertain the readiness of Marine Corps units would be negatively impacted and could potentially jeopardize the lives of Marines.

In accordance with Department of Defense Instruction 8500.2, as a MAC II system, TRAP must establish a program to ensure comprehensive and effective continuity of business essential functions during a broad spectrum of emergencies or situations that may disrupt normal operations. TRAP must establish a recovery strategy to include an alternate site to mitigate the impact of disruptive events that provides for the partial resumption of mission or business essential functions within 48 hours of activation.

PHYSICAL ENVIRONMENT

Primary site is Marine Corps Base, Quantico, VA.

TECHNICAL ENVIRONMENT

TRAP is a web-based common access card (CAC)-enabled application with a NIPR and SIPR instance. The application consists of custom application software and tailored Commercial-Off-The-Shelf (COTS) software. The custom application software was developed using C# on an ASP.Net framework. The database is built utilizing Oracle 11g.

CONTINGENCY PLAN

PLAN MANAGEMENT

CONTINGENCY PLANNING WORKGROUPS

The TRAP Information Assurance Working Group (IAWG) and Production Working Group (PWG) shall be chartered and facilitate the review of this Contingency Plan’s strategies, teams, and tasks.

CONTINGENCY PLAN COORDINATOR

A coordinator and an alternate shall be appointed to monitor and coordinate the TRAP Contingency Plan, training and awareness, exercises, and testing (see Appendix B). The Contingency Plan Coordinator will work closely with the TRAP Lead Engineer and Program Manager to ensure the viability of the TRAP Contingency Plan.

CONTINGENCY PLAN ORGANIZATION

The TRAP program has developed and trained individuals to respond to an incident affecting the TRAP system. The Incident Response Team (IRT) is made up of the following teams. Individuals may be assigned to more than one team as long as the team responsibilities do not conflict causing a delay in the execution of this plan.

· Emergency Management Team (EMT). It is the responsibility of this team to order the execution of the recovery plan, based on the advice of the Damage Assessment Team.

· Damage Assessment Team (DAT). The DAT will be the first team activated when an emergency occurs. It is the responsibility of this team to inspect the integrity of the system.

· Backup Recovery Team (BRT). The BRT is responsible for executing the Backup and Recovery Plan.

· Customer Focus Team (CFT). The CFT is responsible for ensuring that customer relations are maintained throughout the incident.

ALTERNATE SITE

A suitable alternate TRAP site is co-located with the system integrator lab. The lab has a warm TRAP suite that meets all of the MAC II Classified system requirements in the DoDI 8500.2 guidance including being continuously updated to meet Information Assurance Vulnerability Alert (IAVA) and Operational Directive (OpDir) guidance as they are released.

DATA BACKUP

In order to minimize the impact of a disaster, backups are accomplished in accordance with the TRAP Backup Standard Operating Procedure (SOP), which shall be documented in a Systems Administrators Manual (SAM). The TRAP team performs backups according to DoD and DoN guidance, as well as any specific guidance stipulated by the TRAP project officer. The DoDI 8500.2, Information Assurance (IA) Implementation directive identifies certain IA Controls that dictate the extent to which backups should be conducted. The backup Standard Operating Procedure (SOP) establishes responsibilities and procedures for the TRAP IA Program’s backups, to include organizational and individual responsibilities, registration, compliance criteria, extensions, enforcement, and verification.

For NIPRNet systems, a copy of the weekly backups must be securely stored locally. If local storage is not available, arrangements should be made to transport the backups to the Marine Corps Systems Command Security office located aboard MCB Quantico in building 2200. All backup media must be stored in an environmentally controlled facility and placed in a fireproof safe. In the event of an impending disaster, more frequent backups will be taken to ensure the recovery of the most current data version and to increase the likelihood of usable media in a post-event scenario. For SIPRNet systems, the Information Assurance Manager (IAM), Information Assurance Officer (IAO), or their authorized representatives will transport all classified backup media to the Marine Corps System Command Security office for appropriate storage.

TERMS AND DEFINITIONS

The following is a comprehensive list of terms that are important in contingency planning and recovery operations.

Alert - Notification that a disaster situation has occurred - stand by for possible activation of disaster recovery plan.

Alternate Site - A location, other than the normal facility, used to process data and/ or conduct critical business functions in the event of a disaster. Similar Terms: Alternate Processing Facility, Alternate Office Facility, and Alternate Communication Facility.

Application Recovery - The component of Disaster Recovery that deals specifically with the restoration of business system software and data after the processing platform has been restored or replaced. Similar Terms: Business System Recovery.

Assumption – A thing that is accepted as true or as certain to happen without proof Backup – To make a duplicate of application and/or Operating System (OS) data in the event that the original is lost, damaged, or required for restoration of services after a disaster Backup Agreement - A memorandum of understanding or agreement to provide a service that includes the method of performance, any applicable fees, the duration, the services provided, and the extent of security and confidentiality maintained. This agreement also identifies the procedures or standby equipment that is available for use in the event of a failure or inaccessibility of normally used equipment.

Backup Personnel Roster - A roster that identifies the names of authorized personnel who can fill a recovery team position when the primary person is not available Business Continuity Planning (BCP): Business Continuity Planning refers to the activities required to keep an organization running in the event of a disruption of daily functions. It should identify and document a collection of procedures and information that is developed, compiled and maintained in readiness for use in the event of an emergency or disaster.

Business Impact Analysis (BIA) - predicts the consequences of disruption of a business function and process and gathers information needed to develop recovery strategies.

Business Recovery Process – Recovery Processes identify activities that an organization should implement during a recovery effort. There are seven major steps identified in this process: 1) Immediate response 2) Environmental restoration 3) Functional restoration 4) Data synchronization 5) Restoration of business functions 6) Interim site operations and 7) Return to normalcy.

Damage Assessment - The process of assessing damage, following a disaster, to computer hardware, vital records, office facilities, etc. and determining what can be salvaged or restored and what must be replaced.

Disaster - Any event that creates an inability on an organizations part to provide critical business functions for an unspecified period of time.

Incident – An incident is the violation of an explicit or implied security policy. In general, types of activity that are commonly recognized as being in violation of a typical security policy include but are not limited to:

· attempts (either failed or successful) to gain unauthorized access to a system or its data, including PII related incidents

· unwanted disruption or denial of service

· the unauthorized use of a system for processing or storing data

· changes to system hardware, firmware, or software characteristics without the owner's knowledge, instruction, or consent

APPENDIX A – CONTINGENCY PLAN TEAM MEMBERS TEMPLATE

Table A- 1 Contact Information

Incident Response Team Phone Tree. In the event of an incident, the TRAP Incident Response Team Phone Tree will be activated. Each person will call the next person on the list and the final person on the callback list will contact their team lead to let him or her know that all notifications have been made. If a person cannot be reached, the team member will call the next person and report the party whom could not be contacted. The person(s) not contacted will be reported to the team lead.

A-9

APPENDIX B –TEAM STAFFING AND ROLE TEMPLATE

B-11

APPENDIX C – ALTERNATE SITE TRUSTED RECOVERY

General The objective of trusted recovery is to ensure that TRAP remains secure and in an accountable state in the face of failures and discontinuities of operation. To accomplish this, TRAP incorporates a set of mechanisms enabling it to remain in a secure state whenever failures or discontinuities occur. Additionally, this plan includes a set of procedures enabling the administrators to bring the system to a secure state whenever unanticipated failures or discontinuities occur. Care will be taken to ensure only appropriately cleared personnel support the trusted recovery. If appropriately cleared personnel, as defined by the Security Manager or IAO, are unavailable to perform maintenance or repair, personnel with a lesser clearance may be used but only under escort and monitored by approved personnel, as defined by the IAO.

In essence, a Trusted Recovery is ensured in four ways:

· Avoidance – built in TRAP features that prepare for an incident and support the reduction of risk if such an incident occurs. Such features are:

· Install a baseline of protection on all systems and networks

· Ensure that backup copies of the baselines are available and only such baselines are used to recover

· A sound system configuration management plan and maintain close configuration control of hardware and software found in the Corporate Information Technology DataBase (CITDB)

· Ensure that system restoration software, repair disks, backup media, or spares are available to recover the system after an incident

· Identification - If an incident is reported, determine the nature of the incident. The seriousness of the incident will determine what action should be taken.

· Maintain awareness of DOD Computer Network Defense situation including INFOCON, recent IAVA/Bs (Alerts & Bulletins), and Attack Sensing & Warning

· As soon as an incident is suspected, the person handling the incident should start taking notes to keep a log of events.

· Make immediate recommended change to INFOCON if the specific situation warrants.

· Containment – procedures to limit the damage of failures and discontinuities of TRAP operations. Such procedures are:

· Freeze/ eliminate compromised accounts

· Isolate affected network segment or system(s)

· Block Internet Protocol addresses/ phone lines

· Obtain a full backup of the system(s) or network affected

· Recovery - procedures to restore TRAP to normal mission status.

· Use only the approved system recovery disks to recover the operating system, applications, and security tools.

· Restoration of TRAP data will be completed by using the most recent system backup.

· Restoration of TRAP components in the corrector according to the TRAP SAM -- Total Force Structure Management System, System Administration Manual (SAM)

· Once TRAP is back online, incident response personnel should continue to monitor for backdoors that escaped detection and eradication.

Circumstances that Inhibit Trusted Recovery If at any point during the resumption of the system a situation is encountered which could inhibit a trusted recovery, TRAP personnel will cease resumption activities, document the situation and consult with the IAO. It is the responsibility of the IAO to determine the appropriate mitigating procedures necessary to enable a trusted recovery of the system. The IAO shall maintain the documented information related to the incident.

Trusted Recovery Practices The following is a list of Trusted Recovery practices adhered to on the TRAP project to increase the likelihood of each recover is a trusted one. The mechanisms are provided to assure that, after a system failure or other discontinuity, recovery without a protection compromise is obtained.

· Use only fbackup(1M) and frecover(1M) to back up and recover files selectively. Only fbackup(1M) and frecover(1M) retain access control lists (ACLs). Use the -A option of these commands when backing up and recovering files for use on systems that do not implement ACLs.

· If you plan to recover the files to another system, be sure that the user's user name and group name on both systems are consistent.

· Remember that your backup media is sensitive material. Allow access to the media only on the basis of proven need.

· Label backup tapes and store them securely. Offsite storage provides maximum security. Keep archives for a minimum of six months, and then recycle the media.

· Daily incremental and full weekly backups are recommended.

Synchronize your backup schedule with the information flow in your organization. For example, if a major database is updated every Friday, you might want to schedule your weekly backup on Friday evenings.

· If all files must be backed up on schedule, request that all users log off before performing the backup. However, fbackup (1M) warns you if a file is changing while the backup is being performed.

· Examine the logfile of latest backups to identify problems occurring during backup. The backup logfile should have restrictive permissions set.

· Frecover (1M) allows you to overwrite a file. However, the file retains the permissions and ACLs set when the file was backed up.

· You must test your recovery process beforehand, to make sure you can fully recover data in the event of an emergency.

· When recovering files from another machine, you might have to execute the chown command to set the user ID and group ID for the system on which they now reside, if the user and group do not exist on the new system. If files are recovered to a new system that does not have the specified group, the files will take on the group ownership of the person running frecover (1M). If owner and group names have different meanings on different systems, recovery results might be unexpected.

· Power failure should not cause file loss. However, if someone reports a lost file after a power failure, look for it in/ lost+found before restoring it from a backup tape.

· To verify contents of the tape being recovered, use the -I option of frecover (1M) to preview the index of files on the tape. Note, however, that existing permissions of a file system are kept intact by the backup; frecover (1M) prevents you from reading the file if the permissions on the file forbid it.

· Never recover in place any critical files such as /etc/passwd, or those in /tcb/files. Instead, restore the file to a /tmp directory, and give this directory permission drwx, preventing anyone else from using it. Compare the restored files with those to be replaced. Make any necessary changes.

· Auditing is not enabled automatically when you have recovered the system. Be sure to turn auditing on C-14 image2.png image3.jpeg image4.png image5.png image6.emf oleObject1.bin Emergency Management Team

Backup Recovery Team

Customer Focus Team

Damage Assessment Team

Executive Management Team image1.jpeg