SoK: An Analysis of Protocol Design: Avoiding Traps for Implementation and Deployment

Abstract

Today’s Internet utilizes a multitude of different protocols. While some of these protocols were first implemented and used and later documented, other were first specified and then implemented. Regardless of how protocols came to be, their definitions can contain traps that lead to insecure implementations or deployments. A classical example is insufficiently strict authentication requirements in a protocol specification. The resulting Misconfigurations, i.e., not enabling strong authentication, are common root causes for Internet security incidents. Indeed, Internet protocols have been commonly designed without security in mind which leads to a multitude of misconfiguration traps. While this is slowly changing, to strict security considerations can have a similarly bad effect. Due to complex implementations and insufficient documentation, security features may remain unused, leaving deployments vulnerable. In this paper we provide a systematization of the security traps found in common Internet protocols. By separating protocols in four classes we identify major factors that lead to common security traps. These insights together with observations about enduser centric usability and security by default are then used to derive recommendations for improving existing and designing new protocols—without such security sensitive traps for operators, implementors and users.

2 Figures and Tables

Cite this paper

@article{Fiebig2016SoKAA, title={SoK: An Analysis of Protocol Design: Avoiding Traps for Implementation and Deployment}, author={Tobias Fiebig and Franziska Lichtblau and Florian Streibelt and Thorben Krueger and Pieter Lexis and Randy Bush and Anja Feldmann}, journal={CoRR}, year={2016}, volume={abs/1610.05531} }