Change to code signing certificate
From version 6.0.1320 or later
 

Following a recent change to our code signing certificate, some security tools may temporarily flag our executables as untrustworthy.

We recently updated our code signing certificate to reflect our new identity, transitioning from DAZZM to octopus-itsm.com.

This change may trigger warnings from certain security tools, including Microsoft Defender SmartScreen, which may block the setup file (setup.exe) indicating it is not commonly downloaded. After contacting Microsoft, this behavior was confirmed to be normal, as reputation for a new certificate takes time to build.

We confirm that the installation file has been digitally signed in accordance with best practices, using a valid certificate issued in the name of Octopus-ITSM.com Inc.

Recommendation
We encourage users to follow their internal security validation processes and consult with their IT teams before running the installer, in accordance with their organization’s standard procedures.

Thank you for your understanding during this transition period.

Here are the messages that appear when the problem occurs: