Lessons Learned in Game Development for Crowdsourced Software Formal Verification
Lessons Learned in Game Development for Crowdsourced Software Formal Verification
复制标题
众包软件形式验证游戏开发中的经验教训
DOI:
--
复制
发表时间:
2015
期刊:
影响因子:
--
通讯作者:
T. Maddern
中科院分区:
文献类型:
--
作者:
Drew Dean;Sean Gaurino;Leonard Eusebi;A. Keplinger;Christopher Ganas;Timothy Pavlik;Ronald J. Watro;Aaron Cammarata;John T. Murray;Kelly McLaughlin;J. Cheng;T. Maddern
Introduction The history of formal methods and computer security research is long and intertwined. Program logics that were in theory capable of proving security properties of software were developed by the early 1970s [1]. The development of the first security models [2-4] gave rise to a desire to prove that the models did, in fact, enforce the properties that they claimed to, and that an actual implementation of the model was correct with respect to its specification [5; 6]. Optimism reached its peak in the early to mid-1980s [7-11], and the peak of formal methods for security was reached shortly before the publication of the Orange Book [12], where the certification of a system at class A1 required formal methods. Formal verification of software was considered the gold standard evidence that the software enforced a particular set of properties. Soon afterwards, the costs of formal methods, in both time and money, became all too apparent. Mainstream computer security research shifted focus to analysis of cryptographic protocols (e.g. [13; 14]), policies around cryptographic key management [15], and clever fixes for security problems found in contemporary systems [16-19].