Trusted Hardware for Partitioned Multicore

1. Alexandra Constantin James Cook Anindya De Trusted Hardware for Partitioned Multicore Computer Science, UC Berkeley

2. What is a TPM? • TPM – Trusted Platform Module • Specs by Trusted Computing Group (TCG) • Stores secret keys to be used for cryptographic protocols and authentication

3. Release data only if running Vista ! • How to ascertain if the server is running Vista? • Trust TPM hardware and ask it for integrity measurements

4. Attestation TPM hardware is trusted AIK key pair AIK credential signed by trusted third party (privacy CA)

5. Boot Process BIOS boot block = Core Root of Trust Chain of trust Boot block rest of the bios OS, etc. Integrity measurements = hash of code to be loaded Signed hash of code used to establish trust

6. TPM for Bulk Decryption Ascertained that it is Bob Bob Alice

7. TPM for Bulk Decryption Pick K. Send Enc(K,PK) Bob Alice

8. TPM for Bulk Decryption Send Enc(K,Data) Bob Alice

9. Trade-offs in implementation • TPM hardware requirements to maintain efficiency for a system with many partitions? • When to hash? • Some simulation results

11. Issues with TPM protocols: • Privacy: Critical data to be hashed but source to remain undisclosed • Deflection attack: Server initially deflects communication to a TPM based server and later starts communication • Replay attacks : Continue to use certificate after switching OS • Snoopy attacks : Pry on the communication line for certificates and use them as your own

12. Non-network attacks • Have to trust some part of the kernel • DRAM is unsafe – freeze the computation • Pry on the system bus • Side Channel Attacks

13. Trusted Hardware for Partitioned Multicore • Efficiency issues – Is the system reasonable when there are 20 cores and 120 partitions? • Some partitions trusted and some untrusted • Cannot even think of timestamping to prevent replay • More privacy issues : Should not be able to ascertain two partitions are physically on the same computer

14. Virtual TPMs for Partitioned Multicore Multiple partitions hosting operating systems Virtual operating systems reside in virtual machines Changing partitions Virtualize TPMs Create one VTPM per partition Each VTPM has its own keys and resources and can replicate the functions of a real TPM A VTPM manager connects the VTPM instance and the OS partitions VTPM manager collects integrity measurements of VTPM instances

15. Virtualization of TPM • Virtualizing the TPM takes care of privacy issues • Chain of trust now goes through the virtual TPM • VTPM manager can give different privileges to different partitions. • Assurance on Quality of Service (QoS) can be given : we have a novel priority algorithm • Compromise of one partition ≠ Compromising the entire system

16. Hardware design for security TPM Secure DRAM Memory Encrypter Secure Box CPU

17. More security measures • Security unusually dependent on correctness of kernel • Use the Hi-Star labeling mechanism • There are categories and labels – {0,1,2,3} • Rules for information flow – function of category, label tuple • We have one Hi-star category for information flow from secure box to rest of the world

18. Cryptographic issues • RSA vs. ECC protocols • Advantages of ECC : smaller key size • RSA is a malleable encryption scheme – cannot use for signing • ECC arithmetic can be implemented very efficiently in hardware

19. Simulation results JAVA simulation of RSA and Elliptic curve cryptography

20. ECC FPGA Coprocessors for Improved Performance [Rebeiro and Mukhopadhyay] 3 main modules: ALU, register bank, control unit ALU components 14 cascaded circuits quad circuits, used for inversion Multiplier N x Squarer N x Adder Register Bank: 233 bit dual port registers; input to the registers = base point or output of ALU Control unit: Finite State Machine for 32 control signals Replicate coprocessor components according to partitioned multicore performance requirements

21. Use specialized hardware! Results from Software Simulation Results from Hardware simulation

22. Efficient implementation of primitives • Efficient implementation of finite field primitives is of central importance • Doubling a point on Elliptic curve: Can be done in 3 clock cycles (9 field multiplications) • Adding two points on elliptic curve: Can be done in 8 clock cycles (13 field multiplications)

23. Even more decisions? • Tradeoffs: chip area, time complexity, power • Even for basic multiplication (finite field or Zn), one can have the hardware scale as n(log3)/(log 2) and time as log n or have the hardware scale as n and time n(log3)/(log 2) • Circuits have been implemented in Verilog showing tradeoff