Hi. Welcome back to the course. In the last video, we went over some coyote basic information. So we talked about what it is I ot We also talked about the anti architecture, some of communication models and then also some of the challenges of I o. T.
In this video, where to go over the OSS top 10 for io ti vulnerabilities. And we're also gonna discuss countermeasures for each one.
So here's our list of the S top 10 I ot vulnerability. So this is a 2014 list, and probably the next year or two they'll be coming out with the next version of it.
But for now, Number one is insecure. Web interface number two. Insufficient authentication or insufficient authorization. Number three Insecure network service is for lack of transport encryption. Five privacy concerns.
Six Insecure cloud interface is insecure mobile interfaces for seven and then eight is insufficient security. Configurable itty nine insecure software firmer. And then number 10 is poor physical security.
So let's talk about the counter measures of each one.
So for insecure Web interface is this is a lot of common sense stuff you're gonna notice. Several of these have similar countermeasures here. So here we can. We want to make sure we change any default passwords and years their names. And generally that's during the initial set up. We don't want to wait too long before doing that.
We also want to make sure that our password recovery methods are pretty robust. So we don't want a criminal hacker or anything just because we're not doing, you know, a lot of checks and balances.
We just want to make sure that the Web interface is not susceptible the things like cross site scripting or cross Irish Crest forgery.
I just want to make sure that no credentials were exposed while we're just sending network traffic, and that includes internal and external network traffic,
we don't want to allow any weak passwords at all. And then also, we want to make sure you have some kind of account lockout feature. After a certain number of failed Logan takin attempts,
the number two, they're the insufficient authentication and insufficient authorization. Make sure passwords are strong. We also don't want to make sure we can have granular access control. So what that means is basically that I don't want to just say that okay. You know, you work as a network admin, and I just give you all this stuff I want to be ableto truncated down to say, Okay, you only need these two servers,
and you only need to access to these 25 workstations
because that see the people and the information you're working with.
We also want to be able to put in two factor authentication standards in there. And then again, make sure we have pretty robust password recovery mechanisms.
So we're secure. Network service is we basically just want open necessary port. So again, I mentioned all the lot of the stuff is common sense or straightforward stuff. This is all. If you've got some general knowledge of security and, you know, throughout this course what you've learned, you kind of see like Okay, yeah. You know, we want to make sure these things are in place.
So we also want to make sure that our service is air not vulnerable through things like buffer overflows and also distributed Excuse me, denial of service attacks or distributed denial of service attacks as well.
Lack of transport encryption. So we want to make sure that data is encrypted on dhe with protocols like Ellis, I know Easy Council does mention, like in their material about SSL, but realistically, a real life we want to your bliss,
at least at this stage until something else comes out.
And then we want to avoid any proprietary type of encryption protocols, just medical use, accepted encryption standards,
privacy concerns. So we want to just make sure that data critical to just the functionality of R I o T devices collected we want don't want them collecting any other type of personal information.
We want to protect that data with encryption and then also make sure that only authorized individuals or organizations have access to our personal information.
The insecure cloud interface. So you see here again, we got default usernames and passwords. These need to be changed.
We need to have an account lockout feature and then also make sure, as we did with our Web interface, make sure that that's not susceptible through Cross I scripting or cross site request forgery.
Also make sure that credentials aren't gonna being exposed over the Internet, so you might have seen him. I think it's been in the past six months. There's been several articles in the in the media, at least here in the United States regarding insecure, like a W s buckets on. So, like different credentials. And even some companies had log in credentials on *** Club s O.
Just keep that in mind that you don't want to expose that in any capacity anywhere on the Internet.
And then, of course, put in, like, two factor multi factor authentication.
So insecure mobile interface is we want to make sure that we change again. Default using passwords, strong password, reset things in place, account lockouts. Make sure that our credentials, they're not being exposed to wireless networks. And then, of course, two factor authentication,
insufficient security configurable ITI. We want to ensure the ability to keep our admin user separate from our regular users. So we wantto separate those
encrypt the data at rest or even in transit. And then, of course, strong password policies and also logging security events.
So for a number nine, the insecure software firmer. We want to make sure that our device has the ability to actually get updates, right. And then we also want to ensure that the updated file is encrypted, that it comes from the legitimate source, and also that it doesn't contain any type of sensitive data.
We have to ensure the signature and the verb and verify the actual update file. Make sure again, it's from the correct source and then make sure that the update to our servers actually secured
on the finally poor physical shook. Your security soon may have stumbled on that one, Uh, but we want to assure that today's data storage medium cannot be easily removed. So we don't want someone walking out with a server, right? Or we don't want someone walking out with our, you know, a refrigerator. You know, our washer dryer or a thermostat or, you know, a smartphone.
So just make sure that it's secure in some capacity.
Storing the data make sure encrypted at rest. I'm eliminating the use of USB ports, basically disabling them,
insuring the device cannot be disassembled easily, so we don't want somebody just come in and take off the lid and they can grab it and walk out. We want to make sure it's complicated for them to try to take it apart
and then ensure the product can limit administrative capability, so limit the admin capabilities on that particular device.
So in this video, we just talked about the OAS top 10 I ot vulnerabilities on that. Also countering those as well.
The next video we're gonna talk about I ot attack surface is also talk a little bit about I ot hacking tools.