Solutions >For Security Teams
Background lines
Dotted background
Enforce end-to-end artifact provenance, signing, and integrity

Security-First Release Management

Automatically validate artifacts against security policies to prevent unverified releases

Security-First Release Management architecture diagram

The Challenge

Supply chain attacks are increasingly common, and AI-generated code may often drastically increase the attack surfaces. In theory, release management works as a checkpoint to ensure that only verified, compliant artifacts are promoted to production. In reality, time and business pressures often take precedence.

Security scans can be time-consuming, and even false positives require thorough investigation, slowing down the release process. Vulnerability analysis and testing tools may not be perfectly integrated with DevOps pipelines, requiring separate data aggregation and analysis. Policies may be ambiguous or enforced incorrectly, allowing unverified artifacts to enter build pipelines.

The Chainloop Solution

Chainloop takes a “security-first” approach to release management, enforcing end-to-end artifact provenance, signing, and integrity. It automatically captures and connects key evidence for every release artifact, including SBOMs, security scan results, code coverage checks, and other metadata.

It uses this metadata to automatically validate artifacts against pre-defined security policies, preventing the use of unverified or dangerous components. Acceptances, rejections, and exceptions are logged for every artifact and step in the release pipeline.

Security-First Release Management dashboard screenshot
Key Benefits

Why Choose This Solution

Early risk detection

Early detection and mitigation of security risks

Improved security posture

Improved security posture across release management workflows

Detailed audit logs

Detailed logs for audit reporting and root cause analysis

Automated checks

Automated, real-time security checks based on internal requirements and external standards

Powered By These Features

Explore our platform

Digital Signing and PKI Integration

Chainloop uses digital signatures with the in-toto framework to protect artifacts and metadata, ensuring a tamper-proof, SLSA-compliant, and verifiable audit trail. Chainloop supports multiple signing methods, including keyed, keyless and custom PKI options.

Signing keys can be sourced from SigStore Cosign, KMS services, PKCS#11, or Kubernetes/GitLab secrets. Chainloop also provides integrations with enterprise PKI solutions like EJBCA and SignServer.

Observability, Monitoring and Alerts

Chainloop provides a dedicated endpoint for Prometheus instances to fetch metrics, such as the status of the last run and its duration. By combining this Prometheus endpoint with Grafana or other visualization tools, Chainloop makes it possible to create graphs, dashboards and alerts for CI/CD workflows automatically and in a standardized way.

Chainloop also comes with ready-made integrations for notifications in email, Slack, and Discord. These features enable operators to gain real-time insights into their software delivery workflows, and identify and track patterns over time.

Curated Library of Policies-as-Code

Chainloop provides a curated set of policies tailored to common compliance controls, such as SBOM sanity checks, artifact signature verification, license checks, code quality and coverage checks, CVE scans, and many more. Both built-in policies and custom policies are supported.

The results of policy evaluations are stored in Chainloop’s evidence store and can be queried through the user interface. Policies are written in Rego and can be used to evaluate individual materials or the whole attestation document.

Policies are also reusable: this enables security, compliance and legal teams to define global rules (for example, “no GPL dependencies”) and have them enforced consistently across different products.

Declarative, Immutable Workflow Contracts

Chainloop enables Dev, Sec, and Ops teams to create declarative contracts requiring one or more pieces of evidence (e.g. artifacts, SBOMs, reports) to be attached during the SDLC lifecycle. Contracts connect evidence with policies, and Chainloop uses these contracts to verify provenance and integrity before any release reaches production.

These contracts are immutable, eliminating ambiguity in decision-making and setting a foundation for mutual trust and transparency between teams. Contracts can be applied to multiple workflows, making it easy to reuse and update them across teams and products.

Ready to Get Started?

See how Chainloop can transform your software delivery workflow