- Home
- Code Signing Software
- CyberArk Code Sign Manager - Self-Hosted
CyberArk Code Sign Manager - Self-Hosted
What it is
CyberArk Code Sign Manager - Self-Hosted protects and governs private code-signing keys managed by Trust Protection Foundation. Keys can be stored in the Trust Protection Foundation Secret Store or on an HSM. Administrators can restrict use by purpose, user and IP address, configure approval levels, and set limited-use or expiring approvals. The product audits key use and exposes APIs for event logs and signing statistics. REST APIs can request signing, manage projects and environments, set rights, and approve or reject requests. Active Directory or LDAP identities can receive project roles. Clients support Windows, Linux and macOS through CSP/KSP, PKCS#11, GPG and macOS Keychain, with .NET listed for Windows. GPG private keys remain in Trust Protection Foundation while public keys and stubs synchronize to workstations. Deployment requires listed Trust Protection Foundation components, including Certificate Lifecycle and Monitoring, Key Lifecycle and Monitoring, HSM Backend, Authentication Server, Web Console and Web SDK.
For and against
For
- Stores keys in a secret store or HSM
- Rules can restrict purpose, user and IP
- Supports multi-level approval flows
- Audits key use with API access
- Clients support Windows, Linux and macOS
Against
- Installation requires multiple platform components
- Pricing is available by request
The verdict
This self-hosted product focuses on controlled key storage, approvals, auditing and cross-platform signing clients. Its deployment dependencies and governance model are central considerations for implementation.
Who it suits
It suits organizations needing self-hosted governance for code-signing keys across Windows, Linux and macOS. Teams must deploy the required Trust Protection Foundation components.
On the record
- Approvals
- Flows can require approval before a signing key is used, with limited-use approvals and expiration options.docs.venafi.com · read 9 Oct 2026
- Approval workflows
- Code signing flows can require no approvals or multiple approval levels before a private key is used.docs.venafi.com · read 9 Oct 2026
- Auditing
- The product supports auditing code signing key use over time and exposes APIs for monitoring the event log and signing statistics.docs.venafi.com · read 9 Oct 2026
- Change management
- Change management flows can enforce approvals for creating, updating, or deleting projects and environments.docs.venafi.com · read 9 Oct 2026
- 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.docs.venafi.com · read 9 Oct 2026
- 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.docs.venafi.com · read 9 Oct 2026
- 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.docs.venafi.com · read 9 Oct 2026
- Client platforms
- Code signing clients can be installed on Windows, Linux, or macOS.docs.venafi.com · read 9 Oct 2026
- 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.docs.venafi.com · read 9 Oct 2026
- HSM support
- The product documentation includes connecting to an HSM as an administrator task, and lists HSM Backend as a required installation component.docs.venafi.com · read 9 Oct 2026
- Identity integration
- User identities and groups can be added through Active Directory or an LDAP identity provider, then assigned roles in code signing projects.docs.venafi.com · read 9 Oct 2026
- 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.docs.venafi.com · read 9 Oct 2026
- 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.docs.venafi.com · read 9 Oct 2026
- Key storage
- Code signing keys can be protected in the Trust Protection Foundation Secret Store or on an HSM.docs.venafi.com · read 9 Oct 2026
- 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.docs.venafi.com · read 9 Oct 2026
- Licensing
- The documentation says use of the software is subject to the terms of the active license agreement with CyberArk.docs.venafi.com · read 9 Oct 2026
- Optional components
- The installation page lists Time Stamp Service, Code Signing Key Server, and Code Signing Client Distribution as optional components.docs.venafi.com · read 9 Oct 2026
- Private key protection
- For GPG, private keys remain in Trust Protection Foundation while public keys and private-key stubs are synchronized to signing workstations.docs.venafi.com · read 9 Oct 2026
