Microsoft Authenticode
This document covers the necessary information to install, configure, and integrate Microsoft Authenticode with CipherTrust KMS.
Microsoft Authenticode permits end users to identify who published a software component and verify that no one tampered with it before downloading it from the Internet. Authenticode assures end users of the identity of the software publisher and that the code has not been altered after the signature was applied, before they download signed code from the Internet.
Authenticode relies on the proven cryptographic techniques and use of one or more private keys to sign and time-stamp the published software. It is important to maintain the confidentiality of these keys. The CipherTrust KMS integrates with Microsoft Authenticode to provide a trusted system for protecting the organizational credentials of the software publisher.
Note
CipherTrust KMS refers to one of the Key Management Servers, that is, CipherTrust Manager or KeySecure.
Supported Product Versions
This integration is validated on the following operating system variants:
Windows
Windows Server 2008
Windows Server 2012 Standard
Windows Server 2012 R2
CipherTrust KMS
- KeySecure 8.4.3 or higher
CipherTrust Manager
- CipherTrust Manager 1.5 or higher
CADP
- 8.4.3p01 or higher
Third Party Application Details
Microsoft Authenticode (Microsoft Windows SDK 8.1)
Microsoft Windows SDK v6.1
Microsoft Office 2003 Smart Tags SDK (Optional)
Prerequisites
Ensure that the CipherTrust Manager is installed and configured. For more details, refer to the CipherTrust Manager Documentation.
Authenticode communicates with the CipherTrust Manager using the Network Attached Encryption (NAE)-XML Interface. Ensure that the NAE-XML interface is configured. For more details, refer to the CipherTrust Manager Documentation.
Ensure that the port configured on NAE-XML interface is accessible from the Authenticode machine.
Ensure Setting up SSL.
Steps For The Integration
To integrate Authenticode with the CipherTrust Manager:
