Upgrading or updating the AppScan 360° platform

You can update or upgrade AppScan 360° in it's entirety, or specific components, with or without migrating data:
Note: The upgrade procedure is the same for a single VM installation of AppScan 360° or a distributed installation.

Update the current version

To update the installation with a new configuration:
  1. Update the singular-singular.clusterKit.properties file. See Preparing the configuration file for file parameters.
  2. From the folder location that contains the extracted kit, type:
    ./setup.sh $PWD/..

Upgrade to a new version of AppScan 360° without migrating data

Perform an upgrade only when there are no active scans running.

To upgrade to AppScan 360° version 1.2 from version 1.1.x or earlier without migrating data, follow the instructions in:
  1. Setting up the AppScan 360° distributed environment
  2. Preparing the configuration file
  3. Installing the platform and ASRA together

Upgrade to a new version of AppScan 360° and migrate data

To upgrade AppScan 360° version 1.2 or later to a newer version:

Data is migrated automatically.

  1. Make a backup of singular-singular.clusterKit.properties if you want to maintain the same configuration.
  2. Download the new AppScan 360° installation package from MyHCLSoftware.
  3. Install AppScan 360° as described in Installing the platform and ASRA together.
    Note: When upgrading the installation, use --target <newfolder>. Upon upgrading successfully, delete previous installation folders to free up space.

    When it's complete you receive confirmation that the AppScan 360° update is installed and ready to use.

Upgrading AppScan Remediation Advisories only

To upgrade the AppScan Remediation Advisories only:
  1. Download the new AppScan 360° installation package from MyHCLSoftware.
  2. Provide executable permission to the installer by running 
    chmod +x <PATH-OF-INSTALLER/APPSEC-INSTALLER-FILENAME>
  3. Run the installation file, specifying registry information in the command line.
    For example:
    AppScan360_v1.6.0_ASRA.run -- [registry information] -f  ~/.docker/config.json
    You can specify registry information in one of three ways:
    • Directly. For example:
      ./AppScan360_v1.6.0_ASRA.run -- -server <registry[:port]> -f  ~/.docker/config.json

      This method pushes the AppScan Remediation Advisories image to the registry and installs Helm. It does not attempt to create a secret, but verifies that a secret is available in the cluster.

    • From the configuration file specified during ASCP installation. For example:
      ./AppScan360_v1.6.0_ASRA.run -- -config <singular-singular.clusterKit.properties> -f  ~/.docker/config.json

      The method pushes the AppScan Remediation Advisories image to the registry and installs Helm, and creates or replaces the secret.

    • From a separate configuration file. For example:
      ./AppScan360_v1.6.0_ASRA.run -- -file <docker_config_file> -f  ~/.docker/config.json

      This method The method pushes the AppScan Remediation Advisories image to the registry and installs Helm, uses the config file as input to create a secret.yaml file for Helm, and removes any existing secret in the cluster.

      If you choose to use a separate configuration file, the file must contain the following information:

      • CK_DOCKER_REGISTRY_ADDRESS=<registry[:port]>

      • CK_DOCKER_REGISTRY_USERNAME=<username>

      • CK_DOCKER_REGISTRY_PASSWORD=<password>

  4. When installation is complete, you see an appropriate message:

Upgrading or rolling back AppScan 360° using Helm

To upgrade AppScan 360° to a new version using Helm:
  • From inside the cloned repository, run:
    git pull
To rollback to a previous version of the installation:
  1. Review available versions:
    helm history <release-name> -n <namespace>
    Where <release-name> and <namespace> refer to AppScan 360° components and their relative locations in the repository:
    • AppScan Central Platform
      • <release-name>: appscan360-ascp
      • <namespace>: hcl-appscan-ascp
    • AppScan Remediation Advisories
      • <release-name>: asra
      • <namespace>: hcl-asra
  2. Specify the version to which to rollback:
    helm rollback <release-name> <revision-number> -n <namespace>