WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:0

00:14.640 --> 00:31.200
All right, let's take a look at Module

00:31.230 --> 00:34.120
13, which deals with IoT and OT security.

00:34.140 --> 00:39.520
First, we should probably define
the difference between IoT and OT.

00:39.550 --> 00:45.480
Iot is Internet of Things or Internet of
Everything, sometimes called I OE, which

00:45.510 --> 00:49.400
is basically anything with an IP
address and the ability to process.

00:49.430 --> 00:52.520
The more complete definition, network of

00:52.550 --> 00:57.080
devices having IP addresses and the
capability to sense, collect and send data

00:57.110 --> 01:00.740
using embedded sensors, communication
hardware and processors.

01:00.770 --> 01:04.980
They're deployed for a wide
variety of applications.

01:05.010 --> 01:09.600
Typically, they're implanted on natural,
human made or machine made objects and

01:09.630 --> 01:13.000
have the functionality of
communicating over the network.

01:13.030 --> 01:14.660
That right there

01:14.690 --> 01:21.960
is cause for concern, the ability
of communicating over the network.

01:21.990 --> 01:23.920
When you put another device on your

01:23.950 --> 01:27.900
network, you're providing access
potentially to your network.

01:27.930 --> 01:30.680
Imagine that you install a Firm o dog

01:30.710 --> 01:38.200
treat launcher, or Amazon Alexa, or a Nest
front doorbell, or a refrigerator with an

01:38.230 --> 01:41.640
internal camera, or a
sleep number bed, etc.

01:41.670 --> 01:44.560
Those devices are now possibly can be

01:44.590 --> 01:49.340
compromised and used as pivot
points on your network.

01:49.370 --> 01:53.930
They may collect information, report
it back to central authority, etc.

01:53.960 --> 01:56.040
There's cause for concern
because they are computers.

01:56.040 --> 01:58.020
We don't think of them like that because

01:58.050 --> 02:01.260
it's a gungy, cool device that
improves my quality of life.

02:01.290 --> 02:04.020
But at the same time, we're

02:04.050 --> 02:09.220
possibly providing surveillance access
inside our security parameters.

02:09.250 --> 02:12.520
You should exercise a healthy concern.

02:12.550 --> 02:17.000
There's also the concept of isolating
the systems on an isolated network.

02:17.000 --> 02:18.600
We'll talk about that a little bit.

02:18.630 --> 02:21.040
But I got a couple of
stories for you on IoT.

02:21.070 --> 02:23.890
Now, don't get me wrong, love the Alexa,

02:23.920 --> 02:30.400
love the Google Assistant, love
the IP security and so forth.

02:30.430 --> 02:37.940
But two situations that gave me pause
and also freak my wife out a little bit.

02:37.970 --> 02:43.540
But the first story is a friend of mine
gave me a Firm o dog treat launcher.

02:43.570 --> 02:49.640
This little camera pylon looking thing
with a microphone, a camera, a little hole

02:49.670 --> 02:51.960
in the front that you
fire dog treats out of.

02:51.990 --> 02:56.440
The whole purpose for this thing, so you
could check on your dog during the day and

02:56.470 --> 03:01.240
launch little treats and check in
with them and see how they do it.

03:01.270 --> 03:03.140
That's awesome.
That's cool.

03:03.170 --> 03:05.900
My dog will love the
treat launcher for sure.

03:05.930 --> 03:08.720
I get this thing set up and I train my dog

03:08.720 --> 03:11.400
that those projectiles coming at
him are actually a good thing.

03:11.400 --> 03:14.900
They're food.
Once he figured that out, he loved it.

03:14.920 --> 03:17.000
The very freaked out by
it initially, though.

03:17.030 --> 03:20.280
The whole voice coming from
it was a little bit weird.

03:20.310 --> 03:23.180
Once he got used to it, it was awesome.

03:23.210 --> 03:25.800
After we got him trained up on it, I left

03:25.830 --> 03:28.680
it in the corner of the
kitchen and forgot about it.

