Hit papers significantly outperform the citation benchmark for their cohort. A paper qualifies
if it has ≥500 total citations, achieves ≥1.5× the top-1% citation threshold for papers in the
same subfield and year (this is the minimum needed to enter the top 1%, not the average
within it), or reaches the top citation threshold in at least one of its specific research
topics.
Software Security: Building Security In
2006386 citationsGary McGrawCERN Document Server (European Organization for Nuclear Research)profile →
Author Peers
Peers are selected by citation overlap in the author's most active subfields.
citations ·
hero ref
This map shows the geographic impact of Gary McGraw's research. It shows the number of citations coming from papers published by authors working in each country. You can also color the map by specialization and compare the number of citations received by Gary McGraw with the expected number of citations based on a country's size and research output (numbers larger than one mean the country cites Gary McGraw more than expected).
This network shows the impact of papers produced by Gary McGraw. Nodes represent research fields, and links connect fields that are likely to share authors. Colored nodes show fields that tend to cite the papers produced by Gary McGraw. The network helps show where Gary McGraw may publish in the future.
Co-authorship network of co-authors of Gary McGraw
This figure shows the co-authorship network connecting the top 25 collaborators of Gary McGraw.
A scholar is included among the top collaborators of Gary McGraw based on the total number of
citations received by their joint publications. Widths of edges
represent the number of papers authors have co-authored together.
Node borders
signify the number of papers an author published with Gary McGraw. Gary McGraw is excluded from
the visualization to improve readability, since they are connected to all nodes in the network.
McGraw, Gary. (2015). Software security and the building security in maturity model (BSIMM). Journal of computing sciences in colleges. 30(3). 7–8.6 indexed citations
Allen, Julia, Sean Barnum, Robert J. Ellison, Gary McGraw, & Nancy R. Mead. (2008). Software Security Engineering: A Guide for Project Managers (The SEI Series in Software Engineering).1 indexed citations
McGraw, Gary. (2006). Software Security: Building Security In. CERN Document Server (European Organization for Nuclear Research). 6–6.386 indexed citations breakdown →
12.
Pullen, Sam, et al.. (2005). Investigation of Common Architectures for Land- and Sea-Based JPALS. Proceedings of the 18th International Technical Meeting of the Satellite Division of The Institute of Navigation (ION GNSS 2005). 26–37.3 indexed citations
13.
Hoglund, Greg & Gary McGraw. (2002). Point/Counterpoint: Security Band-Aids: More Cost-Effective than "Secure" Coding / Building Secure Software: Better than Protecting Bad Software.. IEEE Software. 19. 56–59.1 indexed citations
14.
McGraw, Gary & Edward W. Felten. (1999). Securing Java: getting down to business with mobile code. John Wiley & Sons, Inc. eBooks.86 indexed citations
15.
McGraw, Gary & Edward W. Felten. (1998). Mobile Code and Security. IEEE Internet Computing. 2(6). 26–29.1 indexed citations
16.
Ghosh, A. K. & Gary McGraw. (1998). An Approach for Certifying Security in Software Components. 12(19). 1–2, 5.9 indexed citations
17.
McGraw, Gary & Edward W. Felten. (1997). Java security: hostile applets, holes&antidotes. John Wiley & Sons, Inc. eBooks.51 indexed citations
18.
Voas, Jeffrey & Gary McGraw. (1997). Software fault injection: inoculating programs against errors. John Wiley & Sons, Inc. eBooks.178 indexed citations
19.
Hofstadter, Douglas R. & Gary McGraw. (1995). Letter Spirit: esthetic perception and creative play in the rich microcosm of the Roman alphabet. 407–466.11 indexed citations
Rankless uses publication and citation data sourced from OpenAlex, an open and comprehensive
bibliographic database. While OpenAlex provides broad and valuable coverage of the global
research landscape, it—like all bibliographic datasets—has inherent limitations. These include
incomplete records, variations in author disambiguation, differences in journal indexing, and
delays in data updates. As a result, some metrics and network relationships displayed in
Rankless may not fully capture the entirety of a scholar's output or impact.