13 hours 9 minutes
hello and welcome to the penetration testing execution standard discussion.
Today we're going to be doing the overview of the vulnerability analysis section of Pee tests and what we're getting ready to get into. So let's jump right in
our first area that we're going to be looking at will be vulnerability testing. We're going to briefly cover what vulnerability testing is some examples of fall types and, overall, the vulnerability testing goals. Now, a lot of times, clients will confuse vulnerability testing for penetration testing.
Always remember, the key difference here is that we're looking to see if there are vulnerabilities. Where is with pen testing were exploiting those vulnerabilities
within the active testing section. We're going to look at what active testing is. We're going to review some automated methods general vulnerability scanners, banner grabbing Web applications, scanners and obvious cation.
Then we'll get into passive testing and what that involves. We're going to look at meta data analysis as well as traffic monitoring,
and then we'll get into validation what that is. Correlation between tools and using multiple tools to validate vulnerabilities, manual testing and protocol specific testing, and then attack and manage such a CZ. The creation of attack trees, isolated lab testing and visual confirmation on vulnerabilities.
We'll move on over into research, where we'll look at public research information, exploit database and framework modules, hardening guides and common miss configurations, private research identifying potential avenues in vectors and disassembly and code analysis.
All of this will come together to give us an idea of how vulnerability analysis should be conducted
based on the penetration testing execution standard. With that in mind, I want to thank you for your time,
and I will look forward to seeing you here again soon.