Scan for known vulnerabilities at any time, for 10 thousand or 100 million artifacts.
Vulnerability scanning at scale
Instantly identify what is yours and what isn’t. Create SBOMs, any language, any container.
With immutable storage
Enforce compliance at every stage of your software pipeline.
Build, Deployment, Runtime
Built with trust and immutability in mind
Based on open source immudb, our highspeed, immutable store. Protect your DevOps against geopolitical Cyberattack risk.
Simple and fast CI/CD integration
Ultra-fast and simple integration with all your existing languages and CI/CD
Strong deployment enforcement
Quickly identify and remove Docker containers and Kubernetes deployments built with untrusted components
Stay compliant with the Cyber-Security Executive Order
Attach tamperproof bill of materials for your apps, Docker containers and Kubernetes deployments and make them instantly visible to your customers, auditors and compliance professionals
High-Speed immutable Database
Docker Container
Protection
Kube-Notary
for Kubernetes
JSVCN Library
for The Web
JVCN Library
for Java
Java Maven
Package
Jenkins CI
Windows Command Line
Github
Actions
Gitlab
CI/CD
Standalone
Travis CI
Codenotary Trustcenter enables any company, developer, automation engineer, DevOps engineer to secure all stages of a CI/CD pipeline.
Attestation (Notarization & Authentication) of every step in your pipeline including vulnerability scanner results and evidence in a tamper-proof and immutable service enables you to reach Level 3 & 4 of the SLSA (Supply-chain Levels for Software Artifacts) standard.
With Codenotary Trustcenter® you can easily build immutable, tamper-proof
solutions and comply with auditor requirements and regulations and laws.
Provide SBOMs
to your customers
Reduce costs for
DevOps compliance
Track artifacts
in your CI/CD pipeline
Search and remove
unwanted components throughout your organization
Prevent
Solarwinds-style attacks
Auditable
SDLC envidence
Our software prevents and mitigates damage from harmful components in your DevOps environment.
Copyright © 2021, 2022 Codenotary Inc. All rights reserved.
Please enter contact information to receive an email with the free trial details.
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.
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.
No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:
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.
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.
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.
We will also send you the research paper
via email.
Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain.
