CAS and Home Assistant: Making Sure Smart Home Are Secure Homes

When we announced the Community Attestation Service, we had a vision. A vision that included two of our passions. The first, making sure software content could be trusted in way that is immutable, tamper-proof and cryptographically verifiable. The second, our passion for open source and its developers. We wanted to ensure that any developer, anywhere, had in their toolbox a completely free and open source service that would allow them to easily integrate content trust and software supply chain security into their projects.

We’d very proud to announce that Home Assistant has rolled out integration of CAS for both the Home Assistant core project as well as third party add-on developers. This is an important step in making sure that as you build your smart home and integrate add-ons and components, your Home Assistant instance is protected from running malicious code, making sure your smart home is a secure home. You can read all about it on the Home Assistant blog.

Why CAS?

CAS is a totally free and open source service that helps you secure and trust your software. It does this by allowing you to create a Software Bill of Materials for your containers and also notarize them, creating an origin record and attesting to what their composition is. This then allows you to trust, or un-trust, those individual components in the bill of materials. This allows developers to ensure that only components they approve make it into their build pipeline, and allows users to trust that every single piece of software they receive from the developer have not been tampered with. Naturally, if a problematic library (such as one with a security issue) or unwanted component makes it into the software, it can easily be un-trusted and prevented from being built by a developer or deployed by a user.

We also make sure this data can never be tampered with by storing it in immudb, our open source, immutable, tamper-proof database. The data in immudb can also be cryptographically verified *on the client side* and another or third party (coming soon) to ensure that the integrity of the data. CAS also preserves your privacy as none of the code/binaries/containers are uploaded to CAS, only the unique signature is.

CAS is also lightweight and super easy to integrate into your project either via scripts or GitHub Actions. You can find out more about CAS and immudb in the links above, by reading the docs and you can also join us on our discord server.

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.

MOST POPULAR

Sorry. No data so far.

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.