[Autogenerated] if you watch any of my other courses,
you know, I'm a big fan of using examples to help us with our learning.
Let's look at another example of where Deb sec ups can help
with traditional security requirements.
In this case, we're going to look up.
What are the benefits of converting security practices that
maybe traditionally manual activities in tow?
Automation, code based activities?
So basically having our security written insult er as cold?
There are many benefits.
With automating security practice.
For example, cold reviews could become cold.
Previews where we have automated code checkers are code being
checked at commit stage so that it never gets turned into a
built application that gets deployed.
If we can catch the coding errors early,
then it means we can reduce our overall security costs on a development costs.
Patching is a very common practice in good security Haijun environments.
Typically,
we would patch on a regular basis eater monthly or some other regular interval.
However, what if we eliminated the need to patch or environments entirely?
What if we were able toe automate the building of environments
on every new environment that was built?
Came what all the latest patches included.
So we're effectively replacing patching as an activity by
automating the building of environments.
Final examples where we can replace incident response or maybe minimize it
if we can't entirely replace it by increasing our time on track modeling
and other types of scenario based activities.
If we can use trip modeling is part of our design,
we may be able to minimize and reduce the number of
incidents we have to deal with.
Although not a fully automated practice,
there are magnitudes available to help us with a lot of
the heavy lifting around track modeling.
These are just some examples of how we can again shift left
with using security as code on moving our security processes
to occur earlier in the life cycle.