Check digital signatures on software packages

Before you install Deep Security, you should check the digital signature on the software ZIP packages and installer files. A correct digital signature indicates that the software is authentically from Trend Micro and hasn't been corrupted or tampered with.

You should:

You can also validate the software's checksums, as well as the security updates' and Deep Security Agent modules' digital signature. See How Deep Security validates update integrity and Linux Secure Boot support for agents.

Check the signature on software ZIP packages

The Deep Security Agent, Deep Security Virtual Appliance, and online help are made available in ZIP packages. These packages are digitally signed. You can check the digital signature on the ZIP file in the following ways:

Check the signature on installer files (EXE, MSI, RPM or DEB files)

The installers for the Deep Security Agent, Deep Security Manager, and Deep Security Notifier are digitally signed using RSA. The installer is an EXE or MSI file on Windows, an RPM file on Linux operating systems (Amazon, CloudLinux, Oracle, Red Hat, and SUSE), or a DEB file on Debian and Ubuntu.

The instructions below describe how to check a digital signature manually on an installer file. If you'd like to automate this check, you can include it in your agent deployment scripts. For more on deployment scripts, see Use deployment scripts to add and protect computers.

Follow the instructions that correspond to the type of installer file you want to check.

Check the signature on an EXE or MSI file

  1. Right-click the EXE or MSI file and select Properties.
  2. Click the Digital Signatures tab to check the signature.

Check the signature on an RPM file

Check the signature on a DEB file