|
| This Article | ||
| | ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Steven M. Bellovin, "Security Think," IEEE Security & Privacy, vol. 9, no. 6, pp. 88, November/December, 2011. | |||
| BibTex | x | ||
| @article{ 10.1109/MSP.2011.172, author = {Steven M. Bellovin}, title = {Security Think}, journal ={IEEE Security & Privacy}, volume = {9}, number = {6}, issn = {1540-7993}, year = {2011}, pages = {88}, doi = {http://doi.ieeecomputersociety.org/10.1109/MSP.2011.172}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Security & Privacy TI - Security Think IS - 6 SN - 1540-7993 SP EP EPD - 88 A1 - Steven M. Bellovin, PY - 2011 KW - security education; secure system design VL - 9 JA - IEEE Security & Privacy ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MSP.2011.172
The author discusses the problem of how a security specialist should think. In particular, such a person should know how to evaluate complex systems and look for vulnerabilities created by interactions. It's hard to do, and even harder to teach.
Index Terms:
security education; secure system design
Citation:
Steven M. Bellovin, "Security Think," IEEE Security & Privacy, vol. 9, no. 6, pp. 88, Nov.-Dec. 2011, doi:10.1109/MSP.2011.172
Usage of this product signifies your acceptance of the Terms of Use.