After having seen all the pros and cons, let's summarize this module.
There isn't actually a one-size-fits-all approach.
Look per project where it makes sense and where it doesn't make
sense to implement automated security testing.
One of the most important advice I can give you with this
regard is that security is always a tradeoff.
Look at the cost of implementing automated security testing versus the benefits.
Does it fit in your specific organization and in your workflow?
It isn't always easy to implement; therefore,
it doesn't always make sense to implement automated security testing.
Besides that, it's always useful to implement automated security testing,
even if it's only to comply with standards.
But again, try to decide on a case-by-case basis.
Next up, well,
Maeve is now actually convinced that automated security
testing is a fit for Globomantics, which makes Jennifer pretty happy.
She already thought it would be great fit for Maeve and her company.
So, the next step is to see what to test and where,
where to implement it in the software development
lifecycle and how to proceed further.
That's what the next module will be about.
See you there.