Web Services to aid DOS attacks
The development of web services standards allows us to contemplate the creation of business applications that are based upon collections of loosely-coupled components served up by a variety of third parties. The question that arises is just who it is that is going to expose themselves to denial of service attacks in this way.
There are many reasons why web services activity is currently restricted to use within the intranet. Mainly, the lack of experience dictates that most development is experimental. Also, there is a shortage of security and manageability within the standards that makes the publication of web services outside the firewall a pretty scary option.
However, if we look forward to a time when these wrinkles have been ironed out, we can see an opportunity for publicly exposed functions to be used to swamp the servers that host them.
The nice thing about the web services standards is that they are designed to help an outside party who wants to find and execute a piece of functionality.
First of all, UDDI will help your attacker to find any services that have been published within the networked environment and then WSDL will provide the details required to make it work.
With the aid of a little SOAP, the service can be executed on the host server and the DOS attack has begun. Swamp the web services with requests and there's a pretty good chance that the servers will fall flat on their backs.
We can argue, of course, that nobody will even contemplate the global publication of web services until a cosy wrapper of security exists around them. However, there needs to be strong identity management that ensures that the host trusts us before giving out the information needed to execute the functions.
One obvious solution is a directory implementation that requires the user is properly authenticated before even knowing which services are available.
This does defeat the idea that any component can be available to anybody but it is only the technology purists that believe this to be practical. A directory offers the foundation required to implement the management features necessary.
In the real world, even globally available web services are going to need registration information - not only for security purposes but also to make sure that users pay for their use. You didn't really think you'd get all this for free. Did you?
Sponsored: Fast data protection ROI?