03:28.710 --> 03:31.760
I wasn't out of the house,
wasn't launching dog treats.

03:31.790 --> 03:34.560
But a little bit later that evening, we're

03:34.590 --> 03:40.080
sitting watching some TV and my phone goes
off and it's an email from the furbo

03:40.110 --> 03:43.900
people with the subject line
highlights from your dog's day.

03:43.930 --> 03:45.880
Isn't that a nice feature?

03:45.910 --> 03:47.720
Highlights for my dog's day.

03:47.750 --> 03:49.680
Not sure what I...
Not sure I like that.

03:49.710 --> 03:51.460
Let's see what this is about.

03:51.490 --> 03:54.920
I click on the link,
it starts playing the video and it's

03:54.950 --> 03:58.820
random clips of our kitchen,
random video surveillance.

03:58.850 --> 04:02.980
Some my dog moving around, some
not, some myself, my wife.

04:03.010 --> 04:06.740
I'm showing her this and I watch her

04:06.760 --> 04:09.600
brow get a little frowed or just
get a little bit concerned.

04:09.600 --> 04:12.020
She's like, Yeah, we're
getting rid of that thing.

04:12.050 --> 04:14.360
My wife is very security conscious.

04:14.390 --> 04:18.240
Sometimes even more than I am and
I do this stuff for a living.

04:18.240 --> 04:19.680
She said, Yeah, absolutely not.

04:19.710 --> 04:22.180
That thing's getting disconnected.

04:22.200 --> 04:23.780
But what are the potential issues there?

04:23.800 --> 04:25.680
It wasn't necessarily malicious.

04:25.710 --> 04:28.900
It was meant to be fun and useful.

04:28.920 --> 04:31.640
But at the same time, I installed an

04:31.660 --> 04:36.440
internal video camera in my house
with motion activated recording.

04:36.470 --> 04:37.840
Probably not good.

04:37.860 --> 04:42.360
If you think about it, though, the
application security that goes around

04:42.390 --> 04:46.860
that, you never know how much
security planning has gone into that.

04:46.890 --> 04:50.840
So if somebody had compromised my Firm o
account online and had collected my

04:50.860 --> 04:54.880
username and password from a Have I Been
Pwned database or something like that,

04:54.910 --> 04:58.880
they might be able to log in and
remotely monitor my house.

04:58.910 --> 05:02.440
So that thing got boxed back up
and we haven't used it since.

05:02.470 --> 05:04.600
Second story, and this one was creepy.

05:04.630 --> 05:07.960
My wife swears up and down that what she

05:07.980 --> 05:12.760
talks about at work shows up
on her phone and so forth.

05:12.780 --> 05:16.000
My explanation for all that is that the

05:16.030 --> 05:20.560
whole predictive suggestion thing is
way more accurate than you think.

05:20.560 --> 05:21.720
You had to have mentioned it somewhere.

05:21.720 --> 05:23.320
You had to have done a web
search or something like that.

05:23.320 --> 05:25.820
She swears up and down.
No, no, no, no, no.

05:25.840 --> 05:29.100
We're sitting one night,
again, watching TV.

05:29.130 --> 05:31.460
We're watching Men in Black International.

05:31.480 --> 05:34.240
You got Chris Hemsworth,
Thor from the Marvel movies.

05:34.270 --> 05:36.740
Then you've got Liam Neeson.
Loved Liam Neeson.

05:36.760 --> 05:38.120
Watch any Liam Neeson movies.

05:38.150 --> 05:39.320
One of my favorites.

05:39.320 --> 05:42.920
We're sitting there and I mentioned to
my wife, I'm like, How old is he now?

05:42.920 --> 05:44.040
How old is Liam Neeson?

05:44.070 --> 05:47.160
She's like, Yeah, I don't know.

05:47.280 --> 05:49.060
Kind of wondered about it.

05:49.090 --> 05:53.860
She gets to talk and there's a scene
where they're both standing side by side.

05:53.880 --> 05:55.440
He was like, Taller than Chris Hemsworth.

05:55.440 --> 05:56.480
She's like, My gosh, he must be tall

