CyberArk Code Sign Manager - Self-Hosted

docs.venafi.com

WebWindowsmacOSLinuxAPISelf-hosted

Spec score 7.9 #9 of 28 in Code Signing Software

What it is

CyberArk Code Sign Manager - Self-Hosted protects and governs private code signing keys managed by Trust Protection Foundation. Keys can be held in the platform’s Secret Store or on an HSM. Administrators can set restrictions based on purpose, user, and IP address, and configure whether signing requires approvals. Approval flows can have multiple levels, limited-use approvals, and expiration options; approvers receive email notifications to review requests. The system audits key use, and APIs expose event logs and signing statistics. REST APIs can request signing, manage projects and environments, set user rights, inspect logs, and approve or reject requests. Identities and groups can be added through Active Directory or an LDAP provider and assigned roles in signing projects. Clients are available for Windows, Linux, and macOS, with interfaces including CSP/KSP, PKCS#11, GPG, and macOS Keychain; .NET is listed for Windows. GPG private keys remain within Trust Protection Foundation while public keys and private-key stubs synchronize to workstations. Installation is part of a Trust Protection Foundation deployment and requires several listed components, including Certificate Lifecycle and Monitoring, Key Lifecycle and Monitoring, HSM Backend, Authentication Server, Web Console, and Web SDK. Pricing is on request.

Spec sheet

Purpose: Protects and governs use of private code signing keys managed by Trust Protection Foundation.Read 9 Oct 2026 · docs.venafi.com
Deployment: Code Signing is installed as part of a standard Trust Protection Foundation installation, with Certificate Lifecycle and Monitoring, Key Lifecycle and Monitoring, HSM Backend, Authentication Server, Web Console, and Web SDK listed as required components.Read 9 Oct 2026 · docs.venafi.com
Support: The maker says existing customers can continue to access product documentation, support, and guidance, and should use their existing support path for product-specific help.Read 9 Oct 2026 · cyberark.com
Approval workflows: Code signing flows can require no approvals or multiple approval levels before a private key is used.Read 9 Oct 2026 · docs.venafi.com
Approvals: Flows can require approval before a signing key is used, with limited-use approvals and expiration options.Read 9 Oct 2026 · docs.venafi.com
Auditing: The product supports auditing code signing key use over time and exposes APIs for monitoring the event log and signing statistics.Read 9 Oct 2026 · docs.venafi.com
Change management: Change management flows can enforce approvals for creating, updating, or deleting projects and environments.Read 9 Oct 2026 · docs.venafi.com
Client distribution: The universal client is normally downloaded from a public endpoint, and administrators can disable that endpoint and host client packages internally, including for air-gapped environments.Read 9 Oct 2026 · docs.venafi.com
Client integrations: Documented client options include CyberArk CSP for Windows, macOS Keychain, PKCS#11 on Linux, Windows, and macOS, GPG on those three platforms, and .NET on Windows.Read 9 Oct 2026 · docs.venafi.com
Client packages: Client downloads include Windows MSI and ZIP packages, macOS DMG and TGZ packages, and Linux RPM, DEB, and TGZ packages for Intel and Arm architectures.Read 9 Oct 2026 · docs.venafi.com
Client platforms: Code signing clients can be installed on Windows, Linux, or macOS.Read 9 Oct 2026 · docs.venafi.com
HSM support: The product documentation includes connecting to an HSM as an administrator task, and lists HSM Backend as a required installation component.Read 9 Oct 2026 · docs.venafi.com
Identity integration: User identities and groups can be added through Active Directory or an LDAP identity provider, then assigned roles in code signing projects.Read 9 Oct 2026 · docs.venafi.com
Installation requirements: The documented installation requires Trust Protection Foundation components including Certificate Lifecycle and Monitoring, Key Lifecycle and Monitoring, HSM Backend, Authentication Server, Web Console, and Web SDK.Read 9 Oct 2026 · docs.venafi.com
Key protection: GPG private keys can be stored in the Trust Protection Foundation secret store or on a connected HSM, and the private keys do not leave Trust Protection Foundation.Read 9 Oct 2026 · docs.venafi.com
Key storage: Code signing keys can be protected in the Trust Protection Foundation Secret Store or on an HSM.Read 9 Oct 2026 · docs.venafi.com
Key use governance: When a flow requires key use approval, the approver receives an email notification and can review the signing request before deciding whether to approve it.Read 9 Oct 2026 · docs.venafi.com
Licensing: The documentation says use of the software is subject to the terms of the active license agreement with CyberArk.Read 9 Oct 2026 · docs.venafi.com
Optional components: The installation page lists Time Stamp Service, Code Signing Key Server, and Code Signing Client Distribution as optional components.Read 9 Oct 2026 · docs.venafi.com
Private key protection: For GPG, private keys remain in Trust Protection Foundation while public keys and private-key stubs are synchronized to signing workstations.Read 9 Oct 2026 · docs.venafi.com
REST automation: REST APIs can request signing, manage projects and environments, set user rights, inspect event logs, and approve or reject key-use requests.Read 9 Oct 2026 · docs.venafi.com
Signing application integrations: The documentation provides sample integration topics for several code signing applications; the listed client interfaces include CSP/KSP, PKCS#11, GPG, and macOS Keychain.Read 9 Oct 2026 · docs.venafi.com
Signing clients: The product provides Windows CSP/KSP and PKCS#11 drivers plus a GPG SmartCard daemon, Linux PKCS#11 and GPG clients, and macOS PKCS#11, GPG, and Keychain integrations.Read 9 Oct 2026 · docs.venafi.com
Usage controls: Administrators can restrict key use by purpose, user, and IP address, and configure approval flows.Read 9 Oct 2026 · docs.venafi.com

Strong points and limits

Strong points

Key use can be restricted by user, purpose, and IP.
Approval flows can require multiple levels.
APIs expose event logs and signing statistics.
GPG private keys stay within Trust Protection Foundation.
Client options cover Windows, Linux, and macOS.

Limits

Pricing is on request.
Installation requires multiple Trust Protection Foundation components.
The documented product is self-hosted.

Who it suits

This self-hosted product suits organizations that need to govern code-signing key use across signing clients and require approval workflows, auditing, or HSM key protection. Deployment requires the listed Trust Protection Foundation components.

Verdict

Code Sign Manager offers policy controls, approvals, and auditing around private signing keys. Its required platform components and self-hosted deployment are important considerations before adoption.