Welcome back to Lesson 6.6. That's the mentioned the end of the module. So let's just go back over the ideas we talked about.
So in this module we discuss deployment tools. Activities contrasted some of the cloud based deployment tools,
and we talked about infrastructure of a code. Why you should be using it, why it'll make your environment more stable and then a demoed it in the idea of we brought
it into our deaths Checkups pipeline within Jenkins and use docker images to deploy to a container and then run the desk tool against that container as a verification that what we produced or what we get ready to deploy has no new vulnerabilities.
We took a look at some of the infrastructure is a code soft off software offerings,
puppet answerable and compared them for provisioning. And how you gonna use him for configuration management
that we took a looking again at the def sec ops maturity model? Specific. That deployment, looking at how you harden your infrastructure, how you deploy,
and then we wrapped it up with looking at kubernetes and discussing containers and the value off
of building these micro services and The less resource is you need, the quicker time you can launch and how it this is makes it capable of scaling in the cloud.
So one final quiz for the module, Which of the following software is not used for implementing a secure configuration
with answerable, puppet chef or nexus?
So while Ness's can evaluate the implantation of secure baseline, it cannot actually apply the changes. Eso it is just it would be evaluation tool, not an implementation tool.