Your current filters are…
Service-oriented architecture (SOA) defines an architectural style which promotes developing applications in a highly decoupled manner with a well defined service interface. The application level boundaries and technology differences are removed with the encouraged support for heterogeneity. Connecting heterogeneous applications together without jeopardizing security is
equally important. Conventional applications hard code it’s own security models - in other words - bake-in to the application it self. This doesn’t find to be the best fit in an SOA deployment.
Standards such as WS-Security, SAML, WS-Trust, WS-SecureConversation and WS-SecurityPolicy emerged over the years to define the ‘best-fit’ security model to an SOA deployment based on Web Services.
This session will cover patterns, best practices and threats associated with SOA security models
by Sander Temme
Enterprise installations of Apache are particularly attractive targets for malicious attacks including Denial of Service, defacement, theft of data or service and installation of zombies or viruses.
Hardening your deployment against such attacks calls for some special techniques and tactics.
Come to this session to learn about attack detection techniques, server protection, secure deployment of multiple servers, configuration of firewall "demilitarized zones" and judicious use of SSL encryption.
How do you deploy an off-the-shelf application that insists on writing to the file system?
And what steps do you take to securely deploy Apache on Windows or UNIX?
This presentation will explore solutions to these very real situations.
6th–11th November 2011