论文标题

CASU:通过低端嵌入式系统的安全更新通过安全更新而折衷

CASU: Compromise Avoidance via Secure Update for Low-end Embedded Systems

论文作者

Nunes, Ivan De Oliveira, Jakkamsetti, Sashidhar, Kim, Youngil, Tsudik, Gene

论文摘要

确保嵌入式系统软件的运行时完整性是一个开放问题。安全性与其他优先事项(例如成本或绩效)之间的权衡是固有的,而解决这些问题既具有挑战性又重要。将恶意代码(例如,通过注射)引入嵌入式设备的运行时攻击的扩散引起了一系列缓解技术。一种流行的方法是远程证明(RA),通过该方法,一个受信任的实体(验证者)检查了不信任的远程设备(Prover)的当前软件状态。 RA产生了及时验证的称者状态的快照,验证者用来决定是否发生攻击。 当前的RA方案要求验证者根据一些不清楚的标准明确启动RA。因此,如果宣传的妥协,验证者只会在下一个RA实例上迟到。虽然足以妥协检测,但某些应用程序将受益于一种更加主动的,基于预防的方法。为此,我们通过安全更新构建CASU:避免折衷。 CASU是一种廉价的硬件/软件共同设计执行:(i)运行时软件不变性,因此排除了任何非法软件修改,以及(ii)身份验证的更新是修改软件的唯一手段。在CASU中,成功的RA实例可作为成功更新的证明,并且由于运行时不变性保证,连续后续的软件完整性是隐式的。这消除了在软件更新之间需要RA的必要性,并导致不引人注目的完整性保证,并保证与先前的RA技术相似,总体性能更好。

Guaranteeing runtime integrity of embedded system software is an open problem. Trade-offs between security and other priorities (e.g., cost or performance) are inherent, and resolving them is both challenging and important. The proliferation of runtime attacks that introduce malicious code (e.g., by injection) into embedded devices has prompted a range of mitigation techniques. One popular approach is Remote Attestation (RA), whereby a trusted entity (verifier) checks the current software state of an untrusted remote device (prover). RA yields a timely authenticated snapshot of prover state that verifier uses to decide whether an attack occurred. Current RA schemes require verifier to explicitly initiate RA, based on some unclear criteria. Thus, in case of prover's compromise, verifier only learns about it late, upon the next RA instance. While sufficient for compromise detection, some applications would benefit from a more proactive, prevention-based approach. To this end, we construct CASU: Compromise Avoidance via Secure Updates. CASU is an inexpensive hardware/software co-design enforcing: (i) runtime software immutability, thus precluding any illegal software modification, and (ii) authenticated updates as the sole means of modifying software. In CASU, a successful RA instance serves as a proof of successful update, and continuous subsequent software integrity is implicit, due to the runtime immutability guarantee. This obviates the need for RA in between software updates and leads to unobtrusive integrity assurance with guarantees akin to those of prior RA techniques, with better overall performance.

扫码加入交流群

加入微信交流群

微信交流群二维码

扫码加入学术交流群,获取更多资源