BedRock HyperVisor™
Not all hypervisors are created equal, and at BedRock the focus was to build a Formally Secured Computing base for virtualizing mixed criticality workloads in the demanding critical infrastructure, where safety and security are mandatory, and where failure is not an acceptable state.
The BedRock HyperVisor™ (BHV™) blocks lateral movement of threats and eliminates the attack surface with a formally secured computing. The BHV™ is a virtualization TCB. Thanks to BedRock Active Security™, even unmodified operating systems and applications can be protected against attacks.
BHV™ supports workloads being unmodified guests, containers and 
services. Traditionally applications are vulnerable to attacks. By consolidating these workloads on top of BHV™ not only the benefits of SWaP-C* are a significant benefit, but also the fact that lateral movements are impossible thanks to the formally proven Bare Metal Property™, but also the BedRocked™ applications can be locked down, monitored and made cyber resilient with deep semantic introspection and policy.
BedRocking™ operating systems, services, containers and applications is saving costs, adds agility and creates cyber resilient systems from existing assets in a software defined architecture.
If you are interested in partnering with BHV™ and Active Security™ for Orchestration, Device Management and Policy Management, please contact us to discuss how to enable and expand your customer base on Bedrocked™ infrastructure.
Zero Trust Design™
Built on a capability-based microkernel, resources are not being created for general consumption, but are locked down by default only for consumption by specific targets that are being assigned dedicated “capabilities” to operate a resource. Think of a resource, a “door”. In common architectures every attacker that would gain access of that resource would be seeing this “door” and be able to open/close/operate it. In a capability-based system the attacker would still only see a “wall”, with no ability to see or operate the resource. This is a fundamental design time decision BHV™ builds on and enables the architecture to build in the Defense In Depth architecture that is unique among commercial offerings.Formal Verification
Building a foundation based on formal verification enables us to precisely define with a formal model what a system can do. This is then matched, through proofs, to the actual code implementing the model. If the proof can satisfy the model, the code is formally verified. Formal verification allows us to establish the correctness of a system to the same degree of confidence that you know that 1 + 1 = 2, eliminating human error. In other words, we have mathematical proof of the BedRock Hypervisor’s effectiveness. At BedRock we are building formal verification at scale by investing in automation.
Minimal Attack Surface
The BedRock Hypervisor combines the best concepts from microkernels, capability-based systems, and modular design for superior performance, security, and isolation. Because it enforces the principle of least authority, BedRock is able to guarantee that most attacks are not possible to begin with. Our secure architecture keeps all critical functions, including Active Security and Policy Enforcement, below the OS-reachable attack surface, thereby fully protecting the OS and its applications.
Security
BedRock Security is enabled without a cooperating operating system or application, eliminating the attack surface of the components. Based on formal verification, the capability-based system ensures resources can only be accessed when explicitly enabled. With this level of security embedded into the BedRock Hypervisor, users can run the software stack from the OS and up without modification beyond their life cycle, while still preventing attacks.
Unmodified Guest OS & Applications
The BedRock Hypervisor is designed to run unmodified guest operating systems without the need to recompile the kernel or any application. Powered by formal methods, the Hypervisor cannot be breached, and, therefore, is not part of the attack vector. The fundamental hardware abstraction layer can leverage hardware features while concealing them from the OS, increasing system security.
No Vendor Lock-In
The BedRock Hypervisor includes a business-friendly open source license. This prevents vendor lock-in, provides freedom of choice, and prohibits intellectual property contamination. Rather than create a dependency, BedRock Systems is committed to community-driven projects and collaboration.
KEY BENEFITS & VALUE PROP OF BEDROCK’S SECURE TCB
