Continuous Security


In today’s fast and ‘ continuous development’ – cycle security is forced, but most of the time failing, to keep up with this pace. Security is almost all the time implemented as “hurdle” after releasing which needs to be taken before we can go to production. Being included after the fact means that you have to catch up on design and implementation before you can test for security related issues. By integrating security in the CI/CD pipeline and in our daily work flow it will be involved throughout the whole life cycle of the development of a feature and thus security can and will be involved from inception of a feature.

Open development