Anil Madhavapeddy suggests a different approach to building Internet services avoiding the complexity of today's services which incorporate many policies and security mechanisms.
Bruce Schneier of the famed Schneier on Security blog puts security in the context of our allegiances to cloud and SaaS providers, the recent news about PRISM and the lack of privacy for us as citizens.
Chris Haddad discusses cloud computing, PaaS, multi-tenancy, cloud ecosystems, cloud aware APIs from the perspective and the benefits it can provide to the business.
John Hughes explains how Quviq tests embedded ECU software for AUTOSAR compliance using QuickCheck.
Robert Winch explains how to secure a multi-tenant application with Spring Security and how to enable OAuth 2.
Mark Ryland presents and demoes identity and access management concepts as used in the cloud and EC2 security groups and packet networking inside the Amazon AWS.
Khawaja Shams presents how NASA’s JPL uses cloud computing, and evaluates some of the existing cloud computing myths in the MythBusters style.
Martin Thompson and Michael Barker explain how Intel x86_64 processors and their memory model work along with low-level techniques that help creating lock-free software.
While Cloud Computing offers increased business agility and reduced cost, many are worried about security: loss of control and lack of confidentiality. Presented by Alon Hazy and Jakob Illeborg Pagter, this talk looks at the threat landscape, then examines how to secure cloud solutions today and in the future.
Blake Dournaee presents Intel’s Service Gateway, a security control point meant to secure on-premise and in the cloud .NET or Java platforms from various security threats like spoofing, tampering, repudiation, information disclosure, DoS, elevation of privilege, all of that in the context of today’s REST or SOAP web services.
Harold van Aalst explains the need to use proper governance for SOA implementations by defining the rules, policies and standards to follow and having a tool to monitor them at runtime in order to discover when they are broken to be able to act on time. Beside the usual design-time governance, Aalst details on Development, Deployment and Runtime Governance.