2007 | ||
---|---|---|
39 | EE | Gary McGraw: Exploiting Online Games. USENIX Annual Technical Conference 2007 |
2006 | ||
38 | EE | Gary McGraw: Software Security: Building Security In. ISSRE 2006: 6 |
37 | EE | Jeremy Epstein, Scott R. Matsumoto, Gary McGraw: Software Security and SOA: Danger, Will Robinson! IEEE Security & Privacy 4(1): 80-83 (2006) |
2005 | ||
36 | EE | Brad Arkin, Scott Stender, Gary McGraw: Software Penetration Testing. IEEE Security & Privacy 3(1): 84-87 (2005) |
35 | EE | Sean Barnum, Gary McGraw: Knowledge for Software Security. IEEE Security & Privacy 3(2): 74-78 (2005) |
34 | EE | Dan Taylor, Gary McGraw: Adopting a Software Security Improvement Program. IEEE Security & Privacy 3(3): 88-91 (2005) |
33 | EE | Nancy R. Mead, Gary McGraw: A Portal for Software Security. IEEE Security & Privacy 3(4): 75-79 (2005) |
32 | EE | Kenneth R. van Wyk, Gary McGraw: Bridging the Gap between Software Development and Information Security. IEEE Security & Privacy 3(5): 75-79 (2005) |
31 | EE | Katrina Tsipenyuk, Brian Chess, Gary McGraw: Seven Pernicious Kingdoms: A Taxonomy of Software Security Errors. IEEE Security & Privacy 3(6): 81-84 (2005) |
2004 | ||
30 | EE | Gary McGraw: Software Security Clue Distribution. CSEE&T 2004: 6-7 |
29 | EE | Srivaths Ravi, Paul C. Kocher, Ruby B. Lee, Gary McGraw, Anand Raghunathan: Security as a new dimension in embedded system design. DAC 2004: 753-760 |
28 | EE | Gary McGraw: Exploiting Software. USENIX Security Symposium 2004 |
27 | EE | Gary McGraw: Software Security. IEEE Security & Privacy 2(2): 80-83 (2004) |
26 | EE | Noopur Davis, Watts S. Humphrey, Samuel T. Redwine Jr., Gerlinde Zibulski, Gary McGraw: Processes for Producing Secure Software: Summary of US National Cybersecurity Summit Subgroup Report. IEEE Security & Privacy 2(3): 18-25 (2004) |
25 | EE | Paco Hope, Gary McGraw, Annie I. Antón: Misuse and Abuse Cases: Getting Past the Positive. IEEE Security & Privacy 2(3): 90-92 (2004) |
24 | EE | Ivaan Arce, Gary McGraw: Guest Editors' Introduction: Why Attacking Systems Is a Good Idea. IEEE Security & Privacy 2(4): 17-19 (2004) |
23 | EE | Denis Verdon, Gary McGraw: Risk Analysis in Software Design. IEEE Security & Privacy 2(4): 79-84 (2004) |
22 | EE | Gary McGraw, Bruce Potter: Software Security Testing. IEEE Security & Privacy 2(5): 81-85 (2004) |
21 | EE | Brian Chess, Gary McGraw: Static Analysis for Security. IEEE Security & Privacy 2(6): 76-79 (2004) |
2003 | ||
20 | EE | Gary McGraw: From the Ground Up: The DIMACS Software Security Workshop. IEEE Security & Privacy 1(2): 59-66 (2003) |
2002 | ||
19 | EE | John Viega, J. T. Bloch, Tadayoshi Kohno, Gary McGraw: Token-based scanning of source code for security problems. ACM Trans. Inf. Syst. Secur. 5(3): 238-261 (2002) |
18 | Gary McGraw: On Bricks and Walls: Why Building Secure Software is Hard. Computers & Security 21(3): 229-238 (2002) | |
17 | EE | Gary McGraw: Managing Software Security Risks. IEEE Computer 35(4): 99-101 (2002) |
16 | EE | Greg Hoglund, Gary McGraw: Point/Counterpoint: Security Band-Aids: More Cost-Effective than "Secure" Coding / Building Secure Software: Better than Protecting Bad Software. IEEE Software 19(6): 56-59 (2002) |
2001 | ||
15 | EE | Christoph C. Michael, Gary McGraw, Michael Schatz: Generating Software Test Data by Evolution. IEEE Trans. Software Eng. 27(12): 1085-1110 (2001) |
2000 | ||
14 | EE | John Viega, J. T. Bloch, Y. Kohno, Gary McGraw: ITS4: A Static Vulnerability Scanner for C and C++ Code. ACSAC 2000: 257- |
13 | EE | Gary McGraw: Will Openish Source Really Improve Security. IEEE Symposium on Security and Privacy 2000: 128-129 |
12 | EE | Gary McGraw, J. Gregory Morrisett: Attacking Malicious Code: A Report to the Infosec Research Council. IEEE Software 17(5): (2000) |
11 | EE | Ross J. Anderson, Terry Bollinger, Doug Brown, Enrique Draier, Philip Machanick, Gary McGraw, Nancy R. Mead, Arthur B. Pyster, Howard Schmidt, Timothy J. Shimeall: Roundtable on Information Security Policy. IEEE Software 17(5): (2000) |
10 | EE | John Viega, Tom Mutdosch, Gary McGraw, Edward W. Felten: Statically Scanning Java Code: Finding Security Vulnerabilities. IEEE Software 17(5): (2000) |
1999 | ||
9 | Gary McGraw: Software Assurence for Security. IEEE Computer 32(4): 103-105 (1999) | |
1998 | ||
8 | EE | Christoph C. Michael, Gary McGraw: Automated Software Test Data Generation for Complex Programs. ASE 1998: 136-146 |
7 | EE | Anup K. Ghosh, Tom O'Connor, Gary McGraw: An Automated Approach for Identifying Potential Vulnerabilities in Software. IEEE Symposium on Security and Privacy 1998: 104-114 |
6 | EE | Gary McGraw: Weak links in e-commerce security: examples from the field. NDSS 1998 |
5 | Gary McGraw, Edward W. Felten: Mobile Code and Security - Guest Editors' Introduction. IEEE Internet Computing 2(6): 26-29 (1998) | |
1997 | ||
4 | EE | Christoph C. Michael, Gary McGraw, Michael Schatz, C. C. Walton: Genetic Algorithms for Dynamic Test Data Generation. ASE 1997: 307-308 |
3 | Jeffrey M. Voas, Gary McGraw, Lora Kassab, Larry Voas: A 'Crystal Ball' for Software Liability. IEEE Computer 30(6): 29-36 (1997) | |
2 | Jeffrey M. Voas, Frank Charron, Gary McGraw, Keith W. Miller, Michael Friedman: Predicting How Badly ``Good'' Software Can Behave. IEEE Software 14(4): 73-83 (1997) | |
1993 | ||
1 | Gary McGraw, Douglas Hofstadter: Letter Spirit: An Architecture for Creativity in an Microdomain. AI*IA 1993: 65-70 |