The Community for Technology Leaders
2018 IEEE Cybersecurity Development (SecDev) (2018)
Cambridge, MA, USA
Sept 30, 2018 to Oct 2, 2018
ISBN: 978-1-5386-7662-2
pp: 130-131
ABSTRACT
Traditionally, methods such as binary analysis, symbolic execution, and fuzzing have been used in a context that is strongly geared towards discovering existing vulnerabilities, rather than use in the development cycle to prevent vulnerabilities from arising. Unit testing, in contrast, is firmly in place as part of the development cycle, but is usually very limited in its ability to explore "deep" paths in a system, or expose completely un-anticipated aspects of system behavior. Incorporating the tools used for vulnerability discovery into the development cycle requires large expansion in the expertise that developers must possess, and significant changes in their practices. DeepState is an open-source tool that provides a Google Test-like API to give C and C++ developers push-button access to symbolic execution engines, such as Manticore and angr, and fuzzers, such as Dr. Fuzz. Rather than learning multiple complex tools, developers can learn one (familiar) interface for defining a test harness, and can use tools built to find security vulnerabilities to automatically generate more powerful unit tests for software, in an approach that merges traditional unit testing, security analysis methods, and property-based testing. This tutorial will show how to use DeepState in development, including to produce complex library and API tests, and how to take advantage of both the ability to easily apply multiple security-oriented back-ends for test generation during development and the novel strategies for improving back-end performance provided by DeepState.
INDEX TERMS
application program interfaces, program testing, security of data
CITATION

P. Goodman, G. Grieco and A. Groce, "Tutorial: DeepState: Bringing Vulnerability Detection Tools into the Development Cycle," 2018 IEEE Cybersecurity Development (SecDev), Cambridge, MA, USA, 2018, pp. 130-131.
doi:10.1109/SecDev.2018.00028
249 ms
(Ver 3.3 (11022016))