|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
Adopting an Enterprise Software Security Framework
March/April 2006 (vol. 4 no. 2)
pp. 84-87
| ASCII Text | x | ||
| John Steven, "Adopting an Enterprise Software Security Framework," IEEE Security & Privacy, vol. 4, no. 2, pp. 84-87, March/April, 2006. | |||
| BibTex | x | ||
| @article{ 10.1109/MSP.2006.33, author = {John Steven}, title = {Adopting an Enterprise Software Security Framework}, journal ={IEEE Security & Privacy}, volume = {4}, number = {2}, issn = {1540-7993}, year = {2006}, pages = {84-87}, doi = {http://doi.ieeecomputersociety.org/10.1109/MSP.2006.33}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Security & Privacy TI - Adopting an Enterprise Software Security Framework IS - 2 SN - 1540-7993 SP84 EP87 EPD - 84-87 A1 - John Steven, PY - 2006 KW - software KW - security KW - development VL - 4 JA - IEEE Security & Privacy ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MSP.2006.33
Most organizations no longer take for granted that their deployed applications are secure. But even after conducting penetration tests, network and hosting security personnel spend considerable time chasing incidents. Your organization might be one of the many that have realized the "secure the perimeter" approach doesn't stem the tide of incidents because the software it's building and buying doesn't resist attack. A new approach offers help across the enterprise.
Index Terms:
software, security, development
Citation:
John Steven, "Adopting an Enterprise Software Security Framework," IEEE Security & Privacy, vol. 4, no. 2, pp. 84-87, March-April 2006, doi:10.1109/MSP.2006.33
Usage of this product signifies your acceptance of the Terms of Use.