Jenkins

Overview

QCecuring integrates with Jenkins to embed code signing and certificate operations directly into CI/CD pipelines. Build artifacts are signed with governed keys, and certificates are provisioned as part of deployment workflows without exposing private keys to build agents.

Key capabilities

• Jenkins plugin for requesting code signing operations during build pipelines.
• Secure signing without exposing private keys to Jenkins agents or build environments.
• Certificate provisioning steps for deploying TLS certificates alongside application releases.
• Approval workflows for signing operations requiring human authorization before release.
• Audit trail of all signing and certificate operations triggered from Jenkins pipelines.

Typical use cases

• Development teams signing build artifacts, containers, and packages as part of CI/CD pipelines.
• Release engineering teams requiring governed code signing with separation of duties.
• Organizations deploying applications that need fresh TLS certificates provisioned at release time.

High-level integration flow

1. Install the QCecuring Jenkins plugin and configure API credentials in Jenkins credential store.
2. Add signing or certificate provisioning steps to Jenkinsfile or pipeline configurations.
3. During builds, Jenkins requests signing operations from QCecuring without accessing private keys directly.
4. QCecuring enforces policies, performs signing, and returns signed artifacts to the pipeline.
5. All operations are logged in QCecuring’s audit trail with links to Jenkins build metadata.

CBOM Discovery

QCecuring scans Jenkins pipeline configurations for code signing certificates, TLS settings, and credential store references, adding cryptographic assets to your CBOM inventory.