Let's try to summarize this module.
When starting with the implementation of automated security testing,
focus on quick wins first.
Start there, where it makes sense, and start with the tests where it makes sense.
Facilitate, not mandate.
You'll get the best results if the whole team supports everything,
if it's not pushed down from the top.
Start with a case-by-case approach.
Where does it make sense?
Which project?
Which tests?
And remember, security is always a tradeoff.
Look at the costs of implementing the automated security
testing tools with regards to the benefits.
What are you trying to protect?
Consider automated security testing a process and not a product.
For the final time in this course,
let's get back to our scenario with Maeve and Jennifer.
Maeve is very happy that she now knows all the concepts
which were discussed in this course.
She now has a better understanding of what automated security testing is,
and therefore, she wants to use it.
What Jennifer does is recommending the two followup courses:
Performing DevSecOps Automated Security Testing,
which deals with the tooling and, for instance,
the automated security testing of bespoke code,
containers, and infrastructure, and Integrating Automated Security Testing Tools,
which deals with integrating automated security testing into a
continuous integration/continuous delivery pipeline.
Both these courses are chock full with practical steps and demos,
as opposed to this pretty theoretical course.
Let's go back to our map of automated security testing.
You just watched Approaching Automated Security Testing in DevSecOps.
The two follow-up courses will deal with the actual execution of the tools,
as well as the implementation in your continuous
integration/continuous delivery pipeline.
This course was full with concepts.
The next two courses will be full with demos and practical explanations.
As for this course, thank you so much for watching.
It was a pleasure, and hopefully see you soon at one of the other courses.
Stay safe.