SOA risks and rewards

From Wiki

Web services mean we can build applications out of distributed systems, encouraging re-use and architectural agility. But when machines talk to machines, there are more and more opportunities for attack. What are the risks of an SOA architecture, and what can we do to defend against them?

We (Transition IT and our associates) are looking at security from a different perspective. We work to protect the backend database down to the individual user, location, machine, security clearance, etc., as well as also protecting the "endpoint", the network card, USB device, Wireless, Infrared, Bluetooth devices so that we have determined (externally) that the user has been validated to "see" the data and that what s(he) sees cannot be copied, printed, or compromised, especially when the user is physically outside the Enterprise. Hope to hear discussion about this approach at the Unconference.

[edit] Experts

Michael Davis, CEO Savid Technologies, Inc. Colin MacKinnon, CEO Transition IT, LLC