Codenotary and the SLSA Framework

Codenotary is leading the way in safeguarding against software supply chain attacks–an ever-present threat, where vulnerable artifacts can be introduced at several points.

SolarWinds and other hacks have encouraged organizations, like CISA, to release guidelines to minimize the risk of such attacks and develop an industry-wide solution jointly with the commercial and open source communities.
Enter the SLSA framework – a systematic guideline preventing the introduction of problem artifacts.

SLSA levels are a common language describing how secure software supply chains and their components truly are.

SLSA 1. The most basic level that can provide risk managers with a high-level view of the origin of artifacts, a.k.a.  Provenance Checks.

SLSA 2. This level requires an immutable reference that points to each change in the repository, making it difficult for an attacker to modify the software, to the point that the build service can be considered safe.

SLSA 3.  An extension of SLSA 2. The source and build platforms must meet stricter security standards that guarantee a more reliable and detailed source audit, preventing sophisticated attacks such as cross-build contamination.

SLSA 4. The maximum level of protection. In addition to meeting all the requirements of the previous levels, SLSA 4 consists of a two-person review of all changes as well as reproducibility of the build process. Common to all levels is an unlimited retention of code changes and an immutable history of changes.

Implementing SLSA does not have to be a daunting task. Codenotary enables compliance with all SLSA levels, offering a platform which notarize artifacts, assigns them a unique identity and stores the results within an innovative cryptographically-verifiable immutable ledger, immudb, that guarantees a trusted supply chain with a tamperproof provenance SBOM.

This way our customers can be sure that the programs, code, libraries and container images are truly the ONLY ones included.

Codenotary Cloud – Protecting artifacts across your software supply chain. For more information, please contact us.

CNIL Metrics & Logs

Self-Hosted performance monitoring and compliant log analysis for VMware vSphere, container and much more.

immudb

Built on the fastest immutable ledger technology. Open Source and easy to use and integrate into existing application.

Codenotary Cloud

Trusted CI/CD, SBOM and artifact
protection with cryptographic proof.
One CLI to manage all.

MOST POPULAR

Sorry. No data so far.

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.