You Get Where You're Looking for: The Impact of Information Sources on Code Security
By Yasemin Acar, Michael Backes, Sascha Fahl, Doowon Kim, Michelle L. Mazurek, Christian Stransky. IEEE Symposium on Security and Privacy, 2016
333 citations recorded by the source corpus.
Subfields: Artificial Intelligence, Information Systems, Signal Processing
View Paper: https://www.semanticscholar.org/paper/6b12cfb7875037cab4033bf0bdc50e184e6b2ae0
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Artificial Intelligence
- Michael W. Hicks
- Michael Backes
- Foutse Khomh
- Felix Fischer
- Huang Xiao
- Sascha Fahl
- Konstantin Böttinger
- Yasemin Acar
In Information Systems
- Michael W. Hicks
- Michael Backes
- Foutse Khomh
- Michelle L. Mazurek
- Jordan L. Boyd-Graber
- Joseph Bonneau
In Signal Processing
- Michael W. Hicks
- Michael Backes
- Foutse Khomh
- Michelle L. Mazurek
- Jordan L. Boyd-Graber
- Joseph Bonneau
Citations in the corpus
- Understanding security mistakes developers make: Qualitative analysis from Build It, Break It, Fix It (2020, background): “Further, prior work suggests that in at least some secure development studies, students can substitute effectively for professionals, as only security experience, not general development experience, is correlated with security outcomes [3, 4, 56, 58].”
- An Empirical Study of C++ Vulnerabilities in Crowd-Sourced Code Examples (2019, methodology): “Studies on Java Script [8], [39] and Android application [7], [40], [57] in Java and in Python [32] have shown the existence of security vulnerabilities in Stack Overflow code snippets reused in applications.”
- Stack Overflow Considered Harmful? The Impact of Copy&Paste on Android Application Security (2017, methodology): “we cannot guarantee that code snippets we detected originate from Stack Overflow with 100% certainty, the fact that Stack Overflow is the most popular Q&A site for Android developers and many of them heavily rely on the posted discussions and solutions [42] suggests Stack Overflow’s significant resp”
- Security Developer Studies with GitHub Users: Exploring a Convenience Sample (2017, methodology): “In a prior ex-periment, we found that about 20% of cryptographic tasks fell into this dangerous category [2].”