home-assistant-builds-on-codenotary

Houston, May 25 2021 – CodeNotary Inc., the leading provider of zero trust protection for DevOps, brings digital trust, integrity, and transparency to the de-facto standard for home automation software Home Assistant.

Software supply chain attacks have already affected many of the largest companies in the world. The SolarWinds
attack
contaminating more than 18,000 customers is just one of many recent such exposures, and more come to light every month, such as the one for the web development language
PHP
.

Recent incidents have clearly shown that many companies and projects face an exceptional challenge when attempting to secure their software supply chain using traditional and insufficient technologies like
digital certificates.

CodeNotary Inc. developed the open-source database immudb as the core technology to provide immutable history and tamper-proof protection of the software development lifecycle. With CodeNotary, it is now for the first time possible for Home Assistant to ensure that only approved code runs on the hundred of thousands homes using their project and to fulfill its mission to put local control and privacy first.

"We were able to implement this solution in record time. CodeNotary’s open-source approach, the easy integration into our DevOps chain and the flexibility when it comes to revocation is a real game-changer. That is how software trust and integrity should look and feel," said Pascal Vizeli, founder and one of the core developers of Home Assistant.

Home Assistant is the world’s largest home automation platform controlling over 1,700 different devices and services without storing any data in the cloud. Powered by a worldwide community of developers & DIY enthusiasts, it comprises over 120k members on Reddit and over 70k Discord users. GitHub’s "State of the Octoverse" 2019 listed Home Assistant as the tenth biggest open-source project on its platform with 6,300 contributors.

"Our team at CodeNotary is thrilled to support such a great and wildly popular open-source project as Home Assistant. Our zero trust solution protects the whole software supply chain from code commits to runtime verification, and makes now every Home Assistant deployment verifiable and immediately revocable in case of security updates or malicious code," said Dennis Zimmer, CTO of CodeNotary Inc.

Links

CodeNotary:

Home Assistant:

CNIL Metrics & Logs

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

immudb

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

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.