We're already at the end of this module,
and we covered a lot of ground with regards to security testing.
We looked at automated security testing and that it's
mainly a form of negative testing.
And negative testing is where you don't know the expected outcome,
as opposed to positive testing.
Negative testing is much harder to do, as you don't know the outcomes.
Then there's static application security testing,
where you don't run the code at all, and dynamic application security testing,
where the code is executed.
We also took a look at vulnerability scanning.
And vulnerability scanning was matching a list of assets
against a list of known vulnerabilities.
Finally, we took a look at manual versus automated testing.
And one important thing to remember here is that,
one, it's not just a replacement for the other.
What's up next?
Let's go back to our scenario.
Maeve now knows what automated security testing is.
"Thanks, Jennifer.
" "You're very welcome.
" So, what are the next steps?
Jennifer asked Maeve whether she would like to know the pros
and cons of automated security testing, and,
of course, Maeve thinks that's great.
And that's exactly what's coming up in the next module.
See you there.