#REQUIREMENTS FOR MIGRATION

You need to upload extract the entire archive to a location such as /opt/Inprotect

You must vi the new configs Inprotect/etc/inprotect.cfg and Inprotect/html/config.php with your desired settings.

There are new copies of the scanlite modules at Inprotect/usr/share/Inprotect/perl/ they need to be copied to lib dir for Net:Nessus

One ensure all the necessary Perl modules are loaded, as the migration script may utilize the following as required by nessusCront_1.60.pl backend code.

use Data::Dumper::Simple; use Net::IP; use Net::Nslookup; use Net::Netmask; use MIME::Lite; #use MIME::Lite::HTML; use Date::Calc qw( Delta_DHMS Add_Delta_YMD ); use DBI; use Getopt::Std; use Switch; use Socket; use POSIX qw(setsid); use IO::Socket;

STEPS YOU NEED TO PERFORM TO DO SUCCESSFUL DATABASE TASKS. ( BACKUP, NEW DB CREATION, MIGRATION OF YOUR EXISTING DATA ) CAN BE DONE IN THREE SIMPLE STEPS.

1. EXISTING DB SHOULD BE BACKED UP by means of

[root@host]# mysqldump -p inprotect > inprotect_0.22.5_backup.sql
#DO NOT DROP OLD DB YET, WE NEED IT FOR MIGRATION OF DATA
      #This is a precautionary measure to have full backup of original db

2. PREP NEW DATABASE INPROTECT2 FROM CLEAN INSTALL.SQL VIA install.pl

      [root@host]# cd /opt/Inprotect/install/
      [root@host]# ./install.pl

EXAMPLE OF USAGE:

[root@fs1 install]# ./install.pl

Checking Prerequisities: DBI OK MIME::Lite OK Parallel::ForkManager OK Date::Calc OK Crypt::CBC OK MIME::Base64 OK IO::Socket OK POSIX OK Socket OK Crypt::Blowfish OK Net::IP OK Net::Netmask OK Net::Nslookup OK

System meets the prerequisites, continuing…

Welcome to Inprotect 1.00.0_alpha_12 [ Central Node Installation]

**Warning: installation must be run as root user!!!! Please Choose from the following options:

1 - Configure Inprotect 2 - install Database components and Configure Inprotect 3 - Migrage existing data to new Inprotect Installation Q - Quit without installation To install scanner nodes load nessus, add first users, and configure a feed. Make your selection [1-3] 3

Fill in all required fields the script will prompt to run a second script

otherwise you will have to run it manually. This will take some time to process, depend on size of you network and scans to date, it could take in excess of 4 hours to migrate each unique scan time and data into the new db. This will evaulate each scan and populate various fields in numerous new tables ( with data that can be verified from reviewing various msg contents from nessus_results, for each report to populate individual hosts stats, incident tracker, nessus_feed version, scan server, feed type at time of the scan, etc ( very thorough ).

[root@host]# ./migrate_data_to_1.0_official.pl

Full logging to

$rootdir/var/log/next_generation.log for debug can be provided to kenneth[dot]kline[at]gmail[dot]com for help migration / debugging

So long as the original db is intact we can start the process over to retry migration by starting at step 2 as it will drop the the new db tables and retry migration ( should only do this when 1. you have not started using the new version, and 2 have been provided a new version of the migration script ).