OK, so in the last lecture, I give you an introduction into the mind of Sheila.
Now we're going to look at the last top 10 to be going through the methodologies that we're going to
use in this course, persons might attack.
Second, might Hirshfield.
Now we're looking at the last top 10 methodology.
You absolutely need to know its methodology inside and out.
So if we go to Osberg, you can look at the data.
Currently, this is the most recent data for this particular project and see how it was submitted and
how it was contributed.
But the important part, of course, is the main tab.
Don't be fooled by the basic looking, you know, layout of the Web page gives a lot of really good
information here.
So what we want to do is we want to look at the top 10 security risks to web applications.
What are defenders seeing in the field?
And number one are injection flaws, flaws.
And this doesn't just mean sequel.
There are other types of injection, right?
There's no sequel is OS injection, Ascham injection, this eldership injection, which is the first
active directory.
We're going to get into a lot of these in this course.
So don't worry if you don't understand what this means yet, we're going to dive in.
You're going to be writing these attacks in your lab.
Give me a lot of fun.
But if you click on one.
Like injection, for example.
We'll get some more information about it.
So you can see, OK, now this is the threat agent, attack vector security witness and the impact and
tells you how exploitable it is, how prevalent, how easy it is to detect how technical and what the
business impact is.
Then you can actually go down.
And you get some of the technical stuff, so first you can see if the application is vulnerable to injection,
tells you how to prevent it.
And then when you scroll down, you actually get the attack scenario, so it actually tells you how
to execute a sequel injection attack.
It gets gets really, really technical, really hands on, so this is really, really cool, you can
even get through some of these teachings.
Right, that are relevant, so you can see.
All right, here's a cheat sheet for SQL injection prevention so you can control click that and when
it opens up, you'll have a nice, you know, little cheat sheet about, you know, preventing this
particular attack vector.
Everything has a table of contents, tells you, you know, OK, you need to parameterize your queries,
you need to do, you know, input validation, you know, make sure you escape the queries properly
and it's all in here.
So this is a treasure trove of information.
You don't need to know the whole thing, but it's really important that you're just aware that this
is here.
OK, and then you can click, of course, broken authentication.
You can go to the next one.
Again, you can look at how exploitable it is, how easy it is for someone to exploit this and what
are some weaknesses, how easy is it to detect broken authentication?
How can you tell if your application is vulnerable?
Remember, we saw credential stuffing?
Yeah, that's from the MicroTech framework, right.
So you can see that this permit's automated attack, such as critical stuffing where the attacker has
a list about usernames and passwords.
Right.
Because the authentication is broken, they might be able to use credentials that were leaked to the
dark web to breach a Web application.
Taught you how to prevent OK, says, hey, don't use a list of the top ten thousand words passwords,
right?
I mean, that sounds like common sense, but there it is.
And you have some scenarios, right?
So, I mean, again, this is really, really awesome stuff.
And you really need to make sure that you go through all this stuff.
So this is this is kind of mandatory, guys.
And you can't call yourself a respectable cybersecurity professional if you aren't aware of these particular
security risks and you can't explain it to someone else.
Exactly.
Absolutely.
Need to know this.
Right, since data exposure.
No security misconfiguration, crosshatch coopting, come on, crosshatch, glyptic, SBB, insecurity,
civilization, so just take the time to click through these again and don't feel bad.
You don't feel don't feel like, you know, it all has to make sense the first time you read through
it, you know, this stuff is going to go over your head in the beginning.
I know it did for me when I was learning this stuff.
But you just want to just kind of get in the habit of reading things even when it doesn't make sense,
even when you're not apprehending everything and just start to get a feel for what's out there, get
a feel for some of the attacks that are happening.
In the very least, I would say click through each of these and then just read the if the application
vulnerable section with the How to Prevent section and then go down and read the example attack scenarios.
That's all you need to do is read the three cubes.
Is the application vulnerable, how to prevent and example attack scenarios and do that for each of
the top 10 and then you're good to go?
That's really all you need to know.
But make sure, you know, inside it out and can be good.
OK, so that's all we have here.
In the next lecture, I'm going to talk about taking notes.
I know it sounds boring, but it's important because we don't take notes.
You're going to get lost and things are going to get complicated.
And when it comes time to write it, penetration testing report at the end of the engagement, it's
not going to be great.
Really?
Really.
The report is the only thing that matters when it comes to pensions.
That's where you draw a value.
So it's really, really important to learn the techniques.
And so you really want to do so.
So I'll see you guys in the next lecture, dig into taking notes that stay organized.
So.