loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Building More Secure Software with Improved Development Processes
November-December 2004 (vol. 2 no. 6)
pp. 63-65
ASCII Text
x 
 
Michael Howard, "Building More Secure Software with Improved Development Processes," IEEE Security and Privacy, vol. 2, no. 6, pp. 63-65, November-December, 2004.
 
 
BibTex
x
 
@article{ 10.1109/MSP.2004.95,
author = {Michael Howard},
title = {Building More Secure Software with Improved Development Processes},
journal ={IEEE Security and Privacy},
volume = {2},
number = {6},
issn = {1540-7993},
year = {2004},
pages = {63-65},
doi = {http://doi.ieeecomputersociety.org/10.1109/MSP.2004.95},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Security and Privacy
TI - Building More Secure Software with Improved Development Processes
IS - 6
SN - 1540-7993
SP63
EP65
EPD - 63-65
A1 - Michael Howard,
PY - 2004
KW - software development
KW - security development lifecycle
KW - trustworthy computing initiative
VL - 2
JA - IEEE Security and Privacy
ER -
 
Michael Howard, Microsoft
In this installment, I draw on experiences gained as a member of Microsoft's central security team to outline some basic best practices you can implement in your software development process. These practices affected Microsoft products released since the inception of its Trustworthy Computing initiative in 2002.
Index Terms:
software development, security development lifecycle, trustworthy computing initiative
Citation:
Michael Howard, "Building More Secure Software with Improved Development Processes," IEEE Security and Privacy, vol. 2, no. 6, pp. 63-65, Nov. 2004, doi:10.1109/MSP.2004.95
Usage of this product signifies your acceptance of the Terms of Use.