in the last video, we talked about patches and importance of testing in this video. We're going to talk about applying patches.
Let's look at the learning objectives.
We're gonna talk about applying patches.
We're gonna talk about the guy last Apache.
Let's take a look at the pre assessment.
All patching of systems can be done just once a year. Is that true or false?
This is actually folks,
so let's look at applying patches.
So what? The traditional method that's flowing,
which had its flow about Ojai coz and encourages the late remediation or regular update process,
So we cover high calls.
We're talking about the legal remediation
and which automation is needed.
So it's for supplying patches.
If your word to try to apply patches, it's four as manually,
meaning that you have to low again to each individual server.
Not only would this be sang come soon,
but this would actually have a very high cults in which you have to spend more money on. Resource is
so the sense of automation
basically loading patches to a patching
platform are basically into a patch in to
and having a to perform the patching. It's more cost effective.
As we can see here, we have automation.
We have to integrate patch management and where every movement remediate as soon as possible.
So let's look at it. So re mediate. So
I need to be remediated as quickly as possible and minimize risk
giving first priority to the most critical issues facing your most critical systems
Automated patch management and suffered distribution solutions can help speed this process and keep cause to a minimum
robot capability can restore software to a previous state and insurers organizations use appropriate software
patch management. What other automated
bone ability matches processes is beneficial.
So let's look at the post assessment here.
$1 side of not using automated patch management
The asset here is true
in this video, we talked about applying patches.
performing another vulnerability scan to verify
the patches that work