Using Docker Plugins to Embed the Community Attestation Service (cas) into your Docker CLI

If you’re not securing your container images and generating SBOMs (Software Bill of Materials) on a daily basis, you should definitely start. If you’d like to get start easily we offer an open source and free service to the community called CAS, the Community Attestation Service. Once you start securing your images, you’ll probably want to have a shortcut to notarize (aka sign) and authenticate (aka verify) your container. Here’s how you can accomplish that easy via Docker plugins to create a shortcut within the Docker CLI.

Let’s take the WordPress container image as an example – Let’s say we want to set shortcuts like the commands below that link to the Codenotary Attestation Service and the Docker’s CLI:

docker notarize wordpress # notarize the container image using your account (add trust)
docker notarizebom wordpress # notarize the container image and SBOM using your account
docker untrust wordpress # remove trust from the container image using your account
docker auth wordpress # verify the container image trust based on your account

Luckily you can integrate any kind of Shell script into the Docker CLI as a plugin to enhance the functionality.

You can find some sample code in this repository does the job for you:

Make sure you have a Community Attestation Service account and the cas binary in your path.

  1. Register:
  2. Download binary:
  3. Login into cas: export CAS_API_KEY=<YOURAPIKEY>; cas login

Then just run the following command on your Docker machine (tested on Linux and macOS) to download the scripts into your Docker CLI plugin folder:

mkdir -p ~/.docker/cli-plugins
for cmd in docker-auth docker-authbom docker-notarize docker-notarizebom docker-untrust; do
    curl$cmd \
        -o ~/.docker/cli-plugins/$cmd && \
        chmod +x ~/.docker/cli-plugins/$cmd

The Docker CLI automatically detects the new plugins and you can run the docker auth or docker notarize commands, adding the container image of your choice.


make sure to log into cas before using the plugins

export CAS_API_KEY=<your API_KEY>
cas login

Trust the wordpress container image

docker notarize wordpress

Trust the wordpress container image and its dependencies

docker notarizebom wordpress

Untrust the wordpress container image

docker untrust wordpress

Authenticate the wordpress container image

docker auth wordpress

CNIL Metrics & Logs

Self-Hosted performance monitoring and compliant log analysis for VMware vSphere, container and much more.


Built on the fastest immutable ledger technology. Open Source and easy to use and integrate into existing application.

Codenotary Cloud

Trusted CI/CD, SBOM and artifact
protection with cryptographic proof.
One CLI to manage all.

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.