Skip to main content

Response by the CCC to the Office of Science and Technology Policy’s RFI on Advancing Privacy-Enhancing Technologies

By Blog

July 7, 2022

To Whom It May Concern:

Please consider the following submission to the Request for Information on Advancing Privacy-Enhancing Technologies from the Confidential Computing Consortium. The Confidential Computing Consortium (https://confidentialcomputing.io) is a Linux Foundation project “to accelerate the adoption of Trusted Execution Environment (TEE) technologies and standards” and has a diverse membership of hardware and software vendors and cloud service providers (https://confidentialcomputing.io/members/). This response was prepared by the group’s Technical Advisory Council with participation from across the membership, and ratified by its Governing Board. The Linux Foundation is a non-profit organization registered in the United States as a 501(c)(6).

The Confidential Computing Consortium has a mandate to engage with governments, standards agencies and regulatory agencies to encourage adoption of Confidential Computing, as well as work with the larger ecosystem and engage with existing and potential end-users of the technologies. It also works with open source projects to further development of implementations. The Confidential Computing Consortium is committed to encouraging open source implementations of Confidential Computing technologies to ensure wide-spread adoption, scalable community involvement, transparency of process, increased security and ease of auditing by relevant interested parties and authorities.

The Confidential Computing Consortium welcomes collaboration with governmental and non-governmental organizations and has mechanisms in place to provide appropriate membership, as well as open technical participation without any membership requirement.

Sincerely,
Stephen R. Walli
Confidential Computing Consortium, Governing Board Chair

Read the response here.

Roadsec: LATAM’s largest hacker conference

By Blog

The Confidential Computing Consortium (CCC) was one of the 10 communities selected to be part of Roadsec, LATAM’s largest hacker conference. Over 5000 participants were present at this in-person conference held in Sao Paulo.

Roadsec started as meetups about cyber-security that were organized across different cities (thus the name Roadsec, as speakers were always on the road). Every year the community gathers in Sao Paulo for the main conference.

Sao Paulo is considered an alpha global city and serves as Latin America’s financial and technological hub. Major banks and cloud service providers have their headquarters and data centers in this city.

Nick Vidal, CCC’s Outreach Committee Co-Chair, was at the conference promoting the CCC and also inviting participants to the Cryptle Hack Challenge, a secure multi-player Wordle clone that demonstrates how Confidential Computing works.

Roadsec organizers were kind enough to provide the CCC a booth to present this emerging technology called Confidential Computing, which protects data in use by performing computation in a hardware-based Trusted Execution Environment. These secure and isolated environments prevent unauthorized access or modification of applications and data while in use, thereby increasing the security assurances for organizations that manage sensitive and regulated data.

Recently, there have been many serious cyber attacks in Brazil, including the leakage of sensitive patient data from DATASUS and sensitive client data from Banco Pan. Confidential Computing could have helped prevent these data leakages.

CCC Project Updates

By Blog

Check out what the CCC Projects have been up to!

Gramine

Gramine project (formerly known as Graphene) will release a new stable version v1.2 in upcoming weeks.

Gramine is a library OS that enables protecting sensitive workloads with Intel® Software Guard Extensions (Intel® SGX). Gramine runs unmodified Linux applications on Intel® SGX out of the box and provides all functionality required for end-to-end protection of workloads: remote SGX attestation, transparent encryption of security-critical files, secure multi-processing. Gramine follows a “lift-and-shift” paradigm for running unmodified applications: to “graminize” the application, it is enough to write a so-called *manifest* file that reflects a runtime configuration of the protected application. Gramine also supports Docker integration via a tool called Gramine Shielded Containers (GSC) and provides a growing set of curated applications, runtimes and frameworks.

In comparison to the previous release, Gramine v1.2 introduces a major overhaul of the FS subsystem. In particular, the Protected Files (PF) feature was significantly reworked. A new manifest syntax allows to mark whole FS mounts for encryption. The PF feature is now available not only in the SGX mode of Gramine, but also in the direct mode, for ease of debugging. We also added support for renaming PFs, memory mapping them with read-write permissions and encrypting them with different user-supplied encryption keys. As a side effect of this rework, multiple bugs in the FS and PF subsystems were fixed.

Additionally, Gramine v1.2 introduces a final reworked CPU/NUMA topology feature (previously marked as experimental). Now, CPU/NUMA topology is securely forwarded inside a Gramine SGX enclave and enabled by default. Among other improvements in Gramine, we highlight better support for CentOS/Fedora/RHEL Linux distributions and the update of the EPID SGX attestation tools to use IAS API v4. We also added a Rust example (a simple web server that uses hyper and tokio crates), as well as a new Python example for SGX quote retrieval.

Along with this technical work, Gramine was presented in different forums and featured in articles and blog posts:

– Gramine talk at the FOSDEM’22 conference: https://fosdem.org/2022/schedule/event/tee_gramine/

– Gramine talk at a Confidential Computing Consortium (CCC) webinar:  https://confidentialcomputing.io/webinar-gramine/

– Highlighted in several use cases and projects at the Open Confidential Computing Conference (OC3 2022) conference: https://www.oc3.dev/program

– Integration with Open Federated Learning (OpenFL) framework: https://medium.com/openfl/a-path-towards-secure-federated-learning-c2fb16d5e66e

– Integration with IBM/Gematik e-Prescription solution: https://github.com/eRP-FD/vau-base-image

– Reference solutions with Gramine as part of the Confidential Computing Zoo (CCZoo): https://github.com/intel/confidential-computing-zoo

– Whitepaper “Computation offloading to hardware accelerators in Intel SGX and Gramine Library OS”: https://arxiv.org/abs/2203.01813

– Blog post “How Open Source Gramine Accelerates Expanding Confidential Computing Market”: https://www.linkedin.com/pulse/how-open-source-gramine-accelerates-expanding-confidential-mona-vij/?trk=articles_directory

– A series of technical blog posts: https://gramineproject.io/blog/

For more information on the release please check out: https://github.com/gramineproject/gramine/releases/tag/v1.2

We invite you to join the Gramine community and contribute to adoption of confidential computing through open source collaboration. We also look forward to your feedback as you deploy this latest release of Gramine for your solutions.

Enarx

The Enarx project had three releases this quarter:

– Enarx 0.3.0 (Chittorgarh Fort) released in March with TLS support, attestation & validation support (https://blog.enarx.dev/chittorgarh-fort/).

– Enarx 0.4.0 (Fort of Dhat al-Hajj) released in April with SGX2 support, improved TLS support, and much more (https://blog.enarx.dev/enarx-0-4-0-fort-dhat-al-hajj/).

– Enarx 0.5.0 (Elmina Castle) released in May with many new/improved features: New enarx deploy subcommand. SGX with EDMM / SGX2 support (https://blog.enarx.dev/elmina-castle/).

In addition to Linux, Enarx is now available on MacOs, Windows, and Raspberry Pi:

– Enarx can now be compiled on additional platforms in a light development version. From MacOS to Raspberry Pi — Extending the Enarx Development Platforms.  (https://blog.enarx.dev/backend-nil/)

The Enarx project announced the Cryptle Hack Challenge:

– Cryptle is a secure multi-player clone of Wordle. The goal of the Cryptle Hack Challenge is to uncover vulnerabilities in the Enarx project. (https://blog.enarx.dev/cryptle-hack-challenge/).

The Enarx community has achieved a huge milestone: we have collectively published 100 tutorials and articles over at Wasm Builders!

– As part of the Confidential Computing Fellowship program, the Enarx project has received several mentees from Outreachy and LFX Mentorship. Wasm Builders has served as a welcoming environment where Enarx community members can share their learning experiences with others (https://blog.enarx.dev/enarx-community-reachs-100-tutorials/).

The Enarx project has participated in the following events:

– Nathaniel McCallum presented “WASI Networking” at Wasm Day at KubeCon + CloudNativeCon Europe 2022 (https://blog.profian.com/wasm-day-at-kubecon-cloudnativecon-europe-2022/).

– Outreachy intern Shraddha Inamdar presented “Enarx: The Platform Abstraction for Trusted Execution Environments” at FOSSASIA (https://enarx.dev/resources/2022-04-09-fossasia).

– CCC Fireside Chat: Stephen Walli received Mike Bursell to discuss his book “Trust in Computer Systems and the Cloud,” with a particular focus on the impact of Confidential Computing on security, trust and risk (https://blog.profian.com/trust-in-computer-systems-and-the-cloud/).

Veracruz

  • We recently announced our 22.05 release which included first-time contributions from several people including Aryan Godara, Mohamed Abdelfatah, and Sagar Arya.  Many of these contributions focussed on adding new examples to the Veracruz repository.  Mohamed will be joining us as our Outreachy-sponsored intern shortly, working on providing better documentation of the expected behavior of Wasi system calls (https://github.com/veracruz-project/veracruz/releases/tag/veracruz-2205).
  • We’ve worked to simplify Veracruz attestation further, across all of our supported platforms, making the process more uniform and removing platform-specific quirks.
  • We’ve started work, and are progressing quickly, on supporting seL4 as an in-enclave operating system for ultra-low TCB enclaves.
  • We’ve worked to improve Veracruz documentation.
  • Many other smaller bug fixes, performance improvements, and upgrades of dependencies to fix security concerns.

CCC Project Updates

By Blog

Check out what the CCC Projects have been up to!

Gramine

Following the first production-ready release “v1.0”, The Gramine Project is releasing “v1.1” in upcoming weeks. One highlight of this release is stability improvements for Golang and Rust workloads. Another prominent feature of the release is support for the musl C standard library – now Gramine allows users to choose between glibc and musl, depending on users’ requirements on the binary size (TCB), as musl is more light-weight than glibc. Also, AddressSanitizer was integrated in Gramine, and it runs in the CI on each change, for detecting any security issues ahead of code merge. This version adds several other features as well as multiple bug fixes (thanks to our ever-increasing user base for reporting issues!).

While there are several use cases under development, we would like to highlight the production release of the OpenVino Security Add-on (OVSA) for Model IP protection (consider using it for your protected ML workloads). Please reach out to the Gramine team if you are experimenting with Gramine and would like to be added to the list of “Users of Gramine

Enarx

In Enarx’s first release “version .0.1.0” (codenamed Alamo) we provided WebAssembly as a runtime. For our upcoming release “version 0.2.0” this coming quarter we are looking forward to providing support for attestation, including Intel’s SGX and AMD’s SEV.

Other areas where we are working on are support for filesystem and networking, which depend on upstream collaboration with the WebAssembly community.

Enarx is under high development and is not production ready yet, but our hope is that these initial releases will allow developers to experiment with Enarx and see its progress.

If you are interested in learning more about the Enarx project, please access our website, star us on GitHub, and join our chat.

Gramine 1.0 release

By Blog

Announcing Gramine production ready release!

Having recently joined the Confidential Computing Consortium in the Linux Foundation, The Gramine Project (formerly known as Graphene) is proud to announce the first production-ready version to enable protecting sensitive workloads with Intel® Software Guard Extensions (Intel® SGX).

The project started as a research prototype at Stony Brook University in 2011, and the first open-source version was published in 2014, followed by the Intel® SGX port in 2017 in collaboration with Intel Labs. In December 2018, Golem and ITL joined the project, forming the core of the open source community around the project, including a first release.  The Gramine community has subsequently grown into a diverse group of contributors, from universities, small and large companies, as well as individuals.

Gramine not only runs Linux applications on Intel® SGX out of the box, but also provides several tools and infrastructure components for a push-button lift-and-shift paradigm for running unmodified applications on confidential computing platforms based on  Intel® SGX. Gramine supports both local and remote Intel® SGX attestation, and with both EPID and DCAP schemes. With the protected files feature, security-critical files are automatically encrypted and decrypted inside the enclave. Gramine supports several performance optimizations for Intel® SGX applications including asynchronous system calls. Gramine is one of the few frameworks that supports multi-process applications by providing a complete and secure fork implementation. Gramine supports Docker integration via a tool called Gramine Shielded Containers (GSC) that automatically converts Docker images to Gramine images.  Containers built with GSC can be deployed via Kubernetes for confidential containers and microservices.  Gramine also supports cloud deployment with Azure Confidential VMs and integrates with Azure Kubernetes Services in Azure cloud.

Since our last release, there have been major changes in the code with 1272 files changed, 100637 insertions, 112144 deletions, 1648 commits from 49 authors. This includes a major rewrite of the code that handles features including memory management, thread handling, process handling, filesystem and signal handling. You can find the detailed changelog at our github.  In future, we plan to continue Gramine development with additional features, code cleanup, tooling, and documentation. We also plan to add generic support for I/O device communication as well as add additional Platform Adaptation Layers (PAL) for other TEEs like Intel® TDX.

Gramine has a growing set of well-tested applications including machine learning frameworks, databases, web servers, and programming language runtimes and there are several projects that are already experimenting with Gramine for developing their solutions to protect data in use. We expect that Gramine 1.0 will bring many of those solutions to production. We look forward to your feedback as you deploy this latest version of Gramine for your confidential computing solutions with lift-and-shift capability.

For more information on the release please check out: https://github.com/gramineproject/gramine/releases/tag/v1.0

We invite you to join the Gramine community and contribute to adoption of  confidential computing through open source collaboration.

The Confidential Computing Consortium Year in Review, 2021

By Blog

We are just finishing the second year of the Confidential Computing Consortium, and it is time once again to look back on what the members have accomplished together. 

Membership & Project Growth

All of our meetings start with the reminder that all members are welcome and all projects are welcome. It have been this way since we launched. 

Remember that companies create non-profits like the Consortium in the broad open source space because our businesses benefit from that membership, and from working together towards common goals. We launched the Consortium with 15 premier and general members, growing to 27 corporate members and 2 non-profits by the end of the first year. While we lost a few members this year as company priorities shift, we have continued to grow to 36 corporate members and 4 non-profits over this past year. 

This year we welcomed the following companies to the Consortium: 

Ampere, Applied Blockchain, Baidu USA, Canary Bit, Cisco, Crust, Edgeless, En|viel, Ethernity Cloud, HUB Security, Madana, Opague Systems Inc, Phalla Network, Technology Innovation Institute, Western Digital, Xilinx. 

Our newest general member last week is Profian. The addition of general members through the year brought us over the twenty mark and we added a new general member representative to the governing board (Eric Voit, Cisco). 

A primary part of our shared mission is to support open source and standards projects relating to confidential computing to accelerate the acceptance and adoption of confidential computing in the market. This year the Consortium welcomed four new projects:

  • Keystone: Keystone is an open-source project for building trusted execution environments (TEE) with secure hardware enclaves, based on the RISC-V architecture. Our goal is to build a secure and trustworthy open-source secure hardware enclave, accessible to everyone in industry and academia.
  • Veracruz: Veracruz is a research project exploring the design of privacy-preserving distributed systems.  Veracruz uses strong isolation technology and remote attestation protocols to establish a “neutral ground” within which a collaborative, multi-party computation between a group of mistrusting principals takes place.
  • Gramine: Gramine is a rebranded Graphene project. A particular use case for Gramine is Intel Software Guard Extensions (SGX), where applications do not work out-of-the-box. Gramine solves this problem, with the added security benefits. Gramine can serve as a compatibility layer on other platforms.
  • Occlum: Occlum makes running applications inside enclaves easy. It allows one to run unmodified programs inside enclaves with just a few simple commands.

The Technical Advisory Council (TAC)

The Technical Advisory Council continues to meet every other week. It is an opinionated public debate and everyone is welcome to attend. Members in the TAC saw the need to begin to add some structure and this year created the idea of Special Interest Groups (SIG) as they put in place the Attestation SIG. It was recognized by members that attestation will become the next challenge in confidential computing and have begun the discussion of how best to enable TEE attestation across the industry. 

The TAC membership also published a more detailed Technical Analysis of Confidential Computing white paper.

The Outreach Committee

Outreach Committee members were also busy this year in their collaboration. The Consortium Webinar Series has been building with monthly entries covering our projects and topics that span our domain. This is a good quick way to get an introduction to projects as each project has contributed to the collection. 

A global pandemic makes it tough to gather together, but this year the members organized and ran the first Confidential Computing Developer Summit, C2DS in June. It was run as a virtual unconference with a full day of content. There was good attendance with 400 registered developers participating through the day. All the feedback was good and the team looks forward to building an event again this coming year. 

The Outreach Committee commissioned an analyst group to produce a market study this year. Working with members, the analysts have built a view of the confidential computing industry in its growth. The study will be published this month. 

Lastly, Outreach Committee members have been working towards launching an End User Advisory Council to attract broader input into how users of confidential computing technology see the challenges ahead. We had hoped to launch the advisory council at the Linux Foundation Open Source Summit in September, but pulled back as people continue to be cautious with pandemic travel. Look for a launch in the near future. 

Outreach is working with the Linux Foundation creative staff to improve the Consortium website and we will be rolling changes out soon.

General Administrivia

I have long joked that governing boards should be boring places voting on meeting minutes, money, and membership. 

  • In keeping with that intent, we continue to run a healthy budget surplus as working committees spend money cautiously in a pandemic. 
  • We reviewed and tuned our charter last year in the Fall. As members continued to evolve our transparent, collaborative endeavor together, they had suggestions for tweaks to the charter that were voted last Fall. We will open the charter again shortly to see what new changes will be proposed. In making this an annual practice, it becomes an easy muscle to exercise, and debates don’t become worrisome and contentious. 

We continue to get great support from the Linux Foundation services teams. Stephano Cetola has recently moved to become a technical director at the RISC-V organization. While we are sad to see him go, Brian Warner is stepping into the role of Linux Foundation program manager. This year Ashley Weltz joined the program management team to help put the developer summit and end user advisory council in place. 

I look forward to continue working with all of our members in the coming year. A number of new projects have approached the Consortium. New members continue to express interest. It should be an exciting year ahead. 

Updated January 2022 to reflect new members joining in Q4 of 2021.

The Confidential Computing Consortium Year in Review, 2020

By Blog

The first year of the Confidential Computing Consortium is coming to a close and it is an important time to reflect on what we’ve done and where we’re going as we look ahead to our next year. 

I want to start from the perspective of ‘why’ the Consortium. Companies create non-profits like the Consortium in the broad open source space because our businesses benefit from that membership. We launched the Consortium with 15 premier and general members and have since grown to 27 company members and 2 non-profit members. 

AccentureAlibabaAMDAnjunaAnqlave
ArmBaiduBytedanceCosmianCysec
DecentriqFacebookFortanixGoogleHuawei
iExecIntelKinditeMicrosoftNvidia
Oasis LabsOracleR3Red HatSwisscom
TencentVMware

Bold indicates a premier member. Our non-profit members are: iotex.io, MIT

For all of our corporate members: 

  • Confidential computing directly (or indirectly) benefits our company stories to customers.
  • Directly supporting/servicing the growth of well-formed OSI-licensed projects that create hardware TEE based solutions can provide building blocks for products and services to customers as part of our product portfolios. 
  • Directly funding/participating in collateral development that educates the marketplace and creates a community within the industry provides a consistent baseline in the market on which to build our individual customer-facing messages.  
  • Directly engaging in the Technical Advisory Council (TAC) discussions provides a collaborative space to debate and test engineering-focused discussions relating to confidential computing and accelerates innovation in the domain. 
  • The Consortium provides a shared cost structure and participation structure for the members supporting projects and building educational collateral.
  • Being a member creates a direct association of the company brand with the technology space through the Consortium brand.
  • ‘Hallway discussions’ around the main business of the Consortium create and strengthen business relationships and opportunities.  

The primary working committees of the Consortium are the Technical Advisory Council (TAC) and the Outreach Committee. They have each (and together) accomplished a lot in these first ten months getting to know each other as members and working towards those common objectives. (Some of this has been particularly challenging as the last five months have been in the midst of the COVID-19 pandemic.) 

The TAC has:

  • Accepted the first three open source projects under the Consortium umbrella in Oct 2019 (enarx, the Open Enclave SDK, and the SGX SDK for Linux). 
  • Agreed on a confidential computing definition, the scoping of the consortium mission, and scoping of TEE to the definition.   
  • Continued to improve and evolve the project acceptance criteria and services work.
  • Accepted three new projects through the Spring 2020 (Graphene, the Trusted Compute Framework, and Keystone… ).
  • Developed an introductory whitepaper on Confidential Computing with the Outreach Committee.
  • Developed content then participated in analyst and press briefings (e.g., Gartner, Forrester, IEEEFortune)
  • Developed and evolved work processes and templates (e.g., project submission) to accomplish the mission.
  • The TAC chair has engaged and coordinated with outside organizations (e.g., homomorphicencryption.org, IETF).

The Outreach Committee has: 

  • Developed the confidential computing messaging framework in coordination with TAC.
  • Organized and ran the press and analyst briefings (e.g., Gartner, Forrester, IEEE, Fortune)
  • Developed the current white paper with TAC.
  • Begun the long process of web site improvements. 
  • Organized and ran our booth presence at the Linux Foundation Open Source Summit in Lyon (October 2019), and at the Linux Foundation Open Source Summit North America virtual event. 
  • Begun planning for a conference for Spring 2021 for 300-500 participants, (and a test virtual event this Fall). 
  • Begun tracking interest in the Consortium with the launch of the Confidential Computing whitepaper.

I would very much like to thank all of the participating members. A truism about successful open source project communities is the need for people in the community to be willing to chop wood and carry water. The ‘community’ isn’t some magic workforce, but rather a group of individuals doing the work together towards shared goals. This is just as true when you build a non-profit as an umbrella organization for such OSI-licensed projects. 

I would be remiss if I didn’t thank our Linux Foundation program manager, Stephano Cetola, who helps us navigate the Linux Foundation services we use, and keeps clearing the to-do lists we collectively put in front of him, as well as Scott Nicolas from the Linux Foundation who helped us with the initial heavy lift of starting the Consortium and continues to get dragged into the occasional discussion about all things charter related.  A special thanks also to Omkhar Arasaratnam and Morgan Akers from JP Morgan Chase who have been active participants in TAC discussions and have shown us the need to build an end user advisory committee this coming year. 

We have a number of exciting projects to begin our second year with the TAC working on an in-depth technical report, the Outreach Committee exploring a Fall virtual event, and beginning work on the End User Advisory Committee. All this along with our regular work supporting the open source projects under our umbrella. I’m looking forward to it, and hope the membership is as excited as I am. 

As the Confidential Computing Consortium Grows

By Blog

The Confidential Computing Consortium is a community focused on open source licensed projects securing data in use and accelerating the adoption of confidential computing through open collaboration. The Consortium announced its intentions in August 2019, and has been heads down laying the foundations for open collaboration between the parties involved in confidential computing and creating a welcoming home for open source projects.

What is Confidential Computing

Confidential Computing is the protection of data in use by performing computation in a hardware-based Trusted Execution Environment. Technology solutions exist for securing data at rest in storage and data in transit across the network, but until recently securing data in use during computation wasn’t part of the story. Chip manufacturers have been bringing technologies to market (Intel with Secure Guard eXtensions, Arm with TrustZone, and AMD with Secure Encrypted Virtualization). These are examples of Trusted Execution Environments (TEE), the core building block in confidential computing. Software development frameworks and application deployment mechanisms were soon to follow. 

Developers that handle sensitive data such as Personally Identifiable Information (PII), financial data, or health information need to remove threats that target the confidentiality and integrity of the data in system memory. Using TEE to isolate and protect the execution environment of applications ensures data is secure while in use, preventing it from being exposed in the memory of the compute infrastructure. 

Accomplishments to Date

Since launch, the Consortium established an Outreach Committee–chartered with educating the industry and developers about confidential computing, and supporting the health of the Consortium projects–and a Technical Advisory Council (TAC)–chartered with driving the technical direction of the Consortium and supporting the Consortium projects.

In October, the TAC met at the Open Source Summit EU and heard from, and approved, three open source projects to join the Consortium:

  • Software Guard Extensions (SGX) SDK for Linux, designed to help application developers protect select code and data from disclosure or modification at the hardware layer using protected enclaves in memory.  
  • Open Enclave SDK, an open source framework that allows developers to build Trusted Execution Environment (TEE) applications using a single enclaving abstraction. Developers can build applications once that run across multiple TEE architectures.  
  • Enarx, a project providing hardware independence for securing and deploying applications using TEEs. 

As we come through the first quarter of 2020: 

  • The TAC has debated at length a definition for confidential computing after a survey of the members and across the industry.  
  • The Outreach Committee has begun educating industry shapers, like analysts, on this definition, and the work of the Consortium projects  
  • The Outreach Committee is developing educational materials for developers and the wider industry 
  • The administration of the Consortium continues to evolve and take shape. The Legal Subcommittee has now met on a number of topics to get a measure of how the Consortium can best meet its members’ legal needs. The Budget subcommittee is working to help the working committees have a better grasp of the money to be spent supporting Consortium projects and building educational collateral. 
  • New members continue to join the Consortium. We’re up to nine premier members, and 13 general members, with several more members filing paperwork as we speak.
  • New projects are in discussions with the TAC to come under the Consortium umbrella. 

The TAC and Outreach Committee are now heads down developing the website, wiki, and GitHub sites to ensure policies and decisions are captured, documented, and public, and to improve our on-ramps and services to open source licensed projects in the confidential computing space. We’re working to create a User Council to engage with sophisticated large-scale users of confidential computing. It is an exciting time. 

Like any open source project, the Consortium is a continuously evolving and growing effort; evolving to meet the needs of the user and growing in the ways that meet these needs. Consortium meetings are open to anyone, and we welcome all– from those who are curious about what confidential computing is to open source projects curious about what the Consortium offers to security researchers on their umpteeth TEE disclosure–there is a seat waiting for you. To find meeting times, join our mailing lists.