loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Knowledge for Software Security
March/April 2005 (vol. 3 no. 2)
pp. 74-78
ASCII Text
x 
 
Sean Barnum, Gary McGraw, "Knowledge for Software Security," IEEE Security and Privacy, vol. 3, no. 2, pp. 74-78, March/April, 2005.
 
 
BibTex
x
 
@article{ 10.1109/MSP.2005.45,
author = {Sean Barnum and Gary McGraw},
title = {Knowledge for Software Security},
journal ={IEEE Security and Privacy},
volume = {3},
number = {2},
issn = {1540-7993},
year = {2005},
pages = {74-78},
doi = {http://doi.ieeecomputersociety.org/10.1109/MSP.2005.45},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Security and Privacy
TI - Knowledge for Software Security
IS - 2
SN - 1540-7993
SP74
EP78
EPD - 74-78
A1 - Sean Barnum,
A1 - Gary McGraw,
PY - 2005
KW - software development cycle
KW - software security
VL - 3
JA - IEEE Security and Privacy
ER -
 
Sean Barnum, Cigital
Gary McGraw, Cigital
A critical challenge facing software security today is the dearth of experienced practitioners. Approaches that rely solely on apprenticeship as a method of propagation won't scale quickly enough to address this burgeoning problem, so as the field evolves and establishes best practices, knowledge management can play a central role in encapsulating and spreading the emerging discipline more efficiently. This article is about the kinds of security knowledge that can provide a solid foundation for software security practices.
Index Terms:
software development cycle, software security
Citation:
Sean Barnum, Gary McGraw, "Knowledge for Software Security," IEEE Security and Privacy, vol. 3, no. 2, pp. 74-78, Mar./Apr. 2005, doi:10.1109/MSP.2005.45
Usage of this product signifies your acceptance of the Terms of Use.