App Control: Why Agent Install Packages are not Signed?

Products

• Carbon Black App Control (formerly Cb Protection)

Issue/Introduction

Why the policy specific Agent Installer Package signed by Publisher ´Publisher: Unknown Publisher´ instead of Carbon Black or Bit9

Environment

• App Control Agent (formerly CB Protection): All Supported Versions
• Microsoft Windows: All Supported Versions

Resolution

These packages are being updated by the local server each time the CL version on the server is changed

Additional Information

The only ParityHostAgent.msi file that is actually signed, is the version that resides under C:\ProgramFiles (x86)\bit9\Parity Server\hostpkg folder (which is the App Control installation folder)