Upgrading from a previous version of the application to version 4.0.1

You can upgrade a previous version of Kaspersky Industrial CyberSecurity for Networks to Kaspersky Industrial CyberSecurity for Networks version 4.0.1 by using the kics4net-backup.sh data migration script from the application distribution kit. Kaspersky Industrial CyberSecurity for Networks versions 3.0.1 and 4.0 can be upgraded to version 4.0.1 using the kics4net-backup.sh script.

The kics4net-backup.sh script lets you migrate the following data from the previous version of the application to Kaspersky Industrial CyberSecurity for Networks 4.0.1:

• Security policy
• Data on the state and/or operating modes of technologies and methods
• Settings for updating application modules and databases
• Information about an added license key
• Audit entries
• Application messages
• Vulnerabilities (or Vulnerability risks)
• Registered events
• Saved traffic for events
• Network map data

The scenario for upgrading from a previous version of the application using the kics4net-backup.sh script consists of the following steps:

1. Creating a backup copy of data from the previous version of the application

   To create a backup copy of data from the previous version of the application:

   1. On the computer that performs Server functions for the previous version of the application, copy the kics4net-release_<application version>.tar.gz archive from the application distribution kit into a folder of your choice.
   2. Go to the folder containing the copied archive and enter the following command to unpack it:

      tar -zxvf kics4net-release_<application version>.tar.gz

      The unpacked folders and files will appear in the subfolder kics4net-release_<application version>.

   3. Go to the folder with the unpacked files of scripts and packages for installing, verifying and removing application components. The files are located in the kics4net-release_<application version>/linux-astra subfolder.
   4. Enter the following command:

      sudo bash kics4net-backup.sh -b -p <path to backup file> -e -t -n

      where:

      • -b is a setting that enables writing of data to the backup file (required setting).
      • -p is a setting indicating the full path and name of the created backup file (required setting).
      • -e is a setting for disabling retention of registered events (events are saved by default).
      • -t is a setting for disabling retention of traffic for events (traffic for events is saved by default).
      • -n is a setting for disabling retention of network map data (network map data is saved by default).

        Example: sudo bash kics4net-backup.sh -b -p ./old_kics4net_data

      The script will begin the data backup process. Wait for the kics4net-backup.sh script to finish and save the backup file that is created.

2. Removing the previous version of the application

   This step is necessary if you want to install components of the current version of the application to the same nodes where components of the previous version are installed.

   If a Kaspersky Industrial CyberSecurity for Networks version 4.0.1 Server will be installed to a separate computer (not to the computer hosting a Server of the previous version of the application), copy the created backup file to the separate computer.

   Components of a previous version of the application can be removed in the following ways:

   • Centrally on all nodes where the previous version of the application was installed.

     This option uses the application components centralized installation script via the centralized removal procedure.

   • Locally at each node where a component from the previous version of the application is installed.

     This option uses the application components local removal script (if a component from the previous version of the application provides the capability for local installation and local removal).

   After removing components of the previous version of the application, make sure that the computers satisfy the hardware and software requirements for installing Kaspersky Industrial CyberSecurity for Networks version 4.0.1. If necessary, install a supported operating system version and prepare the hardware and software on the computers.

3. Installing Kaspersky Industrial CyberSecurity for Networks 4.0.1 and getting the application partially ready for use

   At this step, you need to install components of Kaspersky Industrial CyberSecurity for Networks 4.0.1. To do so, you can perform the centralized installation procedure or install components by using the application components local installation script.

   After installing components, you need to partially prepare the application for operation by completing steps 1–4 from the description of the preparation process.

   When adding monitoring points to the same network interfaces that were used in the previous version of the application, it is recommended to name the monitoring points the same as they were named in the previous version of the application. This will let you retain the link between events and the new monitoring points when you load data from the backup (otherwise, the names of old monitoring points will be marked as deleted in events if the same names are not found in the new version).

4. Loading data from the backup after installing the new version of the application

   To load data from a previously created backup file:

   1. On the computer that performs functions of the Kaspersky Industrial CyberSecurity for Networks 4.0.1 Server, go to the folder that contains the kics4net-backup.sh script. You can go to the same folder that you opened at step 1, or you can go to the folder /opt/kaspersky/kics4net/sbin/.
   2. Enter the following command:

      sudo bash kics4net-backup.sh -r -p <path to the backup file>

      where:

      • -r is a setting that enables reading and loading of data from the backup file (required setting).
      • -p is a setting indicating the full path and name of the backup file (required setting).

      The script will begin to load data from the backup file into the application. Wait for the kics4net-backup.sh script to finish.