Installation of OneSpan Threat View (evaluation package)

The evaluation package is for evaluation purposes only. It is a good starting point for your own deployment, but should not be used in productive environments "as is" without proper configuration.

The Threat View product package contains the necessary script in a shell file, run_threat-view.sh. Run this file to extract all the image (.tar) files and deploy Docker Compose. Once the system has completed running the script and deploying all images, Threat View is ready to be used. To access the Threat View Administration Interface, open http://localhost/adminui in an internet browser.

Prerequisites

• You have received the onespan_threat-view_version.zip file with the Threat View Evaluation Package from OneSpan, including the initial credentials for the administrator user account.

  The Threat View Evaluation Package is a self-contained zip file that is used to run the Threat View evaluation version locally, using Docker Compose. The package contains all required non-public dependencies such as Docker images for the Threat View services.

  The zip file has a size of approximately 1.5 GB, and includes subfolders for Threat View and the Event Simulator, each containing their respective docker-compose files. The images folder contains all non-public Docker images in archive format. Environment variables are stored in .env files, and each service has its own dedicated folder for specific environment and application properties files.

• Docker and Docker Compose installed

  You must install Docker Desktop and Docker Compose to be able to run the application. For more information, see the Docker Desktop and Docker Compose product documentation.

Installation recommendations

To ensure an efficient and successful installation of Threat View, we recommend the following:

• Windows

  Enable Windows Subsystem for Linux (WSL) 2 with a recent Linux version to run the shell scripts. You can then load and start the Docker containers either through the Docker Desktop GUI, or by using WSL2 to call the run_threat-view.sh and run_simulator.sh scripts.

• macOS

  Use brew install docker-compose to install Docker Compose.

  To use Threat View and (optionally) the event simulator, run the scripts with the following commands:

  • ./run_threat-view.sh

  • (optional) ./run_simulator.sh

• Ubuntu Desktop

  Use sudo snap install docker to install and enable Docker, then enable docker for non-root users. For instructions, see the Docker product documentation for Linux post-installation steps.

  To use Threat View and (optionally) the event simulator, run the scripts with the following commands:

  • ./run_threat-view.sh

  • (optional) ./run_simulator.sh

• Fedora Workstation

  Follow the instructions in the Docker product documentation. We recommend following these instructions instead of using the packages provided by Fedora. Complete the post-installation steps. For instructions, see the Docker product documentation for Linux post-installation steps.

  To use Threat View and (optionally) the event simulator, run the scripts with the following commands:

  • ./run_threat-view.sh

  • (optional) ./run_simulator.sh

• Red Hat Enterprise Linux

  Follow the instructions provided in the Docker product documentation. We recommend following these instructions instead of using the built-in Podman engine provided by Red Hat. Complete the post-installation steps. For instructions, see the Docker product documentation for Linux post-installation steps.

  To use Threat View and (optionally) the event simulator, run the scripts with the following commands:

  • ./run_threat-view.sh

  • (optional) ./run_simulator.sh

Deploy the Threat View evaluation version

Use the run_threat-view.sh script included in the product package in the base folder to run the Threat View services stack. This will load non-public docker images from the images archive folder and use docker-compose to spin up the services.

Public images like database images will be downloaded from the public docker repository.

Once all services are running, access the Threat View application in your browser at http://localhost/adminui and log in with the credentials you received from OneSpan.

Manual deployment

If you do not wish to rely on the provided shell scripts, you can also deploy the system manually.

Recommendations for manual deployment

When deploying the Docker Engine, we highly recommend the following:

• Follow the instructions provided in the Docker product documentation.

  Any default packages provided with your distribution might not be compatible with Threat View. Also, Threat View currently does not support Podman as a container engine, and we advise you to use Docker Engine instead.

• Complete the post-installation steps.

  We recommend following the Docker product documentation for Linux post-installation steps

• Run the containers as non-root.

  Otherwise, you need to run the Docker Compose steps outlined below as root or sudo.

To deploy Threat View manually

1. Unzip the downloaded archive in the location of your choice: unzip insights_<version>.zip

2. Navigate to the threat-view subfolder: cd ./threat-view_<version>/threat-view

3. Extract and load all the Docker images: for TAR in ./images/*.tar; do docker load -i "$TAR"; done

4. Run Docker Compose: docker compose up -d

5. (Optional) Run the Event Simulator.

   1. Navigate to the simulator subfolder: cd ../simulator

   2. Extract and load the images: for TAR in ./images/*.tar; do docker load -i "$TAR"; done.

6. Run Docker Compose: docker compose up -d.