Okay, So one of the things that constantly amuses me is how we will try whatever we can to get around the system. This actually doesn't work. But what the driver of this car was hoping to do is to bypass those security cameras where they snapshots your license plate and enter them into a database.
his idea is, Hey, if I dropped the database table, maybe my information will be cleared from the record. And this said it. Full speed traps. It doesn't. This doesn't actually work there a couple of little issues with it. But the bottom line is,
we tend to be crafty, especially when it comes to getting around traffic tickets. I know that. That's one of
one of the things that I liketo think about doing.
Did I just admit to that that's not what I meant at all?
Okay, but the bottom line, an example of code injection. And how do we mitigate code injection? We mitigate code injection by using input validation, limit field links, limited data types. So, for instance, for a date, you have no business entering in letters, right? Should be,
you know, two characters, two characters, four characters,
all numeric. Um, making sure that certain that a definition languages like drop tables are not allowed us input. There's no reason for that. Nobody's named Johnny drop tables, right? So don't allow that stuff in your database
now. Like I said, I'm not gonna read every one of the's. But just to enhance your knowledge, it's probably as I scroll through them worth you getting a screenshot? Numbness, if I don't talk about, is probably not testable, but just again to enhance your knowledge. And you can go upto a wasp. You don't have to, you know, take my screen shots.
what we know, right? So broken authentication, Just some way that authentication fails. I don't properly authenticate you. I'm just using password authentication, authentication, information, being sent in clear text. You know, lots of different ways in sensitive bad exposure can happen
a 1,000,000 different ways. We don't rip that in storage. We don't encrypt it. Motion. We allow, um
uh, social engineering people to bypass the normal security mechanisms. You know, this isn't a specific attack. This is just a general exploit.
security, Miss configurations.
Just not, you know, leaving default settings
having um not locking down the ability to traverse folders or files on a website, Right? Just
any sort of miss configuration. Will we test to ensure we don't have those miss those miss configurations? We test as much as possible, right?
Um, cross site scripting cross site scripting is an issue that has been the thorn in our sides for a long time now. It is actually less popular, less common than it waas in the 2013 a wasp, it was the number one exploit
in 2013. Now it's fallen down to number seven. That still means it's quite heavy, right?
Still a lot of risk with cross site scripting. So the idea is any cross site Scripting is a threat to the end user,
so they are perhaps directed to a page that's either been compromised or to a rogue page. And when they dio and their browser goes toe load, what's on the page? There's a malicious script that runs. There are lots of ways that that can happen. But the bottom line is
this isn't a threat to the backend database.
This is a threat to the user appliance system in their browser. So, for instance, you know the job of your browser is to run the code that's displayed, or that's, you know, the code that's present in the website. If there's a malicious code that it's gonna be one, um,
vulnerable component usage, that simply means that we sometimes copy and paste code. We sometimes use deprecate ID code that's not still supported. We may use AP eyes that are not secure. You basically just the fact that we cut corners, sometimes
insufficient logging and monitoring. If we're not watching, we don't know what happens, all right. So, like I said, not meant to be an in depth study of a loss. But just hitting a couple off the issues that our greatest concern tow us,
understand the benefits of a WASP and understand the handful of attacks there, and some of these will get into more in depth.
But ultimately, just understanding is part of due diligence that we educate ourselves and that we're aware off the threats that exist in Goa specifically dresses those threats in relation to Web applications