A software bill of materials (SBOM) is a list of ingredients that make up software components. Therefore, it’s sometimes called a software ingredient list. Although the definition of SBOM seems simple, in practice, it’s used in a much broader context. You would use an SBOM to catalog what your project needs in order to complete …
WHAT IS AN SBOM BILL OF MATERIALS AND WHAT DOES IT DO? Read More »
While it’s great for application developers to write applications in a language that runs seamlessly on many different operating systems, there is a downside to the application’s intention. Ransomware has damaged many companies, causing downtime, money, and sleepless nights. Looking into some statistics you can find damage predictions of $265 billion by 2031. Writing Ransomware …
Rust-based Ransomware can hit anywhere including Windows, Linux and VMware ESXi Read More »
Spring4Shell is the brother from another mother of Log4j. Vulnerabilities seem to come in bunches; if you see one, you should be worried because it is a sign that there are probably related ones lurking nearby. Getting rid of Log4j was a huge challenge in late 2021 but it looks like it wasn’t a one-time …
Spring4Shell in containers, should you be worried? Read More »
Supply chain attacks are on the rise. Why are they so attractive to cybercriminals? The reason is simple. Most of the industry is not yet ready to efficiently defend against them and once successfully deployed the chances of having a big impact are high. Tampering with the software supply chain of SolarWinds affected 18,000 customers. …
Last weekend the Open Source world was shaken up a bit when a developer maintaining the highly popular libraries faker.js and colors.js sabotaged both projects by breaking their function. The supply-chain dangers from underlying open-source projects were highlighted many times in 2021, the year that ended with the Log4j disaster. But as the new year …
Detect unwanted dependencies in your software like versions of faker.js or colors.js Read More »
On December 10th 2021 the news about a discovered vulnerability in the highly popular Log4j project has shaken up the IT world (and beyond). The vulnerability is tracked as CVE-2021-44228 and allows the unauthenticated, remote code execution on any application that uses Log4j version 2.0-beta9 up to 2.14.1. This bug scores 10 out of 10, …
Apache Log4j vulnerability shows the importance of SBOMs Read More »
Introducing the SLSA framework Preserving the integrity of the code has always been a concern. However, events such as the SolarWinds hack have encouraged organizations such as the Cybersecurity and Infrastructure Security Agency (CISA) to release guidelines to minimize the risk of attacks against the software supply chain. In parallel, the open-source community and the …
Community Attestation Service guarantees the provenance of code, makes compliance with Presidential cybersecurity order fast and easy HOUSTON, October 26, 2021– The U.S. Executive Order on Improving the Nation’s Cybersecurity includes “providing a purchaser a Software Bill of Materials (SBOM) for each application.” Codenotary Community Attestation Service — the first free, open source artifact and …
Software Bill of Materials (SBOM), What It Is and Why It Is So Important Over time, having a reliable Software Bill of Materials (SBOM) has become a fundamental part of the security strategy of DevSecOps teams. Why? That’s the topic we are going to address in this article. What is an SBOM Let’s start by …
Software_Bill_of_Materials_SBoM_what_it_is_and_why_it_is_so_important 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.
