PrivateCore

PrivateCore is a venture-backed startup located in Palo Alto, California that develops software to secure server data through server attestation and memory encryption. The company's attestation and memory encryption technology fills a gap that exists between “data in motion” encryption (TLS, email encryption) and “data at rest” encryption (disk encryption, tape encryption) by protecting “data in use” (random access memory). PrivateCore memory encryption technology protects against threats to servers such as cold boot attacks, hardware advanced persistent threats, rootkits/bootkits, computer hardware supply chain attacks, and physical threats to servers from insiders. PrivateCore was acquired by Facebook, a deal that was announced on 7 August 2014.

PrivateCore
Private
IndustryEncryption
FoundedOctober 19, 2011 (2011-10-19)[1]
FoundersOded Horovitz
Steve Weis
Headquarters,
U.S.
Area served
Worldwide
Key people
Oded Horovitz (CEO, co-founder)
Steve Weis (CTO, co-founder)
Todd Thiemann (VP Marketing)
Carl Waldspurger (Advisor)
ParentFacebook, Inc. 
Websitewww.privatecore.com

History

PrivateCore was founded in 2011 by security veterans from VMware and Google with seed funding from Foundation Capital.[2][3] PrivateCore “virtualizes” physical security and enables service providers and enterprises deploy servers processing sensitive data in outsourced environments while maintaining security around data in use.[4]

The company's memory encryption technology has been spurred by a number of industry trends including the increasing sophistication of hackers, a larger number of servers in outsourced environments, larger amounts of sensitive data being placed in persistent memory, and x86 virtualization technology which can increase the environment attack surface.

PrivateCore was acquired by Facebook, a deal that was announced on 7 August 2014.[5][6]

Technology

PrivateCore's focus is securing data-in-use on x86 servers. The company has taken advantage of recent microprocessor innovations including larger microprocessor caches and hardware cryptographic acceleration technology that enable more effective methods of encrypting memory while maintaining acceptable application performance. The technology approach goes beyond previous academic research efforts such as TRESOR.

PrivateCore assumes that the only element that need be trusted in a system is the Central Processing Unit (CPU). The firm uses Trusted Platform Module (TPM) chips and Intel Trusted Execution Technology (Intel TXT) to provide remote server attestation. PrivateCore also supports the cryptographic hardware acceleration provided by Intel AES-NI technology.

PrivateCore technology is positioned as being most applicable to outsourced or hosted environments where the enterprise cannot have trust in the compute infrastructure.[7]

Products

The PrivateCore vCage product portfolio comprises vCage Manager and vCage Host. vCage Manager validates the integrity of x86 servers running Linux as well as the vCage Host. vCage Host installs on bare-metal servers and provides a hardened hypervisor based on KVM that can secure server random access memory (RAM) with AES encryption. vCage Host does this by loading a secure hypervisor into CPU cache and acting as a gateway to encrypt memory paging in and out between the CPU cache and RAM. vCage memory encryption leverages the KVM hypervisor but also has the potential to support other hypervisors. vCage Host supports existing KVM management tools.

vCage supports a number of use cases including creating OpenStack trusted computing pools as well as protecting x86 servers in co-location and bare-metal cloud environments.

vCage Manager and vCage Host became generally available on 11 February 2014.[8]

gollark: Monoids.
gollark: ```Within the grove the mist thickened to a warm and bitter-tasting fog; from somewhere up ahead came the sound of bubbling water. The trees parted, and Djishin found himself in a clearing where four nuns in white robes sat contemplating a monolith of glistening black basalt. On its face were inscriptions such as the monk had never seen: (>>=) :: m a -> (a -> m b) -> m b return :: a -> m a“What is this stone, great ladies?” asked Djishin.“We call it the Monad,” said the first nun.“Why do you venerate it so?” asked Djishin.“Through it, we may touch the impure without being corrupted,” said the second nun. “We can fell a Maybe-tree with a Maybe-ax and always hear a Maybe-sound when it crashes down—even if the sound is Nothing at all, when the ax isn’t real or there’s no tree to fall.”```
gollark: …¿
gollark: JS is dynamically typed, look where that got usm
gollark: Or at least === as default.

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.