free-continuous-integrity-verification-of-your-docker-containers

 

Docker Container Tetris

 

In our last blog (here), we showed how to sign and verify your build code. With an established baseline, we’ll move on to the really cool stuff that will make your life a whole lot easier. Below are the few, simple steps you can take to get next level, free continuous integrity verification of your Docker containers. This way as a developer anytime you execute a Docker run command for any over your numerous containers, you can be sure your code is 100% safe the way you intended it to be.

 

VCN Watchdog for Container Protection

 

We developed VCN Watchdog so you can maintain continuous verification of your Docker runtime environment. Watchdog continuously monitors your environment in order to prevent unknown and/or compromised containers from being executed.

 

How to use VCN Watchdog

 

One of the great things about VCN Watchdog is it can monitor any functionality you want and alert you accordingly.

 

Check out the project and edit the verify file by customizing your monitoring alerts to whatever you want.

 

You will need to make sure your /var/run/docker.sock is accessible.

 

Then run this on your server:

 

 

docker-compose build && docker-compose up -d

And you are good to go.

 

Design of VCN Watchdog

 

This tool is designed as a sidecar for your existing Docker runtime environment. All running containers are continuously checked via CodeNotary vcn for integrity. If a container fails the verification check, then a customizable alert is triggered and you will be notified.

 

Conclusion

 

That’s it. Now you know how to get free continuous integrity verification of your Docker containers. It really is that simple.

 

Thanks to the innovative use of blockchain and smart contract technology, you now can iterate faster, more securely and at lower costs. Gaining immutable integrity using the CodeNotary vcn tool saves you from a lot of headaches and remediation costs. Additional ways CodeNotary benefits you include:

  • Increased Customer Confidence
  • Increased Productivity/Less Remediation
  • Never Before Available Customer Insights

 

See how you can protect your Docker builds continuously with CodeNotary by clicking below to start your free trial. And bonus, it’s free for OSS and non-commercial users.

 

Sign Me Up!

CNIL
Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud
PERFORMANCE MONITORING, LOG ANALYSIS, LICENSE COMPLIANCE!

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

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.