4 hours 39 minutes
welcome to Module seven, where we've reached the end of our pipeline and we're doing operation and monitoring. This will be the last major major module before we do a wrap up
in less than 7.1 will just take a look at an overview of the concepts we're going to learn during these different lessons.
So we'll look at the operations tools activities in the same way that the monitoring we'll take a look, a rasp and s e a back in the same way, that same contrast tool. And I'll demo it again just so we can see the difference between the I asked
and the wrasse sports actually going into a blocking mode versus just monitory.
And then, as we don't throughout these other modules will look at the def SEC ops maturity model but specifically for operations and maintenance. End of monitoring. And then we'll look at some of the continuous monitoring capabilities.
So the learning objectives we want to discuss operation monitoring, differentiate rasp, and I asked tool and then demonstrated to so you can see what it looks like and what the findings are
and then describe S e a monitoring. So
we did it before. We were looking at what's what's in there and we're evaluating it. But we're also interested in looking at it when we're monitoring in the monitoring phase so that
that might be that lag between testing and actual or running applications so we can identify any vulnerabilities.
And we want to look at, examine monitoring and logging maturity and then critique the need for application level security and then
look at some of the benefits of the Cloud Native Computing Foundation and look in using the tools from from their what they have
here. We are back on our infinity paths. We see we've reached the end. We're in the continuous monitoring phase,
and just so we understand what we mean by monitor its do where we could discover trends and problems So it might be like the hardware, the network if you have application or even if you're doing micro services monitoring your containers,
um, you're gonna be monitoring not only for these operation but for security events to any failures, incidents, compliant deviations. At this point, you probably familiar, and I'm sure everybody's doing this, but you would be doing continuous vulnerability scanning as well
and just want to go back quick Toothy This s S d f.
They have a quite a few requirements for responding to vulnerabilities. So RV 0.1 There's identifying confirmed vulnerabilities on an ongoing basis. Ganyu probably doing a lot of this where you establish the vulnerability program Monitor databases confirm your security tool chain,
which the last bullet would be specific to Def SEC. Ops is a
These are the tools I have in my chain, each one of my stages that are performing these activities to identify vulnerabilities along the full life cycle
and of RV to you have an assessment and priority Prior authorization and remediation. Eso do you do issue or bug tracking?
And when you get to RV three do you have Do identify root cause vulnerabilities You documented lessons learned
and then implement changes to thes thes s S d F practices.
So in this less than we took a look at the concepts for the module and everything will be learning. And the next will take a look at rasp and, uh, software composition analysis specific to the rasp in a running environment