Today's corporate security groups are not staffed to handle the specialized skills needed to perform code analysis and security testing from OpenStack. This discussion will focus on three areas: 1. Who should be responsible for testing (hint: a specialized group of ninjas; 2. Automating API and Code testing w/demo; how this translates into better code in OpenStack. There is a paradigm shift in how security testing is being conducted by software companies. The benefits of moving security testing away from an info-security" perspective will make security testing a repeatable process that is streamlined, more efficient, and more secure in OpenStack environment. "
Director, Quality and Security Engineering, Rackspace Hosting
Jim is a Director of Quality and Security Engineering at Rackspace. Jim has successfully built a team of specialized security engineers that is part of the development, quality, and delivery process at Rackspace. Jim felt that the best way to interconnect and ensure security testing was done correctly was to move security testing away from Corporate Security and move it into the quality organization. This new paradigm has melded the developer... Read More →