[Autogenerated] as you move towards the operator monitor faces.
The focus changes from ensuring the application is built robustly,
checking to make sure that the application is not under attack on when
it is that we know about it as soon as possible.
We also want to make sure that there's no unauthorized changes.
Mated configuration off the environment.
Compliance is code which checks the configuration of the
environment against approved baselines.
ONDA eliminates any deviation from this baseline in their real
time is important for the operate phase.
Verification of monitoring on ideally continues.
Checking that everything is operating within expected norms is
another key aspect off the operate phase.
If we flatten out or Dave SEC ops lifecycle into a linear representation,
we can see that all along the pipeline.
There's many different tools required to ensure a
successful def sec up implementation.
It can become confusing with so many different tools available on the market,
Place toe understand exactly where these tools
fitting in terms of the specific face,
their most suitable to one useful reference guy is
this periodic table of Dev ops tooth, which is regularly updated.
You can visit this period the table at the link I have provided under slide.
It provides various different tools for different types of
activities in the Dev Ops Lifecycle.
It also includes a list of security twos which you can see on
the bottom right hand corner off this diagram.
This is a very useful guide to help you distinguish between the
suitability of various different tunes for the different phases
off the day of SEC ops pipeline.