Module 4 Summary
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
Already have an account? Sign In »
4 hours 39 minutes
this is less than 4.7, where we reach the end of module force. Let's just recap what we learned.
So I talked about the beginning doing or what pipeline orchestration means specifically in continuous integration. Continuous delivery
talked about the agile development and how this impacts security and how we need to, as security
people integrate into that and be able to move at the same pace as a development and automate without with our tools.
We talked about some of the tools and activities for development and build because that's the stage we're talking about right now.
Looked at some of the open source static analysis tools, and we actually actually showed them demoed them and Jenkins and how we've now added our heart pipeline. We had ecstatic analysis and software composition analysis and
through Swiss spot bugs with awas dependency check. We also did some stylistic checking,
and they introduced the Death SEC ops maturity model that we're going to use again throughout the modules just to give a plan of Here's what we're doing or here's Here's how you can improve your pipeline for def SEC ops,
And we also talked about third party libraries how we cannot analyze them, why it's important and why we should be looking at it specifically through the supply chain and protecting this code and these libraries that were injecting into our applications
of the final quiz here. It wasn't it wasn't addressed in this topic are in this module, but we've mentioned a couple times and that might be interested. So
Kubernetes is a is a product for what purpose
is it a four Lin based evaluation? Is it for container orchestration or is it for configuration management?
I figured I would just take the description directly from the Kubernetes website, so they they describe themselves as kubernetes is an open source system for automating deployment, scaling and management and containerized applications. It groups containers that that make up any application to a logical units for easy management and discovery.
That's a lot.
It just It's the orchestration of the the containers and making true their load balance that running. Are they healthy? You canoe patching on them
and we'll talk about it. And one of the late later modules will delve into Cuban edges a little bit more, but just interesting topic and it's really with the way everything's going now.