1 00:00:01,850 --> 00:00:08,810 Hi there, welcome back to this course. Keeping in mind the classic architecture of Iot systems that 2 00:00:08,810 --> 00:00:14,870 you can see in this slide, in this lesson, I will describe what are the typical Iot attacks? 3 00:00:16,590 --> 00:00:24,510 Typical attacks on Iot systems include: attacks on the cloud and the web of Iot architecture, attacks 4 00:00:24,510 --> 00:00:34,590 on mobile apps of Iot architecture, attacks on hardware and firmware of Iot devices, and attacks 5 00:00:34,590 --> 00:00:45,060 on wired and radio communication protocols used by Iot devices such as a Bluetooth protocol, ZigBee, etc.. 6 00:00:45,600 --> 00:00:52,110 And among these attacks, we can mention, for example, the replay attacks, jamming attacks, 7 00:00:52,110 --> 00:00:54,530 man in the middle attacks, etc.. 8 00:00:56,960 --> 00:01:05,390 Let's consider now, first of all, the Owasp IoT top ten security risks list, that you can see in this 9 00:01:05,390 --> 00:01:06,200 slide. 10 00:01:07,940 --> 00:01:19,910 The first risk is having an IoT system with devices that have weak passwords. For example, the 11 00:01:19,910 --> 00:01:32,210 Mirai malware used in a 2016 attack identified vulnerable Iot devices using a table of more than 60 12 00:01:32,210 --> 00:01:40,730 common factory default usernames and passwords and logs into them to infect them and spread to other 13 00:01:40,730 --> 00:01:41,540 targets. 14 00:01:43,680 --> 00:01:53,010 The second risk is having an IoT system with devices that have either unnecessary or vulnerable 15 00:01:53,010 --> 00:01:55,080 network services. 16 00:01:57,140 --> 00:02:04,990 Another great risk is constituted by the various and possible interfaces of an IoT system that could 17 00:02:04,990 --> 00:02:12,730 present vulnerabilities. Therefore vulnerabilities in Web cloud, mobile interfaces and in general 18 00:02:13,150 --> 00:02:16,660 in APIs used by the Iot system. 19 00:02:18,810 --> 00:02:29,310 A big problem can also arise from Iot systems where the software or firmware update mechanism has vulnerabilities 20 00:02:29,790 --> 00:02:31,890 as indicated in the slide. 21 00:02:34,290 --> 00:02:43,680 Another serious risk is constituted by Iot systems that use software components or libraries that are 22 00:02:43,680 --> 00:02:51,050 not updated or obsolete or no longer maintained by those who develop them. 23 00:02:53,990 --> 00:03:02,990 There is also risk associated with Iot systems that do not adequately protect or abuse personal data 24 00:03:02,990 --> 00:03:04,270 stored in them. 25 00:03:06,820 --> 00:03:16,270 Another risk is the lack of adequate protection, in terms of encryption or access control mechanism, on 26 00:03:16,270 --> 00:03:22,270 the data transiting on the transmission channels or residing on the devices. 27 00:03:25,070 --> 00:03:33,130 The lack of appropriate device management functions is also very critical in terms of updates, monitoring, 28 00:03:33,140 --> 00:03:36,080 response to incidents, etc.. 29 00:03:39,160 --> 00:03:48,220 Owasp also identifies as a risk factor the fact that Iot devices are often supplied with insecure 30 00:03:48,580 --> 00:03:54,490 default configurations and without the possibility of modifying them. 31 00:03:57,710 --> 00:04:06,440 Talking about the lack of physical hardening, some considerations can be made. The first step in protecting 32 00:04:06,440 --> 00:04:16,190 a device prior to going into production is to remove all physical, radio or optical ports that were there 33 00:04:16,190 --> 00:04:18,260 for development purposes. 34 00:04:18,890 --> 00:04:25,760 Of course, at least one part is required to connect the production device to the local network or back 35 00:04:25,760 --> 00:04:26,810 into the cloud. 36 00:04:26,990 --> 00:04:34,730 But all other ports that are no longer required should be removed, including any circuit board 37 00:04:34,730 --> 00:04:38,130 tracks that connect the port into the circuitry. 38 00:04:38,990 --> 00:04:46,850 Similarly, all test points should ideally be removed, including pins and circuit tracks, or at 39 00:04:46,850 --> 00:04:55,610 least effectively disabling test access by, for instance, blowing on-chip fuses for JTAG. 40 00:04:57,830 --> 00:05:00,470 OK, this lesson ends here. 41 00:05:01,160 --> 00:05:04,010 Thank you for your attention bye.