[Autogenerated] The last topic in this module that I want to cover is
in relation to continuous integration and delivery.
You may know this A C I.
C D pipelines.
They're called pipelines because they're typically sequence
of steps that occur in sequential order,
usually highly automated.
There are a number of different components associated with every pipeline.
For instance,
you will have source code as one component in the pipeline where all
your code management repositories will be located.
Developers will commit on bull code for modification
from thes repositories from there.
Once source code is ready,
software will be built unit tested on usually incur a
certain amount of integration testing.
Once all of this has been successfully passed, then the deployment takes place.
There can be multiple different environments,
including an acceptance environment staging environment on production,
where the softer will live at operate for users so you can see there is a
continuous integration pipeline and the continuous deployment.
Piper.
Let's now fit security on top of these different pipelines.
Security design comes before the cold is written,
but once code is written, security review off the code should be undertaken.
Ideally, this should be an automated review during the testing phase,
security testing should be baked in an integrated part
off the continues integration pipeline.
And finally, during the deployment,
all the plumbing should be done securely by using automation to
ensure that all production environments on other environments that
are being deployed to are securely configured.
What this approach gives us by embedding automation for security into
the pipelines is a repeatable and consistent approach.
Security becomes embedded in the pipeline.
It's no longer an after toward on.
Remember the friction points we discussed earlier,
where security was frequently being labeled as being
too late on delaying projects?
Well, that friction disappears more than anything else.
This gives us a sustainable security process for your software development.
Lifecycle.
Let's move on and some of this module.