Microsoft Word Hardware Reconfiguration Methodology V final2

Data security requirements

Before carrying out any backup, it is important to determine security requirements that are necessary for safeguarding data, both during backup and storage. Consider the following:

1. 
   Will data be sent over the network? If so, is it on a trusted network? If not, then perhaps data should be encrypted; this can be done by piping backup the data stream through SSH or GPG before it goes out onto the network.
   

2. 
   Should the data be encrypted, regardless if it is backed up locally or remotely? If so, then the data should be encrypted from the source system using GPG or other similar tool.
   

3. 
   If encryption is used, is there a mechanism or resource to help in the management of encryption keys (i.e. PKI)? Who has access to the keys? Who has the passwords necessary for encryption and decryption?
   

4. 
   What network tool should be used for network backups? RSH, SSH, and Netcat can be used. SSH should be used for encrypting the network stream between computer systems. RSH and Netcat can be used on trusted networks or if the data stream is already encrypted via other means (i.e. GPG).
   

5. 
   What are the current security settings for the machines involved in the backup process (local sources and remote systems)? What are security settings supposed to be set to? Can unauthorized users or systems gain access to either the source and/or remote systems while backups are being performed?
   

6. 
   Can the backup tool support output/input piping? This may be required, depending on the type of backup to be done, including compression and encryption requirements as
   

well as data backup location (local or remote backup system). Tar, Cpio, Dump, and DD
all support piping. Advanced piping capability can be achieved through scripts.

7. 
   Does the backup user have the necessary rights and permissions to backup all system and user data? Does that user have permissions to send and receive backup data streams over the network from/to remote systems?
   

4.