From the course: DevSecOps: Building a Secure Continuous Delivery Pipeline

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Keeping security in operate

Keeping security in operate

From the course: DevSecOps: Building a Secure Continuous Delivery Pipeline

Start my 1-month free trial

Keeping security in operate

- [Instructor] The runtime state of the application is where users interact with, or consume the application. This is where we operate our application or service or, put simply, runtime is our application in production. Runtime is often the most forgotten place of the pipeline, and in DevSecOps in general. This is because most people think about putting security testing in place closer to development, which makes a ton of sense, and we even have a handy mantra to describe the process. We call it Shift left. However, in continuous delivery, we can't just stop with deployment. We also have to see our application in use in order to inform our next development cycle. So instead of just shifting left, security has to also make the shift right. This means putting instrumentation into our runtime or production, and this turns out to be really valuable because this is where you're actually getting attacked. You might be thinking, "haven't we been focusing" "on security and production for…

Contents