Upgrading from a previous version

Upgrading from a previous version on Unix-based deployments

Preliminary notes

Upgrading is usually a two-step process:

  1. upgrade the mdssc package by installing the newer package

  2. upgrade the existing code by downloading new images

Notes for upgrading to 4.1 and later

When upgrading from 4.0.x behind a TLS-terminating load balancer, set ALLOWED_ORIGINS. Otherwise, the Cross Domain Transfer Activity Log stops loading.

Notes for upgrading to 4.2 and later

Cross Domain Transfer import scan settings

In 4.2, the High Side sets the import scan on each connection mapping, not in High Side Setup. The upgrade copies your 4.1 settings to each mapping:

  • Scan Before Import keeps its 4.1 value. If it was never set, it is on after the upgrade.

  • Workflow keeps the 4.1 scan workflow. If none was set, the mapping uses the Default Workflow.

The 4.1 Maximum Allowed Severity and Block transfer if secrets are found settings are removed. To block vulnerabilities and secrets, set the Blocked File Definition of the mapping's workflow.

After the upgrade, open each mapping on the High Side and check its import scan settings. For details, see Cross Domain Transfer.

API keys

In 4.2, each user has one API key. Existing API keys continue to work after the upgrade. When a user saves a new API key, MDSSC deletes that user's other keys.

After you save a new API key, update every place that uses the old key:

  • the webhooks in your service providers

  • the Authorization Token in the Low Side setup of Cross Domain Transfer

For details, see Configuring an API Key.

Acquire the installer package

In order to acquire the new package please visit My OPSWAT -> Product Downloads

Debian / Ubuntu package (.deb)

  1. Update your packages

sudo apt-get update

  1. Move to the folder containing the installer and install it

sudo dpkg -i <name of the file>.deb || sudo apt-get install -f

  1. Start the service

sudo mdssc -u update

  1. Optionally, you can check the status using the following command:

sudo mdssc -c status

  1. Open a browser and navigate to the web interface: http://<server> to configure your deployment

Red Hat Enterprise Linux / CentOS package (.rpm)

  1. Update your packages

sudo yum -y update

  1. Move to the folder containing the installer and install it

sudo yum upgrade <name of the file>.rpm
Warning

If yum fails with Cannot download repomd.xml, run the upgrade with all repositories disabled:

sudo yum upgrade -y --disablerepo="*" ./mdssc-<version>.noarch.rpm

  1. Start the service

sudo mdssc -u update

  1. Optionally, you can check the status using the following command:

sudo mdssc -c status

  1. Open a browser and navigate to the web interface: http://<server> to configure your deployment


Next to read:
Kubernetes deployment
On This Page
Upgrading from a previous versionUpgrading from a previous version on Unix-based deploymentsPreliminary notesNotes for upgrading to 4.1 and laterNotes for upgrading to 4.2 and laterAcquire the installer packageDebian / Ubuntu package (.deb)Red Hat Enterprise Linux / CentOS package (.rpm)Cross Domain Transfer import scan settingsAPI keys