As developers we’re not always fully aware of security implications stipulated from changes to our code whether these are done in the CI, CD or an artifact database. It is always challenging to predict the impact of a changed 3rd party library, a security context or an RBAC permission, accessing a different network to the same resource or even using an API in a different way than we used to. Understanding the impact immediately and being able to make a change without disrupting the pipeline is therefore an important requirement. This session will present best practices to cope with these day to day changes and will propose a set of tools to address them cohesively.