Database Reference
In-Depth Information
run a service under the root privileges? Do you keep your firewall ports configured by de-
fault (it's still not a problem to find which are opened, but we do not want to give the bad
guys a chance to slack)? Still believe that WEP is unbreakable (in addition, allowing guest
WEP-based Wi-Fi access to corporate data)?
This sanity checklist is not complete, but we have no intention to publish a corporate red
topic with all security do's and don'ts.
Another noteworthy point is that you can play and have a lot of fun with honeypots and
honeynets, but please make sure that they are completely (better still, physically) separ-
ated from any of your actual environments.
There is no pattern called diligence or vigilance; that's the state of mind of security ops.
You, as an architect, must assist with the proper security configuration of the following
elements of the SOA infrastructure:
• Composition controllers and subcontrollers
• Concurrent contacts
• ESB / SG engines / agents
• Orchestration engines
In fact, every single element of your SOA infrastructure must not go amiss. An obvious
thing to say is that highly reusable components, service engines, and most common ser-
vice agents must be checked first and on a regular basis.
You also have to include into your Ops red topic (security response plan) and orange topic
(backup/recovery plan), a drill schedule, usually performed on your honeynet.
Sensitive data exposure
From a perspective of common sense, this is not a vulnerability, but primarily a negli-
gence similar to the security misconfiguration discussed earlier and quite common to web
applications (remember, we are not accusing anyone). However, for SOA, it has a broader
context. Data is not only exposed on static web via AJAX/REST API. More often than
not, it is insufficient crypto-strength or the lack of crypto-protection on sensitive elements
of a SOAP message.
Reliance on TLS when intermediaries are on the message path is another example of such
exposure, especially if the intermediary is active, that is, involved in message transforma-
tion. Even behind the Secure Gateway, in IPC-certified organizations, message data
should be encrypted all the way to the ultimate receiver.
Search WWH ::




Custom Search