loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Four Ways to Improve Security
May/June 2005 (vol. 3 no. 3)
pp. 65-67
ASCII Text
x 
 
Brian Snow, "Four Ways to Improve Security," IEEE Security and Privacy, vol. 3, no. 3, pp. 65-67, May/June, 2005.
 
 
BibTex
x
 
@article{ 10.1109/MSP.2005.66,
author = {Brian Snow},
title = {Four Ways to Improve Security},
journal ={IEEE Security and Privacy},
volume = {3},
number = {3},
issn = {1540-7993},
year = {2005},
pages = {65-67},
doi = {http://doi.ieeecomputersociety.org/10.1109/MSP.2005.66},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Security and Privacy
TI - Four Ways to Improve Security
IS - 3
SN - 1540-7993
SP65
EP67
EPD - 65-67
A1 - Brian Snow,
PY - 2005
KW - software quality-control
KW - cryptographic primitives
KW - hardware assist
KW - separation mechanisms
VL - 3
JA - IEEE Security and Privacy
ER -
 
Brian Snow, US National Security Agency
Many of today's commercial IT security products aren't as secure as they need to be. In fact, it's been this way from the beginning of the emergence of security products. Yet, processes and techniques ranging from the near horizon to over the horizon (still a gleam in a researcher's eye) could dramatically improve the situation. To get there, customers must demand more from vendors today to get the security they?ll need in the products they'll buy tomorrow.
Index Terms:
software quality-control, cryptographic primitives, hardware assist, separation mechanisms
Citation:
Brian Snow, "Four Ways to Improve Security," IEEE Security and Privacy, vol. 3, no. 3, pp. 65-67, May/June 2005, doi:10.1109/MSP.2005.66
Usage of this product signifies your acceptance of the Terms of Use.