Last week’s attack affects hundreds of thousands of accounts and exposes their containers to malicious code. We at CodeNotary publish open source software too and wanted to make sure our containers were unaffected.

Here’s how we did it:

Verify Container Authenticity and Integrity

      1. Create a free CodeNotary account
      2. Sign the local copy of your Docker container image:

        vcn sign docker://hello-world

      3. Download your container image from

        docker pull hello-world

      4. Ensure the container image you pulled from has been signed with CodeNotary:

        vcn verify docker://hello-world

        If the output looks like the following, you can be sure that your code has not been tampered with:

        user@opa50:~$ vcn v docker://zerotrust/parity
        Asset: docker://7d2d42157acdabf4ae46a4815af9037179c871a3b20df628c997af5d452bd7ff
        Hash: 7d2d42157acdabf4ae46a4815af9037179c871a3b20df628c997af5d452bd7ff
        Date: 2019-05-01 14:00:35 +0000 UTC
        Key: 0x2a4d3071a9d12e3886d43890d0dbaa8be60febec
        Name: docker://7d2d42157acdabf4ae46a4815af9037179c871a3b20df628c997af5d452bd7ff
        Size: 270 MB
        Company: vChain, Inc.
        Level: 2 – SOCIAL_VERIFIED
        Status: "TRUSTED"

Enable Continuous Container Integrity Monitoring with the vcn-watchdog

Moreover, to avoid the risk of leaking any malware-injected software to our users and customers, we built a continuous integrity verification monitoring tool for our containers. The sidecar vcn-watchdog, we released on GitHub as an open source project constantly protects from unwanted, infected Docker container /images/blog.

Integrated with Docker, the watchdog continuously checks the container’s integrity against its known, CodeNotary-signed image. If a container fails the verification check, an alert is sent to, in our case, our Slack account.

This is how you can quickly enable continuous integrity monitoring for your containers:

      1. Sign your locally stored container with CodeNotary:

        vcn sign docker://ImageId

      2. Check out on your server. The tool continuously verifies the integrity of your containers:

        git clone

      3. Edit the verify file and set the alerting/monitoring tool you are using (see the following instructions)
      4. Make sure /var/run/docker.sock is accessible
      5. Run with the following command on your server

        docker-compose build && docker-compose up

To modify the verify file, hook up your alerting tool into the err() function. If you use Slack as we do, please do the following:

      1. Create a Slack Bot (Slack documentation here)
      2. Use the following code:

        function err() {
           echo "Container ${1} (${2}) verification failed" >&2
           curl -q -X POST
               -H ‘Content-type: application/json’
               –data "{"text":"Container ${1} (${2}) verification failed"}"
        "$TOKEN/$KEY" > /dev/null 2>&1}

Once the set up is complete, if the verification fails, you will see the below message pop up in your Slack Bot notifications:

Slack Bot-CodeNotary-Docker Sync Alert Example

Your container has been verified and is safe if you do not see the alert message.

If you prefer to complicate your life and execute 13 time-consuming, manual steps every time you suspect you have been hacked, Madhuakula outlined a step-by-step guide for coders who prefer that route. However, most don’t as Joona Hoikkala tweeted recently.

Twitter Post

Start using vcn-watchdog, create your CodeNotary account today:


Start Your Free Account

Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

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


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.