Keylime: Pushing the Boundaries of Remote Attestation on the Edge
summary
Keylime moves from a pull-based verifier-driven model to a push-based agent-driven model, replacing per-node HTTP servers and 2s polling with agents that authenticate via proof-of-possession via TPM certify and negotiate evidence capabilities (TPM quotes, IMA and UEFI logs). Implementation uses TPM PCR quotes, AK challenges, and capability negotiation; work is split across upstream contributors and vendors. Result: smaller agent footprint, easier firewall-friendly deployment, better tolerance for intermittent connections; secure payload delivery remains off by default.
AI-written summary · about
chapters (8)
- 0:00Keylime intro and remote attestation
- 4:57What Keylime is and how it works
- 11:55Keylime’s architecture problems
- 17:23Agent-driven attestation changes
- 23:50Push model for edge deployments
- 25:19Open source improvements
- 28:37Keylime future
- 29:24Q&A on attestation
related talks
41mKeylime - An Open Source TPM Project for Remote Trust of IoT
43mKeylime - An Open Source TPM Project for Remote Trust.
49mKeylime: Bootstrapping and Maintaining Trust
46mToward Usable Open-Source Remote Attestation for Cloud and Edge
38mKeylime, Securing your Slice of the Cloud.
29mA Simple Protocol for Remote Attestation of System Integrity
20mCloud-native security in Rust with Keylime
24mFrom Trust Assumptions To Trust Evidence: Why PKI and Confidential Computing
