CyberArk Code Sign Manager - Self-Hosted
6.0#15 in code signing softwareWebAPILinuxmacOS
VisitCyberArk Code Sign Manager - Self-Hosted vs SignPath
What both publish
| Fact | CyberArk Code Sign Manager - Self-Hosted | SignPath |
|---|---|---|
| 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. | SignPath describes its deployment options as SaaS, self-hosted, or hybrid. |
| 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. | Private keys remain in SignPath-managed or customer-managed HSMs; the architecture page states FIPS 140-2 Level 3 compliance. |
| Purpose | Protects and governs use of private code signing keys managed by Trust Protection Foundation. | SignPath provides code signing and software integrity tools that enforce policies across software builds and releases. |
CyberArk Code Sign Manager - Self-Hosted plans
No prices published.
SignPath plans
- Open Source Code SigningFree
- Code GovernancePriced on request
- Software Integrity PlatformPriced on request
Pick CyberArk Code Sign Manager - Self-Hosted if…
It suits organizations that need to govern private code-signing key use with access restrictions, approvals, and auditing. It is also relevant to teams signing through Windows, Linux, or macOS clients within a Trust Protection Foundation deployment.
Pick SignPath if…
SignPath suits development teams that need controls around signing and verifying software releases. Its free option is for qualifying open source projects; deployment choices also include self-hosted and hybrid.