Month: May 2019


    In what can be seen as an ironic twist of fate, digital security firms Kaspersky and ESET reported recently how a Zombie-themed video game called ‘Infestation’ by Electronic Extreme delivered malware directly to its players. This was due to an supply chain attack on the video game developer application Microsoft Visual Studio. Electronic …

zombie-infestation-software-developer-tools-the-ms-visual-studio-attack Read More »


  The above video to use CodeNotary to sign a Docker container image. Be sure to note how the video ends with all but one container verification failing, which is exactly as it should be since only one container was signed in the demo. Risk surrounds everyone everyday. For coders, risk is especially important to …

how-codenotary-can-protect-you-from-using-compromised-container-images Read More »


    CodeNotary is the only decentralized, secure and blockchain based Kubernetes solution out there to guarantee the integrity of the containers running in a k8s cluster. In this blog, we will show you how to find and continuously monitor for unwanted Docker /images/blog in your K8s environment by using CodeNotary and its CLI tool, …

find-continuously-monitor-your-kubernetes-environment-for-unwanted-docker-images Read More »


    There are numerous security measures a developer can perform but nearly half (48%) of all developers say they don’t have enough time to do so. They know security is important but with an often demanding schedule they end up concentrating on developing for functionality instead of security. This kind of thought process can …

security-with-what-time-my-continuous-integration-backlog-is-overflowing Read More »


You might have noticed that we, at Opvizor, consistently improve the container support of Performance Analyzer. No matter if you’re running docker container on Docker hosts or you’re using Kubernetes. As we already have one of the most detailed and complete VMware monitoring stack in the industry, especially the Kubernetes monitoring part comes in very …

performance-analyzer-for-kubernetes-on-vsphere Read More »


    Blockchain is such a new innovation that holds unknown potential, it’s still very much a journey and not a destination. New discoveries are constantly being made with the technology and that challenges our economic fitness. Along with the specter of the groundbreaking value of blockchain, comes new market opportunities. However, as with any …

dos-and-donts-in-ethereum-parity-aura-genesis Read More »


This is the third blog of the series and hopefully the last one as I am confident to have gone through all the requirements, issues and limitations of the current code signing process. ‘Code Signing Certificates’ Journey of Pain #3: When Even Signing Isn’t Enough’ shines a light on the extortion by the certificate authority …

code-signing-certificates-journey-of-pain-3-when-even-signing-isnt-enough Read More »

Use Case - Tamper-resistant Clinical Trials


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.

Use Case - Finance


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.

Use Case - eCommerce and NFT marketplace


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, …)


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


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.

Use Case - DevOps Evidence


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.

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.

Subscribe to our newsletter