CyberArk Code Sign Manager - Self-Hosted
docs.venafi.com
- Windows
- macOS
- Linux
- Web
- API
- Self-hosted
What CyberArk Code Sign Manager - Self-Hosted is
CyberArk Code Sign Manager - Self-Hosted governs how private code-signing keys managed by Trust Protection Foundation are used. Keys can stay in the platform’s Secret Store or on a connected HSM. Administrators can set limits based on purpose, user, and IP address, and require one or multiple approvals before signing. Approval rules can include limited use and expiration; approvers receive email notifications and can review requests. The product records key use over time, with APIs for event logs and signing statistics. REST APIs also support signing requests, project and environment management, user rights, and approval decisions. Client options cover Windows, Linux, and macOS, 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 sync to signing workstations. Installation requires several Trust Protection Foundation components, including Certificate Lifecycle and Monitoring, Key Lifecycle and Monitoring, HSM Backend, Authentication Server, Web Console, and Web SDK. Pricing is on request.
Who it suits
It suits organizations that need centrally governed signing keys, approval flows, and audit visibility. Teams using Windows, Linux, or macOS clients can choose among the documented signing interfaces.
Good to know, and what to watch
- Restricts key use by purpose, user, and IP address
- Supports limited-use and expiring approvals
- APIs expose event logs and signing statistics
- GPG private keys remain within Trust Protection Foundation
- Requires multiple Trust Protection Foundation components
- Pricing is available on request
- No cloud signing
The verdict
CyberArk Code Sign Manager - Self-Hosted combines key-use controls, approval workflows, and audit APIs within a Trust Protection Foundation deployment. Its documented installation requirements and self-hosted model are important considerations for teams evaluating it.
What the maker publishes
- Approvals
- Flows can require approval before a signing key is used, with limited-use approvals and expiration options. source
- Approval workflows
- Code signing flows can require no approvals or multiple approval levels before a private key is used. source
- Auditing
- The product supports auditing code signing key use over time and exposes APIs for monitoring the event log and signing statistics. source
- Change management
- Change management flows can enforce approvals for creating, updating, or deleting projects and environments. source
- 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. source
- 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. source
- 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. source
- Client platforms
- Code signing clients can be installed on Windows, Linux, or macOS. source
- 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. source
- HSM support
- The product documentation includes connecting to an HSM as an administrator task, and lists HSM Backend as a required installation component. source
- Identity integration
- User identities and groups can be added through Active Directory or an LDAP identity provider, then assigned roles in code signing projects. source
- 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. source
- 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. source
- Key storage
- Code signing keys can be protected in the Trust Protection Foundation Secret Store or on an HSM. source
- 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. source
- Licensing
- The documentation says use of the software is subject to the terms of the active license agreement with CyberArk. source
- Optional components
- The installation page lists Time Stamp Service, Code Signing Key Server, and Code Signing Client Distribution as optional components. source
- Private key protection
- For GPG, private keys remain in Trust Protection Foundation while public keys and private-key stubs are synchronized to signing workstations. source
- Purpose
- Protects and governs use of private code signing keys managed by Trust Protection Foundation. source
- REST automation
- REST APIs can request signing, manage projects and environments, set user rights, inspect event logs, and approve or reject key-use requests. source
- 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. source
- 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. source
- 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. source
- Usage controls
- Administrators can restrict key use by purpose, user, and IP address, and configure approval flows. source
Checked against the maker's pages on 9 Oct 2026.