Microsoft Word Hardware Reconfiguration Methodology V final2

Laboratory isolation

It is important before proceeding with any tests or modifications that the test environment (i.e. laboratory) be completely isolated from any of the operational networks. Both networks need to be free from any potential source of contamination that could be caused the other. If either environment were interconnected it would make bug tracking and troubleshooting more problematic. Even environments separated by NAT-based firewall systems cannot stop all possible cross-contamination issues. Thus, when conducting tests on C2 systems and their networks it is important to determine the sources of possible outside influence in order to track down bugs or other issues. Furthermore, the extra layer of objectivity afforded by isolation will make system reaccredidation and recertification longer and more complex as outside sources may have to be taken into account.

3. Backing up

It most certainly is important to backup all data before proceeding with software testing in the event changes must be rolled back. However, depending on the specifics of the test environment, the software used and installed, backups may not always be necessary, although they are often a good idea. In addition to preserving data backups will allow for the additional testing of new backup technologies, methodologies, and emergency restoration procedures.

Data to be backed up will vary considerably and will be according to the type of data and test systems to be backed up. A backup may consist of user data, applications, and configurations or it could be a full system backup. However, the backing up multiple test systems may result in an excessive work and may therefore be more appropriate to use cloning and distribution systems (i.e. Norton Ghost) instead. This approach is particularly well suited to environments where all or most of the systems are identical. More information on backing up can be found in Section 3.

4.