Media Alert

Intel at Open Confidential Computing Conference 2024

Join Intel experts for panel discussions and talks at this year’s Open Confidential Computing Conference (OC3), a virtual event on March 13. Hosted by Edgeless Systems, OC3 is the premier event for security architects, cloud-native software engineers, IT security experts, CISOs, CTOs, security researchers and developers who want to learn about confidential computing.

This press release features multimedia. View the full release here: https://www.businesswire.com/news/home/20240308183003/en/

Intel technologists will present advances in confidential computing and participate in a CTO panel discussion at this year's Open Confidential Computing Conference. The virtual event is March 13. (Credit: Intel Corporation)

Protecting systems and sensitive, confidential or regulated data, especially while in use, has never been more critical. As computing moves to span multiple environments – from on-prem to public cloud to edge – organizations need protection controls that help safeguard sensitive intellectual property (IP) and workload data wherever that data resides. Learn how Intel, together with its partners and customers, builds the trusted foundation for protecting AI workloads and computing in a data-centric world.

Open Confidential Computing Conference (OC3) 2024
When: March 13, 2024
Where: Virtual Event
Registration: Free to attend

Confidential Cloud Native Attestation – Challenges and Opportunities

Confidential computing brings with it tamper-resistant registers to measure digital ingredients, akin to what the Trusted Computing Group’s TPM 2.0 offers, such as BIOS, firmware, kernel and beyond. Clouds are varied in their infrastructure and multiple confidential computing vendors, each potentially with multiple product generations, offering confidential CPUs, GPUs and other special-purpose processing units. Further, there are at least three flavors of confidential virtual machine (CVM) use – whole confidential Kubernetes clusters, launching traditional virtual machine payloads as a CVM using KubeVirt or Virtual Kubelet, or running a confidential container, like CoCo. What should one measure, particularly with confidential clusters where workloads come and go? The trick lies in capturing invariants and keeping them separate to not have a combinatorial explosion of values to register in an attestation service as good values. Further, what is the essence that we must keep invariant to protect the workloads in the various contexts?