05:56.480 --> 05:58.660
because I know Chris Hemsworth
is like, you know, over 6 feet.

05:58.690 --> 06:00.660
I wonder how tall he is.

06:00.690 --> 06:05.840
I go, I'm like, Yeah, he
definitely looks tall.

06:05.860 --> 06:08.660
I always get these out of order here.

06:08.690 --> 06:10.960
But I'm like, Man, I wonder how old he is.

06:10.980 --> 06:12.840
Alexa, how old is Liam Neeson?

06:12.860 --> 06:15.040
Liam Neeson is 74 years old.
Got it.

06:15.070 --> 06:18.420
Would you also like to
know how tall he is?

06:18.450 --> 06:21.420
We both look at each other
like, We didn't ask that.

06:21.450 --> 06:24.440
We're really sure she was listening before

06:24.470 --> 06:28.580
we actually sent the voice
prompt, but it was really creepy.

06:28.600 --> 06:31.300
I don't think it's really a
plausible explanation for that.

06:31.330 --> 06:35.640
But just for the record, Chris
Hemsworth is 6'3, Liam Neeson is 6'4.

06:35.640 --> 06:36.800
He actually has an inch on Chris

06:36.830 --> 06:39.380
Hemsworth, and he's
currently 74 years old.

06:39.410 --> 06:41.760
But she offered up some stuff that we had

06:41.790 --> 06:45.640
just been talking about that there's
no way she could have known.

06:45.960 --> 06:47.820
What are they collecting?

06:47.850 --> 06:49.820
What are they surveilling?

06:49.850 --> 06:53.620
Again, healthy caution, especially
with cameras and things like that.

06:53.650 --> 06:56.440
I've got no cameras
that are left uncapped.

06:56.470 --> 07:01.000
I've got caps on a
laptop, things like that.

07:01.000 --> 07:04.720
There's some duct tape over the top of it
because I've just seen way too many

07:04.750 --> 07:08.680
compromise systems that the first thing
they do is turn on video camera access.

07:08.710 --> 07:11.460
Couple of stories around IoT.

07:11.480 --> 07:14.600
I'm getting ready to put in some home

07:14.630 --> 07:19.200
automation stuff and
I'm going to be hardwired and everything.

07:19.200 --> 07:20.640
I'm just going to say that right now.

07:20.670 --> 07:27.240
I said in the last module, big proponent
of hard cabling, especially for security

07:27.270 --> 07:31.880
systems, things like that, because a
signal jammer could pretty easily knock

07:31.910 --> 07:35.480
out your entire network,
depending on the right frequency.

07:35.510 --> 07:37.240
I'm digressing a little bit here.

07:37.270 --> 07:40.340
That's a bunch of dialog
for just the opening slide.

07:40.360 --> 07:41.400
Let's dig into it.

07:41.420 --> 07:42.960
One more.

07:44.680 --> 07:48.260
Years ago, there used to be this
movie called Warriors of the Net.

07:48.290 --> 07:52.760
It was a graphical representation
of IP, TCIP, and how that works.

07:52.760 --> 07:54.240
It was based on space trucking.

07:54.240 --> 07:56.200
I remember at the end of that thing, and

07:56.230 --> 08:00.040
this was 20 years ago, end of that
thing, they're saying, Who knows?

08:00.070 --> 08:04.360
Maybe your refrigerator will have a camera
where you can see if you've got the

08:04.360 --> 08:07.160
makings for a chicken c atatory
while you're at the supermarket.

08:07.160 --> 08:09.040
I remember thinking very vividly thinking

08:09.040 --> 08:11.920
to myself, Wow, yeah, I don't think
we're ever going to get there.

08:11.950 --> 08:15.800
We're there.
You got refrigerators and have cameras.

08:15.830 --> 08:18.840
You've got all of these IP enabled devices

08:18.860 --> 08:22.680
that can communicate with
hand held apps and so forth.

08:22.710 --> 08:28.440
Again, we're in a revolution of AI and IoT
and so forth, but we need to really,

