arXivDaily arXiv每日学术速递 周一至周五更新
arXiv 1907.01679cs.CR
收藏

构建它,打破它,修复它:争夺安全开发

Build It, Break It, Fix It: Contesting Secure Development

James Parker, Michael Hicks, Andrew Ruef, Michelle L. Mazurek, Dave Levin, Daniel Votipka, Piotr Mardziel, Kelsey R. Fulton

摘要:

典型的安全竞赛侧重于破坏或减轻有缺陷的系统的影响。我们推出了Build-it,Break-it,Fix-it(BIBIFI)竞赛,旨在评估安全构建软件的能力,而不仅仅是破坏它。在BIBIFI中,团队构建指定的软件,目标是最大限度地提高正确性,性能和安全性。当团队试图破坏其他团队的提交时,测试后者。优胜者是从最好的建设者和最好的破坏者中选出的。BIBIFI的设计是开放式的;团队可以使用任何他们喜欢的语言、工具、流程等。因此,竞赛结果揭示了与成功构建安全软件和破解不安全软件相关的因素。我们进行了三次竞赛,共涉及156个团队和三个不同的编程问题。从这些竞赛的定量分析发现,最有效的构建提交使用C/C++,但提交编码的静态类型的安全语言比C/C++提交的安全缺陷的可能性低11倍。同时也是成功的构建团队的突破团队在发现安全漏洞方面明显更好。

英文摘要:

Typical security contests focus on breaking or mitigating the impact of buggy systems. We present the Build-it, Break-it, Fix-it (BIBIFI) contest, which aims to assess the ability to securely build software, not just break it. In BIBIFI, teams build specified software with the goal of maximizing correctness, performance, and security. The latter is tested when teams attempt to break other teams' submissions. Winners are chosen from among the best builders and the best breakers. BIBIFI was designed to be open-ended; teams can use any language, tool, process, etc. that they like. As such, contest outcomes shed light on factors that correlate with successfully building secure software and breaking insecure software. We ran three contests involving a total of 156 teams and three different programming problems. Quantitative analysis from these contests found that the most efficient build-it submissions used C/C++, but submissions coded in a statically-type safe language were 11 times less likely to have a security flaw than C/C++ submissions. Break-it teams that were also successful build-it teams were significantly better at finding security bugs.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