Why Secure Applications are Difficult to Write

	This Article
	Subscribers, please Login Purchase article: $19 PDF HTML IEEE Xplore Subscribers RSS feed
	Share
	Email this Article to a friend
	Bibliographic References
	ASCII Text BibTex RefWorks Procite/RefMan/Endnote
	Add to:
	Digg Furl Spurl Blink Simpy Google Del.icio.us Y!MyWeb
	Search
	Similar Articles Articles by James Whittaker

March-April 2003 (vol. 1 no. 2)

pp. 81-83

	ASCII Text	x
	James Whittaker, "Why Secure Applications are Difficult to Write," IEEE Security and Privacy, vol. 1, no. 2, pp. 81-83, March-April, 2003.

	BibTex	x
	@article{ 10.1109/MSECP.2003.1193218, author = {James Whittaker}, title = {Why Secure Applications are Difficult to Write}, journal ={IEEE Security and Privacy}, volume = {1}, number = {2}, issn = {1540-7993}, year = {2003}, pages = {81-83}, doi = {http://doi.ieeecomputersociety.org/10.1109/MSECP.2003.1193218}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, }

	RefWorks Procite/RefMan/Endnote	x
	TY - MGZN JO - IEEE Security and Privacy TI - Why Secure Applications are Difficult to Write IS - 2 SN - 1540-7993 SP81 EP83 EPD - 81-83 A1 - James Whittaker, PY - 2003 VL - 1 JA - IEEE Security and Privacy ER -

James Whittaker

DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MSECP.2003.1193218

The authors discuss software security as an awareness issue, because software that is unaware of its potential vulnerabilities has no chance of being secure. Only by being aware of potential threats and using vigilant defensive countermeasures can we hope to write secure applications, and we can only achieve security through awareness and understanding of these issues.

Citation:

James Whittaker, "Why Secure Applications are Difficult to Write," IEEE Security and Privacy, vol. 1, no. 2, pp. 81-83, Mar. 2003, doi:10.1109/MSECP.2003.1193218

Peer Review Notice | Give Us Feedback

Usage of this product signifies your acceptance of the Terms of Use.