08:28.470 --> 08:33.740
really think through the security of
all this just to be on the safe side.

08:33.770 --> 08:36.000
I'm going to jump off my soapbox now, but

08:36.030 --> 08:40.200
industrial devices, health care devices,
home devices, wearable devices, health

08:40.230 --> 08:48.120
care devices, insulin pumps, pace makers,
little computers that could be hacked.

08:48.150 --> 08:50.920
Again, gives you a pot.

08:50.940 --> 08:56.880
Have a healthy skepticism or healthy fear.

08:56.880 --> 08:58.120
What am I looking for it here.

08:58.150 --> 09:02.380
Have a healthy concern for the security of
these devices before you just default

09:02.410 --> 09:06.700
configuration deployment to your home
networks or your business networks.

09:06.730 --> 09:09.360
While organizations are opting for IoT

09:09.390 --> 09:14.600
devices, i nenvironments, IoT devices work
on a three dimensional plane, offering

09:14.630 --> 09:19.280
connectivity for anyone, anytime,
for anything from any place.

09:19.310 --> 09:21.740
So outdoors, indoors, daytime, night

09:21.770 --> 09:27.480
between PCs, human to human, human to
things, everything keeps an IP address.

09:27.510 --> 09:31.900
And we've got a heck of a connectivity
network in the form of the Internet

09:31.920 --> 09:34.440
and an addressing scheme
that accommodates all those.

09:34.440 --> 09:37.340
So yeah, there's a lot of advantages
to it, no doubt about it.

09:37.370 --> 09:39.640
Iot applicationers and devices.

09:39.670 --> 09:44.560
This is one of two slides in your course
where to list out the different service

09:44.580 --> 09:47.300
sectors, the locations, and
the devices being used.

09:47.320 --> 09:50.060
The HVAC, one more quick story for you.

09:50.080 --> 09:52.600
We used to use in one of the clients I

09:52.620 --> 09:55.820
work with used to have a training
center location in Panama City.

09:55.850 --> 09:58.840
In Panama City, it was a room rental.

09:58.840 --> 10:00.480
They were leasing it for a while.

10:00.510 --> 10:04.660
But the way we adjusted the thermostat
there was through a Honeywell app.

10:04.680 --> 10:05.820
It's Honeywell thermostat.

10:05.840 --> 10:07.880
It did everything through a web interface.

10:07.910 --> 10:12.260
That was three and a half years ago, and
that facility was actually

10:12.290 --> 10:17.520
partially destroyed during the
Hurricane a while back and was rebuilt.

10:17.550 --> 10:22.280
But I still have remote access
to that Honeywell thermostat.

10:22.310 --> 10:26.800
Again, all the applications and a lot
of stuff is web application based.

10:26.820 --> 10:29.680
You have to consider the
security for all this.

10:29.700 --> 10:34.600
Last one, remember
that nanny cam a few years back where that

10:34.630 --> 10:38.900
creep had hacked in and was talking to
the kids saying it was Santa Claus?

10:38.920 --> 10:40.280
Creepy.
Healthy, respected.

10:40.280 --> 10:41.880
That's the last example I give up.

10:41.910 --> 10:44.500
I'm going to give promise.

10:44.530 --> 10:46.720
Buildings, energy, consumer at home,

10:46.750 --> 10:50.520
health care and life
science, transportation.

10:51.520 --> 10:55.760
I do have a friend who's not a
test mechanic, but he teaches.

10:55.790 --> 10:59.720
He's a master GM mechanic
of the highest level.

10:59.750 --> 11:03.340
But he's also a college instructor.

11:03.370 --> 11:09.680
He was doing a class on Teslas with a huge
nondisclosure agreement attached to it.

11:09.710 --> 11:13.100
He said, You would not believe
what that thing can monitor.

11:13.130 --> 11:16.080
I do believe it.
All right.

11:16.110 --> 11:18.200
So vehicles, again, anything computer

11:18.230 --> 11:21.040
controlled, if you can talk
to it, you can hack it.

