codenotary-product-update-july-2019

 

CodeNotary - Product Update July 2019.v2

 

It’s finally time for a new CodeNotary product update again. The update includes organizational management and signing features, CodeNotary for Kubernetes suite add-on – Kube-Notary: a K8s watchdog, and the JVCN for Maven plugin and JSVCN for JavaScript package.

 

What’s New in CodeNotary

  • Organization management:
    • Ability to create an organization and add users to it from the dashboard
    • Ability to sign assets in the organization’s name
    • Ability to verify an asset based on an organization
  • CodeNotary for Kubernetes:
    • Kube-notary: a Kubernetes watchdog to continuously monitor Kubernetes cluster at runtime and notify when unknown or untrusted container /images/blog
      • CodeNotary created Grafana dashboard
      • Verification metrics exporter for Prometheus
  • JVCN: the Maven plugin allows for the verification of dependency integrity during builds
  • JSVCN: the JavaScript package allows for the verification of a digital asset’s integrity that is used in a web application

 

Start Using CodeNotary

 

Organizational Management

Enterprise users now can sign the digital assets their organization produces by creating an organization in the dashboard (below) for their company. New organizational team members can be directly in the dashboard as seen below as well.

CodeNotary Organizational Dashboard View

 

Verifying a Digital Asset Against an Organization

Verification of an organization’s digital asset can be done from anywhere globally, both from inside and outside of the organization. This allows for users outside of the signing organization to be sure that the indicated organization did, in fact, sign the digital asset they are seeking to use.

 

Verifying Against a Group of Signers (Keys)

Groups of signers or organizations such as several vendors like microsoft.com, redhat.com, and opvizor.com can be required to have all their signatures approved before a digital asset is okayed to be used. For example, before an asset is allowed to be used internally or passed off to another contractor, signatures from multiple responsible parties, e.g. contractors, auditors, regulators, etc., all need to sign off on an asset first.

 

More information can be found on our blog here.

 

CodeNotary for Kubernetes: Kube-Notary

kube-notary is the first add-on of the CodeNotary for Kubernetes suite. It acts as a watchdog for users’ Kubernetes environments and continuously monitors clusters at runtime, issuing instant notifications when an unknown, untrusted, or unsupported container image is found running. After deploying the service within a cluster, all pods are continuously checked by matching the hash signature of the running image to the hash that is stored immutably on the blockchain. If the hashes match, trust is verified. Containers are checked and re-verified at regular, user-specified intervals. If any containers are found that are not ‘Trusted’, kube-notary alerts you instantly.

 

Additionally, kube-notary comes with a built-in verification metrics exporter, everything can be easily visualized in a Prometheus time series database using the CodeNotary created Grafana dashboard (screenshot below).

 

Kubernetes vcn Grafana Dashboard Visual 2

 

More information can be found about kube-notary on our GitHub page here or the Grafana dashboard here.

 

JVCN

CodeNotary & Maven Integration Graphic 

The jvcn-maven plugin allows for the verification of dependency integrity during builds. Additionally, the build process can be stopped by the plugin if it encounters a non-trusted dependency.

 

More information can be found on our blog here or GitHub repo here.

 

JSVCN

The JVSCN package is an easy to use JavaScript client for the CodeNotary platform. It allows for the verification of digital assets used in web applications by connecting directly to the CodeNotary blockchain and querying asset metadata from CodeNotary. This way developers can integrate the power of the blockchain with their web apps without having to deal with the complexity of communicating with a blockchain. The package is unit tested and well designed and is a verify-subset of our vcn tool functionality. It is available on NPM here.

 

More information can be found on our blog here or GitHub repo here.

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.