IBM today announced the general availability of IBM Cloud Data Shield, a service built to better protect business applications while information is at rest, in transit, and in use. The platform, developed in a partnership with Fortanix, relies on confidential computing, a technology gaining traction as more organizations seek new ways to secure their sensitive data in the cloud.
Cloud Data Shield, which went into beta in late February, contains Fortanix's Runtime Encryption platform and Intel Software Guard Extensions technology. The combination enables "confidential computing," a term used to describe the protection of data in use by performing processes in a hardware-based trusted execution environment (TEE). A TEE ensures that only authorized code can execute in an environment and that external forces can't tamper with it.
Modern approaches to cloud security address data at rest, when it's on a hard drive or in a storage system, and in transit, when it's moving between locations. Few secure data when it's in use by an application and exposed in memory. Data must be decrypted for an application to use it, making it possible for criminals or insiders to access the data while an application runs.
"A user with privileged access can take a memory dump at run time and could still access the sensitive information stored in memory," says Nataraj Nagaratnam, CTO and director of cloud security for IBM Cloud and Cognitive Software. In-memory encryption, another term for confidential computing, encrypts data in use to eliminate the possibility of exposure.
Cloud Data Shield lets users run containerized applications in a secure enclave on an IBM Cloud Kubernetes Service host. The service supports user-level code to allocate enclaves, which are protected from processes running at higher levels of privilege. IBM offers TEE-based secure enclaves in Bare Metal servers and in Kubernetes Nodes in all cloud data centers, and it teamed with Fortanix so clients could use TEE without learning the ins and outs of secure enclaves.
"You don't have to understand how enclaves work," explains Fortanix CEO Ambuj Kumar. Cloud Data Shield runs containerized applications on IBM Cloud Kubernetes or Red Hat OpenShift, both in a secure enclave running on Intel SGX hardware. Customers can use their own custom application without modifying it to access all features of the service. When the container is converted, users can access a dashboard to see how the application is running.
"You get the visibility, and your software is now running securely without you having to configure or recompile your container," Kumar says. Application writers don't have to worry about changing anything. There is an option to use the open source Enclave Development Platform (EPD) to write native applications for confidential computing environments, IBM says.
During the year-long beta period, Nagaratnam says his team learned about clients' requirements to run different languages; as a result, they expanded the language capabilities: Fortanix's run time encryption OS lets containerized applications run in the secure enclaves with no code change, and it supports languages including C, C++, Python, and Java. They also learned the utility of having some curated applications, like NGINX, Vault, and MySQL, run on the TEE.
Confidential Computing: What It Is, Why It's Growing
Confidential computing is not new; however, it is becoming more broadly known and discussed as businesses look for new ways to protect sensitive data from this kind of threat. In August 2019 the Linux Foundation announced plans to form the Confidential Computing Consortium (CCC), a nonprofit made up of hardware vendors, cloud providers, developers, open source pros, and academics focused on defining and driving adoption of confidential computing.
"It's always been a niche thing that's been hard to go mainstream, and it's really pretty new," says Jim Reavis, co-founder and CEO of the Cloud Security Alliance. This has begun to shift. The current attitude toward confidential computing mirrors the early attitudes toward the cloud.
"Twelve years ago, we saw interest in 'kicking the tires' on cloud, in general, to see if it was something that would be valid for highly sensitive information where you don't want any sort of a window of it decrypted," Reavis continues. Now, with confidential computing, businesses are trying to understand the types of attacks that require it and costs of application migration.
A few scenarios would require the security that confidential computing promises. Reavis points to insider attacks inside a cloud provider, where a business doesn't trust the infrastructure provided. While some attacks could resemble this, he says, providers are usually pretty secure.
There is a bigger interest in confidential computing from a compliance and risk management perspective, he continues. Organizations are worried about scenarios in which a cloud provider is in a foreign country, or has relations with a country, and the government requests access to data. They want to assure themselves they have decoupled provider access and root of trust, and know that the information is isolated in the secure enclave.
The interest is stronger in the military, central banks, and financial services organizations where "they do worry about disruptions to the supply chain or memory attacks that are very sophisticated," Reavis says. These days, there are actors who could pull those attacks off.
Questions remain about how comfortable businesses are with the secure enclave tech, which is a more secure architecture but still relatively young. Still, confidential computing is based on principles of isolation, sandboxing, and trusted platform modules that have been around for a long time. Sophisticated businesses are investing in this technology and starting to pilot applications.
"They definitely see this as a very solid concept," Reavis notes.