loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Caution: This Product Contains Security Code
September-October 2003 (vol. 1 no. 5)
pp. 86-88
ASCII Text
x 
 
Martin Stytz, James A. Whittaker, "Caution: This Product Contains Security Code," IEEE Security and Privacy, vol. 1, no. 5, pp. 86-88, September-October, 2003.
 
 
BibTex
x
 
@article{ 10.1109/MSECP.2003.1236243,
author = {Martin Stytz and James A. Whittaker},
title = {Caution: This Product Contains Security Code},
journal ={IEEE Security and Privacy},
volume = {1},
number = {5},
issn = {1540-7993},
year = {2003},
pages = {86-88},
doi = {http://doi.ieeecomputersociety.org/10.1109/MSECP.2003.1236243},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Security and Privacy
TI - Caution: This Product Contains Security Code
IS - 5
SN - 1540-7993
SP86
EP88
EPD - 86-88
A1 - Martin Stytz,
A1 - James A. Whittaker,
PY - 2003
VL - 1
JA - IEEE Security and Privacy
ER -
 
Martin Stytz, US Air Force Research Laboratory
James A. Whittaker, Florida Tech

Traditionally, software developers have written functional code and error code. Now they must consider writing a third type of code, security code. Unfortunately, few programmers have learned the intricacies of developing security code. In this article, the authors look at today's security coding environment and suggest some research approaches to advance programmers' capabilities in this challenging arena.

Citation:
Martin Stytz, James A. Whittaker, "Caution: This Product Contains Security Code," IEEE Security and Privacy, vol. 1, no. 5, pp. 86-88, Sept. 2003, doi:10.1109/MSECP.2003.1236243
Usage of this product signifies your acceptance of the Terms of Use.