Trusted Computing Methods and Security
- Level
- Graduate
- Status
- Under development
Note: this course is still being designed and calibrated; the page content is for reference and does not represent the final teaching version.
Syllabus
Course Overview
Trusted Computing Methods and Security studies how to establish, transfer, and verify trust in partially trusted systems. Topics include TPMs, TEEs, remote attestation, secure boot, key sealing, supply-chain provenance, and the limitations of trusted execution.
This is a graduate topic course at the intersection of hardware security, virtualization, and applied cryptography.
Prerequisites
- System security, applied cryptography, and architecture fundamentals.
- Understanding of keys, certificates, and boot chains.
- Ability to read systems research papers.
Learning Outcomes
- Explain roots of trust, measured boot, and remote attestation.
- Evaluate TPM, TEE, and virtualization trust boundaries.
- Design key sealing, policy binding, and attestation-verification flows.
- Analyze side-channel and rollback risks in trusted execution.
- Build a small trusted-computing prototype or audit report.
Course Format
- Two meetings per week: one for core concepts and one for labs, paper discussion, or project review.
- The course proceeds over 16 weeks, each with a checkable assignment, lab, or project milestone.
- Reproducibility is required: code, configuration, data, lab logs, and reports must be reviewable by staff or peers.
Weekly Plan
Roots of trust and threat models
Define trust assumptions for a deployment scenario.
Roots of trust and threat models: lab and review
Define trust assumptions for a deployment scenario. Complete the paired lab, record issues, and explain design tradeoffs in class review.
TPMs, PCRs, and measured boot
Experiment with PCR extension and measurement logs.
TPMs, PCRs, and measured boot: lab and review
Experiment with PCR extension and measurement logs. Complete the paired lab, record issues, and explain design tradeoffs in class review.
Secure boot and key sealing
Design key-release policies and rollback protection.
Secure boot and key sealing: lab and review
Design key-release policies and rollback protection. Complete the paired lab, record issues, and explain design tradeoffs in class review.
Remote attestation protocols
Implement an attestation verifier prototype.
Remote attestation protocols: lab and review
Implement an attestation verifier prototype. Complete the paired lab, record issues, and explain design tradeoffs in class review.
TEEs and trusted-execution boundaries
Analyze enclave TCB and interface risks.
TEEs and trusted-execution boundaries: lab and review
Analyze enclave TCB and interface risks. Complete the paired lab, record issues, and explain design tradeoffs in class review.
Virtualization and cloud trust
Evaluate confidential-computing claims.
Virtualization and cloud trust: lab and review
Evaluate confidential-computing claims. Complete the paired lab, record issues, and explain design tradeoffs in class review.
Supply-chain provenance and policy automation
Connect build provenance, signatures, and deployment policy.
Supply-chain provenance and policy automation: lab and review
Connect build provenance, signatures, and deployment policy. Complete the paired lab, record issues, and explain design tradeoffs in class review.
Limits of trusted computing and report
Submit prototype, security analysis, and limitations.
Limits of trusted computing and report: lab and review
Submit prototype, security analysis, and limitations. Complete the paired lab, record issues, and explain design tradeoffs in class review.
Assessment
Concept questions, reading responses, design tasks, and small programming or lab exercises.
Trusted-computing prototype, policy design, security analysis, and paper review.
Participation in discussions, demos, code or paper reviews, and peer feedback.
Submit reproducible artifacts, a technical report, and a demo explaining methods, results, limitations, and future work.
Course Project
Projects may implement remote attestation, TPM key sealing, TEE application audit, or supply-chain provenance policy.
Policies
- AI tools are allowed, but generated code, lab notes, and design suggestions must be reviewed by the student and disclosed in the report.
- Students may not submit code, proofs, configuration, or experimental results they cannot explain; each member must defend their own design, tests, and tradeoffs.
- Late work affects iteration grades, but the course values reproducible, auditable, and maintainable results over last-minute accumulation.
Reference Courses
International
- CMU15-793: Secure Computer Systems
- ETH ZurichSystem Security — SECTRS Group
- ETH ZurichTrusted Computing 研究方向
- MITTrusted Computing @ MIT CSAIL
- MIT6.5950 Secure Hardware Design(含 TEE)
- StanfordCS 155: Computer and Network Security(含处理器/TEE安全)
- University of MichiganEECS 598-12: Hardware Security
China 985 Universities
- 上海交通大学网络空间安全学院本科培养体系
- 中国科学技术大学可信融合课题组(IoT安全与可信计算)
- 北京大学高可信软件技术教育部重点实验室
- 清华大学可信网络与系统研究所