loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Software Security and SOA: Danger, Will Robinson!
January/February 2006 (vol. 4 no. 1)
pp. 80-83
ASCII Text
x 
 
Jeremy Epstein, Scott Matsumoto, Gary McGraw, "Software Security and SOA: Danger, Will Robinson!," IEEE Security and Privacy, vol. 4, no. 1, pp. 80-83, January/February, 2006.
 
 
BibTex
x
 
@article{ 10.1109/MSP.2006.23,
author = {Jeremy Epstein and Scott Matsumoto and Gary McGraw},
title = {Software Security and SOA: Danger, Will Robinson!},
journal ={IEEE Security and Privacy},
volume = {4},
number = {1},
issn = {1540-7993},
year = {2006},
pages = {80-83},
doi = {http://doi.ieeecomputersociety.org/10.1109/MSP.2006.23},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Security and Privacy
TI - Software Security and SOA: Danger, Will Robinson!
IS - 1
SN - 1540-7993
SP80
EP83
EPD - 80-83
A1 - Jeremy Epstein,
A1 - Scott Matsumoto,
A1 - Gary McGraw,
PY - 2006
KW - service-oriented architecture
KW - SOA
KW - security
VL - 4
JA - IEEE Security and Privacy
ER -
 
Jeremy Epstein, webMethods
Scott Matsumoto, Cigital
Gary McGraw, Cigital
The current buzzword of choice among the technical elite (at least those subject to marketing departments) is service-oriented architecture, or SOA (pronounced "SO-uh"). As SOA moves from hype to practice, an opportunity exists to do security right, but a similar opportunity exists for disaster if security is done wrong. This article describes 13 snares that we must avoid to end up with SOA security that makes sense.
Index Terms:
service-oriented architecture, SOA, security
Citation:
Jeremy Epstein, Scott Matsumoto, Gary McGraw, "Software Security and SOA: Danger, Will Robinson!," IEEE Security and Privacy, vol. 4, no. 1, pp. 80-83, Jan./Feb. 2006, doi:10.1109/MSP.2006.23
Usage of this product signifies your acceptance of the Terms of Use.