The DOI matches its Crossref record.
Software security testing
Abstract
Testing software security is a commonly misunderstood task. Done properly, it goes deeper than simple black-box probing on the presentation layer (the sort performed by so-called application security tools) - and even beyond the functional testing of security apparatus. Testers must use risk-based approaches, grounded in both the system's architectural reality and the attacker's mindset, to gauge software security adequately. By identifying risks in the system and creating tests driven by those risks, a software security tester can properly focus on areas of code in which an attack is likely to succeed. This approach provides a higher level of software security assurance than is possible with classical black-box testing.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
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
Arkin, B., Stender, S., & McGraw, G. (2005) · IEEE Security and Privacy Magazine · doi:10.1109/msp.2005.23 · Cited by 264
Self-citationSoftware 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
A scenario-based framework for the security evaluation of software architecture
Alkussayer, A., & Allen, W. H. (2010) · 2010 3rd International Conference on Computer Science and Information Technology · doi:10.1109/iccsit.2010.5564015 · Cited by 22
Metadata
- Authors
- Potter, B., & McGraw, G.
- Venue
- IEEE Security & Privacy Magazine
- Published
- 2004-09
- Volume
- 2
- Issue
- 5
- Pages
- 81-85
- ISSN
- 1540-7993 (ISSN-L)
- OpenAlex
- W2126513753
- Cited by
- 233
- References
- 0
- FWCI
- 21.36
- 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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Software security testing. https://app.cochat.ai/papers/10.1109/msp.2004.84
- The paper
- Potter, B., & McGraw, G. (2004). Software security testing. IEEE Security & Privacy Magazine. https://doi.org/10.1109/msp.2004.84
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.