Why Current Approaches To "Shift-Left" Are A DevOps Antipattern
The primary purpose of any software-driven organization is to go faster, innovate and deliver greater value. While our customers have told us that security and compliance are vitally important, if done poorly, they feel that it can hinder innovation and slow down software delivery. This is the 'compliance tax' that must be paid and shift left approaches to software security only add to that tax.
In this session, Tim Johnson of CloudBees and Welly Siauw of AWS will present a model for calculating the security and compliance tax and how organizations can use that to change the organizational approach to security and compliance in a DevOps world.
Why "Shift-Left" is a DevOps anti-pattern
How to estimate the true costs of DevSecOps and Compliance work
The key solution attributes necessary to reduce or eliminate your Compliance Tax
Senior Product Marketing Manager - Cloudbees
Tim is a senior product marketing manager who focuses on the impact DevOps has on the people and the organizations adopting it. He has over a decade of product marketing experience with industry leaders such as Electric Cloud, BMC Software, Cisco, Google and SurfControl.
Principal Partner Solutions Architect, DevOps, AWS
Welly Siauw is a principal partner solutions architect at Amazon Web Services (AWS). He spends his day working with customers and partners, solving architectural challenges. He is passionate about service integration and orchestration, serverless and AI/ML. He has authored several AWS blogs and actively leads AWS Immersion Days and Activation Days.