11:21.070 --> 11:26.400
Always keep that in mind and you'll have
the right mindset, but you should question

11:26.430 --> 11:30.040
everything and if I could
talk to it, I can hack it.

11:30.070 --> 11:34.480
Iot technologies and protocols,
and that's the CEH in me talking.

11:34.510 --> 11:36.560
Short range wireless communications,

11:36.580 --> 11:39.460
medium range wireless
communications, long range.

11:39.490 --> 11:41.340
We have some different technologies

11:41.370 --> 11:46.040
for interoperability
between IoTs and protocols.

11:46.070 --> 11:51.300
A lot of this stuff, again, uses
conventional Ethernet 802.11 and TCPIP.

11:51.330 --> 11:53.640
The wired communication, Ethernet,

11:53.670 --> 11:56.800
Multimedia over CoAx,
power line communication.

11:56.800 --> 11:58.560
Power line communication is we're sending

11:58.580 --> 12:02.500
signaling through existing
power line infrastructure.

12:02.520 --> 12:04.140
Then some of your IoT operating systems.

12:04.170 --> 12:08.840
Okay, Windows IoT, Amazon FreeRTOS,
Contiki Fusha, Name of Few, RIOT.

12:08.870 --> 12:15.380
Some of your application protocols,
CoAP, Edge, physical web, XMPP.

12:15.410 --> 12:16.560
The IoT architecture.

12:16.580 --> 12:19.940
You may have direct
access to the IT device.

12:19.960 --> 12:21.220
It may access through a gateway.

12:21.240 --> 12:23.280
Depending on how you've got the tiers set

12:23.280 --> 12:26.520
up, the gateway is responsible for
collecting data from devices and

12:26.520 --> 12:29.840
performing preliminary processing
the data before sending the cloud.

12:29.870 --> 12:33.580
This could be a multi layered
scenario or architecture.

12:33.610 --> 12:35.740
One example is an IoT gateway.

12:35.770 --> 12:39.480
Just the layers of the IoT architecture.

12:39.480 --> 12:43.060
We're not going to pick this apart too
much right now, but the device layer,

12:43.080 --> 12:47.000
the communication layer, the cloud
platform layer, and the process layer.

12:47.030 --> 12:51.520
Again, these are the different tiers of
communications between the processing and

12:51.550 --> 12:55.100
if it is using a cloud app, you'll
send it to the cloud platform.

12:55.130 --> 12:58.840
But that's a bunch of middleware
components for staging between the

12:58.870 --> 13:02.460
devices, ultimately the
data being processed.

13:02.490 --> 13:06.520
The device to device model
is direct connectivity.

13:06.550 --> 13:11.500
Light bulb, for example, across the
wireless network to the light switch.

13:11.530 --> 13:13.920
Typically, there's some a hub being used.

13:13.950 --> 13:18.400
I've got exactly one light bulb in one
closet and I can control it through Alexa.

13:18.430 --> 13:21.820
I haven't really gotten
into much more of that.

13:21.850 --> 13:25.980
But at some point, I might
expand on that a little bit.

13:26.010 --> 13:28.320
But the device to cloud model, device to

13:28.350 --> 13:32.360
the temperature sensor, connects to
an application service provider.

13:32.390 --> 13:36.080
Device with a carbon monoxide sensor,
again, connects to the cloud.

13:36.110 --> 13:38.440
Again, that's more of a centralization.

13:38.470 --> 13:39.720
The devices to gateways.

13:39.750 --> 13:43.800
The devices, again, send to the gateways
up to the application service provider.

13:43.830 --> 13:47.360
Then you have cloud to cloud
communications as well or a back end data

13:47.390 --> 13:52.560
sharing model if you are actually sharing
data between two cloud providers.

13:53.880 --> 13:55.680
Again, from a deployment perspective, the

13:55.680 --> 13:58.560
only thing I've ever deployed is what
I've been talking about at home.

13:58.560 --> 14:01.280
I haven't really gotten into
any production environments.

14:01.280 --> 14:03.960
I've done security testing
on them, but no deployments.