1 year ago

This is the last post in a three-part series on continuous security. In our previous posts, we talked about why Security as Code, security orchestration and continuous monitoring are the backbone of truly viable continuous security, the next phase of the CI/CD revolution. CISOs and CTOs alike need to recognize that the continuous security approach will be what enables engineering velocity, and not what hinders it, for elite engineering teams.

In this post, when referring to continuous security monitoring, the idea is to create a framework that is the security equivalent of continuous integration or deployment, aligned with modern DevOps and software delivery processes.

Embedding continuous security practices into your engineering serves to benefit security engineering, and vice versa, by ensuring that engineering organizations don’t destroy their culture and velocity with security requirements after the fact.