CyberArk Code Sign Manager - Self-Hosted vs SignPath Foundation

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.

SignPath Foundation provides code-signing certificates to eligible open-source projects, with signing carried out through SignPath.io. For each release, SignPath.io checks that signed files are automated builds from the project’s stated source repository. Certificate private keys are generated and stored on a hardware security module. Each signing request requires a team member’s approval, and every release requires manual approval. Projects must assign author, reviewer, and approver responsibilities, while all team members must use multi-factor authentication for SignPath and repository access. Eligibility requires an actively maintained project with an existing release, an OSI-approved open-source license, and no proprietary code or malware. Supported build systems include Jenkins, GitHub, GitLab, Azure DevOps, TeamCity, and AppVeyor. Supported targets span Windows executables and scripts, MSI, CAB, AppX/MSIX, NuGet, Java archives, Android packages, RPM and Debian packages, Office macros, XML, JSON, OCI container images, ClickOnce, and other files. The free plan is free for eligible projects. Its certificate identifies SignPath Foundation as publisher, and the Foundation may decline applications.