Bridging Security To the Cloud
Case Study: Vordel and Oracle present Best Practice Architecure for SOA - Five case study examples
Security must be applied to an SOA
Policies must be enforced (Runtime)
- Policies must be defined (Design Time)
- Control who can access the service
- Control how the service must behave
- Via Gateways (on the network)
- And via Agents (at the Services themselves)
Case Notes from a Vulnerability Assessment of a Bank’s Web Services
- What happened when a Bank allowed security experts to try to breach the protection of its Web Services
- How a vulnerability assessment of a bank's Web Services was undertaken.
- Established attack vectors are applied to the Web Services paradigm.
- Description of battery of tests and uncovered vulnerabilities are analyzed.
Security for AJAX and Web 2.0
- What is web 2.0
- Applying security to web 2.0
- How is XML security relevant for web 2.0
Security for REST Web Services
- What is "REST" anyway? How is it different from SOAP?
- Applying security to REST
- Reference architecture to protect both REST and SOAP
Mapping Security to an SOA
- what is a “Services Oriented Architecture” ?
- How do you go about creating a “Services Oriented Architecture”?
- Just how important are XML and SOAP for a Services Oriented Architecture ?