Transcription of Confidential Computing Deep Dive v1
{{id}} {{{paragraph}}}
Confidential Computing Deep Dive A Publication of The Confidential Computing Consortium October 2020. Contents 1 Introduction 3. 2 Confidential Computing 4. Definition 4. Why is Hardware Necessary for Confidential Computing 4. 3 Trusted Execution Environments (TEEs) 5. Properties 5. 4 Related Technologies 7. Security Comparisons 8. Scalability Comparisons 8. 5 Threat Model 9. Goal 9. Threat Vectors 10. In-Scope 10. Out-of-Scope 11. Side-Channels 11. Background 11. Example 11. Mitigation 12. 6 Attestation 13. Hardware-Based Attestation 13. Anonymity 14. TCB Recovery 14. 7 Conclusion 15. About the Confidential Computing Consortium 16. References 17. 1 Introduction In classical Computing , data exists in three states: in transit, at rest, and in use. Data traversing the network is in transit, data in storage is at rest, and data being processed is in use. In a world where we are constantly storing, consuming, and sharing sensitive data - from credit card data to medical records, from firewall configurations to our geolocation data - protecting sensitive data in all of its states is more critical than ever.
homomorphic encryption, or even (e.g., in [2] ) covering the entire space of protecting data in use. This diagram illustrates why we refer to confidential computing as protecting data in use by using a hardware-based TEE, to distinguish it from other techniques.
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document:
{{id}} {{{paragraph}}}