The DOI matches its Crossref record; 5 of the 5 references it cites were found in a registry or an index.
Software security
Abstract
Software security is the idea of engineering software so that it continues to function correctly under malicious attack. Most technologists acknowledge this undertaking's importance, but they need some help in understanding how to tackle it. The article aims to provide that help by exploring software security best practices. A central and critical aspect of the computer security problem is a software problem. Software defects with security ramifications, including implementation bugs such as buffer overflows and design flaws such as inconsistent error handling, promise to be with us for years. All too often, malicious intruders can hack into systems by exploiting software defects. Internet-enabled software applications present the most common security risk encountered today, with software's ever-expanding complexity and extensibility adding further fuel to the fire. By any measure, security holes in software are common, and the problem is growing.
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
Cites
Exploiting Software: How to Break Code
Hoglund, G., & McGraw, G. E. (2004) · Cited by 299
Self-citationBuilding secure software: how to avoid security problems the right way
Frazer, K. (2002) · ACM SIGSOFT Software Engineering Notes · doi:10.1145/511152.511169 · Cited by 268
From the ground up: the DIMACS software security workshop
McGraw, G. E. (2003) · IEEE Security & Privacy · doi:10.1109/msecp.2003.1193213 · Cited by 88
Self-citationInside the Windows security push
Howard, M., & Lipner, S. B. (2003) · IEEE Security & Privacy · doi:10.1109/msecp.2003.1176996 · Cited by 43
A call to action look beyond the horizon
Wing, J. M. (2003) · IEEE Security & Privacy · doi:10.1109/msecp.2003.1253571 · Cited by 25
Cited by
Security issues in cloud environments: a survey
Fernandes, D. A. B., Soares, L. F. B., Gomes, J. V., Freire, M. M., & Inácio, P. R. M. (2014) · International Journal of Information Security · doi:10.1007/s10207-013-0208-7 · Cited by 494
Security as a new dimension in embedded system design
Kocher, P., Lee, R., McGraw, G., Raghunathan, A., & Ravi, S. (2004) · Proceedings of the 41st annual Design Automation Conference · doi:10.1145/996566.996771 · Cited by 394
Self-citationA Survey of Vehicle to Everything (V2X) Testing
Wang, J., Shao, Y., Ge, Y., & Yu, R. (2019) · Sensors · doi:10.3390/s19020334 · Cited by 312
Arkin, B., Stender, S., & McGraw, G. (2005) · IEEE Security and Privacy Magazine · doi:10.1109/msp.2005.23 · Cited by 264
Self-citationWhat Is the Cyber Offense-Defense Balance? Conceptions, Causes, and Assessment
Slayton, R. (2017) · International Security · doi:10.1162/isec_a_00267 · Cited by 224
Metadata
- Authors
- Mcgraw, G.
- Venue
- IEEE Security & Privacy Magazine
- Published
- 2004-03
- Volume
- 2
- Issue
- 2
- Pages
- 80-83
- ISSN
- 1540-7993 (ISSN-L)
- OpenAlex
- W2294407885
- Cited by
- 509
- References
- 5
- FWCI
- 17.62
- Type
- journal article
- 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.