Skip to content

Cybersecurity🔗

At MVTec, we prioritize product quality and customer benefit. Our software is developed by highly skilled engineers at our headquarters in Munich, following industry best practices and stringent guidelines.

We are committed to ensuring that our software:

  • Retains recognized industry standards and regulatory requirements.
  • Is designed and tested to be free from known vulnerabilities and backdoors.
  • Is continuously monitored and updated to address emerging security threats.
  • Provides all necessary documentation for full transparency on third-party components and dependencies

All transmitted data complies with the General Data Protection Regulation (GDPR) and our data privacy guidelines. In no case any personal data is transmitted to MVTec.

You can find relevant changes in the release notes.

Security contact🔗

If you have any security-related questions or concerns, please contact us at security@mvtec.com. Your request will be processed with care and discretion.

For more information and further contact options, please refer to the MVTec homepage at www.mvtec.com/cybersecurity.

Required login🔗

To be able to download MVTec programs via the Software Manager, a “MVLogin” account on the MVTec website is required. For more information, see also Using the Software Manager > Login.

The login is only required for the download, not for the installation of packages, and is secured following industry best practices.

Verifying the software🔗

When installing MVTec software via the Software Manager (including the Software Manager itself) from the MVTec website, the integrity of the downloaded software packages is automatically verified.
On Windows, we recommend verifying that the signature of the SOM executable is valid.

To ensure a valid signature (Windows only):

  1. Navigate to the folder containing the file som.exe.
  2. Open the context menu of som.exe and select Properties.
  3. Select the Digital Signatures tab.
  4. Double-click one of the “MVTec Software GmbH” entries in the list.
    ⤷ Only continue using SOM if the dialog shows “This signature is OK.”

You can additionally verify the checksum to ensure the integrity of the downloaded software. You find the checksums of the corresponding products under https://www.mvtec.com/downloads/.

To verify the checksum of a downloaded file, you can use the following command:

sha512sum -c <downloaded checksum file>

certutil -hashfile <downloaded installation file> sha512
Verify that the shown hash value is identical to that in the downloaded checksum file.

Unlocking the SOM frontend🔗

The communication between front- and backend of the Software Manager is secured by default, and only a frontend that has been unlocked can communicate with the backend.

Unlocking the frontend requires one of the following events:

  • It is opened by the Software Manager itself.
  • It is opened via the tray icon.
  • An unlock token is provided as part of the URL, for example:
    http://localhost:8188?token=lBGu-ogqHOOSZ7Tj
  • An unlock token is entered via the login form of the frontend.

An unlock token is shown on the console output of the Software Manager during startup, or can be copied to clipboard from the tray icon menu.

As an alternative to the unlock tokens, you can set a password to be used instead of an unlock token in the login form.
To set a password for the frontend, do one of the following:

  • To set a password temporarily, use the command line option --password.
  • To permanently store a password, either
    • use the command som config server.password <password>,
    • manually change the som.config file, or
    • enter the password in the settings dialog of the frontend.

The Software Manager only saves a hash of the password, so you will not be able to retrieve the password in plaintext should you lose it. However, you can always set a new password using one of the methods mentioned above.