The DOI matches its Crossref record.
Software Security: Building Security In
Abstract
Summary form only given. Software security has come a long way in the last few years, but we've really only just begun. I will present a detailed approach to getting past theory and putting software security into practice. The three pillars of software security are applied risk management, software security best practices (which I call touchpoints), and knowledge. By describing a manageably small set of touchpoints based around the software artifacts that you already produce, I avoid religious warfare over process and get on with the business of software security. That means you can adopt the touchpoints without radically changing the way you work. The touchpoints I will describe include: code review using static analysis tools; architectural risk analysis; penetration testing; security testing; abuse case development; and security requirements. Like the yin and the yang, software security requires a careful balance-attack and defense, exploiting and designing, breaking and building-bound into a coherent package. Create your own Security Development Lifecycle by enhancing your existing software development lifecycle with the touchpoints
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cited by
A survey of emerging threats in cybersecurity
Jang-Jaccard, J., & Nepal, S. (2014) · Journal of Computer and System Sciences · doi:10.1016/j.jcss.2014.02.005 · Cited by 892
Shin, Y., Meneely, A., Williams, L., & Osborne, J. A. (2011) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2010.81 · Cited by 607
Deng, M., Wuyts, K., Scandariato, R., Preneel, B., & Joosen, W. (2011) · Requirements Engineering · doi:10.1007/s00766-010-0115-7 · Cited by 533
Towards Achieving Data Security with the Cloud Computing Adoption Framework
Chang, V., & Ramachandran, M. (2016) · IEEE Transactions on Services Computing · doi:10.1109/tsc.2015.2491281 · Cited by 286
On cloud security requirements, threats, vulnerabilities and countermeasures: A survey
Kumar, R., & Goyal, R. (2019) · Computer Science Review · doi:10.1016/j.cosrev.2019.05.002 · Cited by 261
Model-based security engineering for cyber-physical systems: A systematic mapping study
Nguyen, P. H., Ali, S., & Yue, T. (2017) · Information and Software Technology · doi:10.1016/j.infsof.2016.11.004 · Cited by 107
Exploring software security approaches in software development lifecycle: A systematic mapping study
Mohammed, N. M., Niazi, M., Alshayeb, M., & Mahmood, S. (2017) · Computer Standards & Interfaces · doi:10.1016/j.csi.2016.10.001 · Cited by 104
Software security in DevOps: synthesizing practitioners' perceptions and practices
Ur Rahman, A. A., & Williams, L. (2016) · Proceedings of the International Workshop on Continuous Software Evolution and Delivery · doi:10.1145/2896941.2896946 · Cited by 86
Preliminary Findings about DevSecOps from Grey Literature
Mao, R., Zhang, H., Dai, Q., Huang, H., Rong, G., Shen, H., Chen, L., & Lu, K. (2020) · 2020 IEEE 20th International Conference on Software Quality, Reliability and Security (QRS) · doi:10.1109/qrs51102.2020.00064 · Cited by 49
Metadata
- Authors
- McGraw, G.
- Venue
- 2006 17th International Symposium on Software Reliability Engineering
- Publisher
- IEEE
- Published
- 2006-11
- Pages
- 6-6
- ISSN
- 1071-9458 (ISSN-L)
- OpenAlex
- W2015004885
- Cited by
- 785
- References
- 0
- Type
- conference abstract
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.