Code Signing Key Management Server (CSKMS)
5.4#22 in code signing softwareAPISelf-hosted
Visit
| Fact | Code Signing Key Management Server (CSKMS) | SignPath |
|---|---|---|
| Access controls | Signing keys can be administered using key groups and user permissions, with M-of-N hardware tokens for administration and control. | Role-based access controls define who can sign which artifacts, when, and with which certificate. |
| Deployment | It can run offline in an isolated security bunker, where security officers present tokens to access restricted project keys, or connect through secure web services for automated signing. | SignPath describes its deployment options as SaaS, self-hosted, or hybrid. |
| Founded | 1985 | 2017 |
| Integrations | It provides a RESTful API for code-signing clients and offers custom integration services. | The company lists plugins and REST API integrations for GitHub Actions, GitLab, Jenkins, Azure DevOps, and TeamCity. |
| Key protection | The datasheet says keys are protected in a FIPS 140-2 Level 3 physical HSM. | Private keys remain in SignPath-managed or customer-managed HSMs; the architecture page states FIPS 140-2 Level 3 compliance. |
| Purpose | CSKMS manages access to code-signing and encryption keys, signs software images, and can optionally encrypt them for target projects. | SignPath provides code signing and software integrity tools that enforce policies across software builds and releases. |
No prices published.
CSKMS is intended for IC manufacturers and OEMs that sign and secure device software. It also fits teams needing controlled firmware or application signing in self-hosted environments.
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.