SOA is hot and everyone wants to talk about how it’s going to fundamentally change the way applications are built, data is accessed and trading partners communicate. They may very well be right, and given that I do security and not application architecture, I’m not going to spend any time explaining the benefits of SOA. Since you are hanging out on eBizQ, you should know a bit about SOA already. But an overlooked factor in this SOA revolution is the security question -- how is SOA going to impact security and what needs to be done to ensure the integrity of corporate data in a SOA-based world?
What’s the big deal anyway? Why is SOA so much different than existing application architectures? In a nutshell, in a simplistic two or three tiered web application context, you pretty much know who is consuming data and whether they have the proper authorization to do so. But if you tack up a web services interface on some of these data sources, all hell breaks loose. Any application from anywhere can now make calls against the data.
To read the rest click here.
Leave a comment