Codenotary announces the release of a new product: Auditable Change Management (ACM). Do you observe that your company pays for licensed software much more than it could? Now with ACM you are able to cryptographically prove that you never exceeded the agreed amount of resources and software instances. Track all changes – ESXi host or virtual machine …
Bart, a core developer in our immudb team recently published a very interesting article to use GitHub Actions to automatically build and test on many different CPU architectures that are not very common and often not available. When we think about CPU architecture usually there’s one leader that comes to our mind – the famous x86-64 one. …
Multi-CPU Github Actions with Go for automatic builds and tests Read More »
Learn how to reuse code in continuous integration pipelines with our digital assets attestation tool If you need to use the same piece of code in many different pipelines, a Jenkins shared library is a good approach. After importing it, you will have access to its methods, which is a convenient way of avoiding repetition …
A Jenkins shared library to execute commands with vcn, our CLI tool Read More »
Simple uptime monitoring for Internet-of-Things (IoT) is well-known and requires knowing if the devices are up and running. Having additional long-term performance data, secure (tamper-proof) logging at your Edge devices is only a tiny step when using Metrics & Logs. With our support for device, infrastructure, and application metrics as well as Syslog data, you …
Metrics & Logs support for IoT – Bringing Secure Monitoring and Logging to the Edge Read More »
Recently, we at Codenotary released a new version of a GitHub Action that can be used to download our enterprise CLI tool vcn and execute commands with it. Available on GitHub’s marketplace, it can be implemented by our customers in GitHub Action continuous integration pipelines to notarize and authenticate digital assets as part of an …
A GitHub Action to download and use our enterprise tool vcn in CI Read More »
Many thanks to Andrew Kane for maintaining the Ruby SDK for immudb! https://ankane.org/ You can find the Sources here: https://github.com/ankane/immudb-ruby and the Gem here: https://rubygems.org/gems/immudb Installation Add this line to your application’s Gemfile: gem “immudb” Getting Started Create a client immudb = Immudb::Client.new All of these options are supported Immudb::Client.new( host: “localhost”, port: 3322, username: …
Last weekend was all about releasing fixes for a major (critical) Confluence server vulnerability, tracked by CVE-2022-26134, that allows an unauthenticated attacker to execute arbitrary code (remote code execution, RCE). You should be very aware of that vulnerability as Confluence servers are a very attractive target for initial access to a corporate network. Therefore, systems …
Serious security vulnerabilities in Atlassian Confluence affect many organizations Read More »
Trust is a journey and not a state that lasts forever. Many customers we speak with store artifacts and container images in their private registry to keep them secure. The truth is that it is not only about vulnerabilities, but many other attributes, like licenses, existing contracts, or new versions. Therefore, the trust level can …
Release notes 1.3 We’re pleased to announce immudb version 1.3. This version brings some new notable changes, 40% higher performance and a lot of other improvements and some bug fixes. You can find the new release here for all major platforms: https://github.com/codenotary/immudb/releases/tag/v1.3.0 Regarding SDKs, please make sure to check the compatibility list: https://docs.immudb.io/master/getstarted/jumpstart.html New Support …
Verifiable revisions – immudb version 1.3 released Read More »
We are thrilled to see that CAS has been named Open-Source Project of the Week by the highly popular SD Times. Check out the article: https://sdtimes.com/security/sd-times-open-source-project-of-the-week-cas/ Community Attestation Service (CAS) is an open-source service that helps users secure their software and is powered by Codenotary’s digital identity infrastructure. The project lets them create a Software …
Community Attestation Service (CAS) named SD Times Open-Source Project of the Week Read More »
Our software prevents and mitigates damage from harmful components in your DevOps environment.
Copyright © 2021, 2022 Codenotary Inc. All rights reserved.
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.).
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.
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.
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.
No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:
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.
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.
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.
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.
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.
We will also send you the research paper
via email.
Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain.
Please enter contact information to receive an email with the free trial details.
