WEBVTT

0:00:08.220000 --> 0:00:12.500000
 So I'd like to introduce you to some concepts
 about VPNs and some terminology

0:00:12.500000 --> 0:00:16.940000
 that you need to be familiar with for
 the C-SNA exam and just moving forward

0:00:16.940000 --> 0:00:19.980000
 into your life as a network
 admin or network engineer.

0:00:19.980000 --> 0:00:23.500000
 You're going to hear these terms VPNs
 and some of these other terms quite

0:00:23.500000 --> 0:00:26.560000
 a lot so it helps to know
 what we're dealing with.

0:00:26.560000 --> 0:00:29.020000
 So what is a VPN?

0:00:29.020000 --> 0:00:35.040000
 So the acronym VPN stands for Virtual
 Private Network and it's really

0:00:35.040000 --> 0:00:40.600000
 a compilation of two separate overall
 themes, a private network and a

0:00:40.600000 --> 0:00:42.140000
 virtualized network.

0:00:42.140000 --> 0:00:43.280000
 What does that mean?

0:00:43.280000 --> 0:00:46.840000
 Well, let's take a look at this whiteboard
 drawing here for a moment.

0:00:46.840000 --> 0:00:52.060000
 Imagine that you are the network administrator
 in charge of company A

0:00:52.060000 --> 0:00:54.140000
 and you have two sites.

0:00:54.140000 --> 0:00:59.360000
 Maybe they're across the country from
 each other, site one and site two.

0:00:59.360000 --> 0:01:03.640000
 So as the network administrator of company
 A, first of all, you want all

0:01:03.640000 --> 0:01:04.940000
 of this to be private.

0:01:04.940000 --> 0:01:09.500000
 In other words, you want to make sure
 that when packets leave your network

0:01:09.500000 --> 0:01:13.700000
 that they go along your private connections
 from one site to the other,

0:01:13.700000 --> 0:01:18.860000
 they couldn't possibly end up at your
 competitor's network or somewhere

0:01:18.860000 --> 0:01:20.300000
 where they're not supposed to be.

0:01:20.300000 --> 0:01:24.860000
 So your packets are private only seen
 by your network traveling across

0:01:24.860000 --> 0:01:26.480000
 your network connections.

0:01:26.480000 --> 0:01:30.620000
 Also, another thing is maybe these
 same packets in order to make them

0:01:30.620000 --> 0:01:36.000000
 private, you want them to be encrypted
 so that if anybody happens to sniff

0:01:36.000000 --> 0:01:39.440000
 them or catch them along the way,
 they can't see what's in there.

0:01:39.440000 --> 0:01:41.920000
 They don't know what kind of
 data that packets holding.

0:01:41.920000 --> 0:01:46.520000
 So the privacy is that the packets go
 from point A to point B, site one

0:01:46.520000 --> 0:01:49.940000
 to site two, there's no other
 path they could possibly take.

0:01:49.940000 --> 0:01:51.700000
 You're in control of the routing.

0:01:51.700000 --> 0:01:55.180000
 The routing paths will never lead you
 astray and lead your packets somewhere

0:01:55.180000 --> 0:01:56.560000
 they shouldn't go.

0:01:56.560000 --> 0:01:59.780000
 And you probably also want some sort
 of privacy on top of that as far

0:01:59.780000 --> 0:02:05.320000
 as encrypting your data, making sure
 that the data is authenticated, that

0:02:05.320000 --> 0:02:07.240000
 it's going to the right location.

0:02:07.240000 --> 0:02:08.940000
 So that's the private
 network here.

0:02:08.940000 --> 0:02:11.020000
 This is all yours, it's private.

0:02:11.020000 --> 0:02:13.500000
 Now, what about a virtual
 private network?

0:02:13.500000 --> 0:02:19.160000
 Well, imagine for a moment that this section
 here in the middle is actually

0:02:19.160000 --> 0:02:21.100000
 not owned by you.

0:02:21.100000 --> 0:02:24.900000
 This is not your network, this
 is somebody else's network.

0:02:24.900000 --> 0:02:29.900000
 And as such, there are other companies,
 not your own company, that are

0:02:29.900000 --> 0:02:35.060000
 connected to that exact same section
 of routers and switches and cables

0:02:35.060000 --> 0:02:36.840000
 and everything like that.

0:02:36.840000 --> 0:02:41.800000
 And their packets are going through
 that exact same red area that your

0:02:41.800000 --> 0:02:44.120000
 packets are going through.

0:02:44.120000 --> 0:02:49.040000
 But from the perspective of your routers
 at site one and site two, they

0:02:49.040000 --> 0:02:50.000000
 don't know that.

0:02:50.000000 --> 0:02:53.680000
 In other words, if we take a look at
 this router right here, these routers

0:02:53.680000 --> 0:02:59.680000
 on the edge, they believe that they
 are connected to a private network.

0:02:59.680000 --> 0:03:03.220000
 Those routers have no idea that the network
 they're connected to is being

0:03:03.220000 --> 0:03:05.000000
 shared with other companies.

0:03:05.000000 --> 0:03:07.620000
 They don't have to take any special
 precautions about that.

0:03:07.620000 --> 0:03:14.500000
 They trust that this network in the
 middle is providing them privacy.

0:03:14.500000 --> 0:03:16.800000
 It looks like it's their network.

0:03:16.800000 --> 0:03:19.680000
 It looks like it's just an end-to-end
 network connecting site one and

0:03:19.680000 --> 0:03:22.960000
 site two. It just looks like
 one big, long network.

0:03:22.960000 --> 0:03:26.000000
 But in reality, the part in
 the middle is not yours.

0:03:26.000000 --> 0:03:30.340000
 It's sort of providing you this
 virtual end-to-end network.

0:03:30.340000 --> 0:03:33.160000
 When in reality, you don't have an
 end-to-end network that's fully in

0:03:33.160000 --> 0:03:36.800000
 your control. You were leasing or using
 the services of somebody else's

0:03:36.800000 --> 0:03:41.240000
 network in the middle to give you that
 sort of end-to-end connectivity.

0:03:41.240000 --> 0:03:44.820000
 So that's why we say it's
 a virtual private network.

0:03:44.820000 --> 0:03:48.120000
 Because even though it looks like it's
 all yours, this is just for you

0:03:48.120000 --> 0:03:52.600000
 and it's private just for you, in reality,
 the section in the middle could

0:03:52.600000 --> 0:03:56.200000
 be also transporting lots and
 lots of other customers' data.

0:03:56.200000 --> 0:03:58.240000
 But it looks like
 it's just for you.

0:03:58.240000 --> 0:04:02.380000
 That's why we call it a
 virtual private network.

0:04:02.380000 --> 0:04:06.820000
 So we're using or leasing another's network,
 typically the public internet,

0:04:06.820000 --> 0:04:10.180000
 to connect two or more
 of your sites together.

0:04:10.180000 --> 0:04:14.820000
 Now, before VPNs existed, how
 do we get this privacy?

0:04:14.820000 --> 0:04:20.700000
 How do we connect these various spoke
 sites to our hub and maintain privacy

0:04:20.700000 --> 0:04:22.580000
 and confidentiality?

0:04:22.580000 --> 0:04:26.940000
 Well, in order to do that, we had to have
 point-to-point connections between

0:04:26.940000 --> 0:04:29.420000
 pretty much everything.

0:04:29.420000 --> 0:04:33.320000
 Each spoke would have to have some sort
 of point-to-point connection to

0:04:33.320000 --> 0:04:37.780000
 the hub. And if you wanted the spokes
 to talk to each other, they'd have

0:04:37.780000 --> 0:04:39.920000
 to have point-to-point connections
 between them.

0:04:39.920000 --> 0:04:43.420000
 You basically had to maintain a lot
 of point-to-point connections.

0:04:43.420000 --> 0:04:48.340000
 If each one of those was a T1 or a frame
 relay circuit or something, that

0:04:48.340000 --> 0:04:49.560000
 was very pricey.

0:04:49.560000 --> 0:04:50.940000
 But it was all yours.

0:04:50.940000 --> 0:04:54.540000
 Each one of those black lines there, each
 one of these connections, represented

0:04:54.540000 --> 0:05:00.680000
 your privacy. So what you would have
 here is these gray lines are what

0:05:00.680000 --> 0:05:02.680000
 you were using for your
 internet connectivity.

0:05:02.680000 --> 0:05:04.000000
 There was no privacy here.

0:05:04.000000 --> 0:05:06.080000
 This is just what you
 went to the internet.

0:05:06.080000 --> 0:05:09.760000
 But if you want privacy between your
 spokes and your hubs, that's what

0:05:09.760000 --> 0:05:13.000000
 the black lines represented right here,
 what I'm coloring in blue right

0:05:13.000000 --> 0:05:15.480000
 now. These were your point
-to-point connections.

0:05:15.480000 --> 0:05:19.140000
 So you had to have not only connections
 to the internet that you were

0:05:19.140000 --> 0:05:20.860000
 paying for and maintaining.

0:05:20.860000 --> 0:05:23.560000
 In addition to that, every single month
 you had to have these additional

0:05:23.560000 --> 0:05:27.720000
 connections, these point-to-point connections
 to give you privacy between

0:05:27.720000 --> 0:05:32.140000
 each of the spokes or between
 the spokes and the hubs.

0:05:32.140000 --> 0:05:36.280000
 Another problem with this was that
 a lot of subnets were in use right

0:05:36.280000 --> 0:05:40.820000
 here. For example, look at
 just spoke number one.

0:05:40.820000 --> 0:05:44.540000
 There was some sort of IP subnet in use
 along this link, giving it connection

0:05:44.540000 --> 0:05:45.900000
 to the internet.

0:05:45.900000 --> 0:05:48.980000
 There was a second IP subnet that had
 to be used for its point-to-point

0:05:48.980000 --> 0:05:50.560000
 connection with the hub.

0:05:50.560000 --> 0:05:53.940000
 A third subnet used for its point-to
-point connection with spoke four.

0:05:53.940000 --> 0:05:56.980000
 And another one for spoke three
 and another one for spoke two.

0:05:56.980000 --> 0:06:01.540000
 So to maintain all of these connections,
 we had to have one, two, three,

0:06:01.540000 --> 0:06:05.300000
 four, five subnets just
 on spoke one alone.

0:06:05.300000 --> 0:06:07.940000
 And as we know, IP subnets
 come at a premium.

0:06:07.940000 --> 0:06:10.160000
 They're very rare.

0:06:10.160000 --> 0:06:12.040000
 There's running out.

0:06:12.040000 --> 0:06:14.660000
 And so this was not really
 a scalable situation.

0:06:14.660000 --> 0:06:19.480000
 But after VPNs were invented, then
 we could actually use our existing

0:06:19.480000 --> 0:06:21.240000
 connections to the internet.

0:06:21.240000 --> 0:06:24.220000
 And those connections to the internet
 could actually do two things.

0:06:24.220000 --> 0:06:27.460000
 We could use that connection on the internet
 to actually send this normal

0:06:27.460000 --> 0:06:33.520000
 data to the internet, to our web browsing
 or our Google or Amazon.com

0:06:33.520000 --> 0:06:34.780000
 or whatever it was.

0:06:34.780000 --> 0:06:39.480000
 But we could use those same connections
 to build these tunnels from one

0:06:39.480000 --> 0:06:41.080000
 router to the other.

0:06:41.080000 --> 0:06:42.720000
 Now, what do I mean by tunnel?

0:06:42.720000 --> 0:06:46.500000
 What I mean by tunnel is that
 there were IP packets.

0:06:46.500000 --> 0:06:53.580000
 We could have IP packets sent from
 spoke one as an example to the hub.

0:06:53.580000 --> 0:06:55.920000
 Here's a tunnel.

0:06:55.920000 --> 0:06:58.460000
 The source of these packets
 would be spoke one.

0:06:58.460000 --> 0:07:01.060000
 The destination of these packets
 would be spoke two.

0:07:01.060000 --> 0:07:05.500000
 But inside the packets themselves
 would be our data.

0:07:05.500000 --> 0:07:08.280000
 So whatever spoke one need to send
 a hub one, let's say there was some

0:07:08.280000 --> 0:07:13.000000
 file server over here that
 the hub was connected to.

0:07:13.000000 --> 0:07:17.020000
 And there was some PC sitting over
 here in the office of spoke one.

0:07:17.020000 --> 0:07:20.620000
 Well, that PC, when it sent data to
 the internet, like just doing web

0:07:20.620000 --> 0:07:24.940000
 browsing or whatever it was, that information
 would just go through the

0:07:24.940000 --> 0:07:27.760000
 regular internet connection,
 unencrypted, just normal.

0:07:27.760000 --> 0:07:31.800000
 But if that PC sent some data that
 was destined for this server right

0:07:31.800000 --> 0:07:36.560000
 here, the spoke router would say, oh,
 okay, I need to take that packet,

0:07:36.560000 --> 0:07:40.660000
 put it inside another packet, encrypt
 the body of it, and then send it

0:07:40.660000 --> 0:07:44.120000
 to the hub. So even though they're
 both packets are going through the

0:07:44.120000 --> 0:07:48.880000
 internet, one packets destined for an
 internet destination, google.com,

0:07:48.880000 --> 0:07:52.260000
 cnn.com, bankofamerica
.com, whatever.

0:07:52.260000 --> 0:07:56.520000
 That's a regular unencrypted packet destined
 for a point on the internet.

0:07:56.520000 --> 0:08:00.900000
 The other packet leaving this exact
 same physical interface is destined

0:08:00.900000 --> 0:08:05.140000
 for a server within your own company
 at a different location.

0:08:05.140000 --> 0:08:08.700000
 And that's going through a tunnel, meaning
 we're protecting that packet,

0:08:08.700000 --> 0:08:10.500000
 we're adding privacy
 to that packet.

0:08:10.500000 --> 0:08:13.660000
 We're probably encrypting that packet
 so somebody can't see what's inside

0:08:13.660000 --> 0:08:19.740000
 of it. So that's what, that's how a
 VPN would give us that connectivity.

0:08:19.740000 --> 0:08:25.640000
 So now when it comes to VPNs, there's
 two major types of VPNs we need

0:08:25.640000 --> 0:08:28.260000
 to be familiar with, just
 a couple more terms.

0:08:28.260000 --> 0:08:32.260000
 One type of VPN is called
 a peer to peer VPN.

0:08:32.260000 --> 0:08:35.920000
 So in a peer to peer VPN, you can see
 that these dashed red lines in this

0:08:35.920000 --> 0:08:42.800000
 particular case indicate peerings of
 routing protocols like EIGRP or OSPF

0:08:42.800000 --> 0:08:45.060000
 or maybe even BGP.

0:08:45.060000 --> 0:08:51.000000
 So in a peer to peer VPN, you are actually
 exchanging routes with your

0:08:51.000000 --> 0:08:52.240000
 service provider.

0:08:52.240000 --> 0:08:55.740000
 So you at the spoke would actually send,
 you know, whatever your subnets

0:08:55.740000 --> 0:08:59.160000
 are here at your spoke location would
 send those subnets to your service

0:08:59.160000 --> 0:09:01.440000
 provider via some sort
 of routing protocol.

0:09:01.440000 --> 0:09:03.700000
 That would be something that you and
 your service provider would work

0:09:03.700000 --> 0:09:07.360000
 out. Could be RIP, could be
 OSPF, could be anything.

0:09:07.360000 --> 0:09:10.300000
 And then your service provider would
 have to have some sort of routing

0:09:10.300000 --> 0:09:13.800000
 protocol running between
 their own routers.

0:09:13.800000 --> 0:09:17.640000
 And then eventually that route would pop
 out here and this service provider,

0:09:17.640000 --> 0:09:22.560000
 remember we called a provider edge router
 or a provider edge would send

0:09:22.560000 --> 0:09:23.720000
 it to the hub router.

0:09:23.720000 --> 0:09:28.320000
 So in peer to peer, we're really talking
 about routing protocol peering.

0:09:28.320000 --> 0:09:30.300000
 Who are you peering with?

0:09:30.300000 --> 0:09:34.960000
 In some types of VPNs, your router, your
 customer premises router is actually

0:09:34.960000 --> 0:09:39.620000
 forming a routing relationship, an EIGRP
 neighbor relationship, an OSPF

0:09:39.620000 --> 0:09:43.320000
 neighbor relationship
 with the ISPs router.

0:09:43.320000 --> 0:09:46.180000
 And then you, the two of you are exchanging
 routes and you are relying

0:09:46.180000 --> 0:09:51.140000
 on the ISP to really get heavily involved
 here to transfer those routes

0:09:51.140000 --> 0:09:54.380000
 all the way to the other
 end to your other site.

0:09:54.380000 --> 0:09:56.520000
 So that's called a peer
 to peer router.

0:09:56.520000 --> 0:10:00.660000
 So in this particular case, the service
 provider is not only giving you

0:10:00.660000 --> 0:10:05.540000
 your physical and data link layer connectivity
 to the VPN, it's also providing

0:10:05.540000 --> 0:10:08.980000
 you layer three connectivity because
 you're doing routing with them with

0:10:08.980000 --> 0:10:10.120000
 the service provider.

0:10:10.120000 --> 0:10:15.280000
 The other type of VPN is something
 called an overlay VPN.

0:10:15.280000 --> 0:10:19.560000
 This is the type of VPN where the service
 provider, all they're doing

0:10:19.560000 --> 0:10:22.140000
 is giving you connectivity
 to their cloud.

0:10:22.140000 --> 0:10:24.320000
 You're not actually doing
 routing with them.

0:10:24.320000 --> 0:10:27.100000
 So with the service provider, they're
 providing you like your physical

0:10:27.100000 --> 0:10:29.060000
 and your data link
 layer connectivity.

0:10:29.060000 --> 0:10:33.100000
 They're setting up your physical circuits
 from one point to the other.

0:10:33.100000 --> 0:10:38.200000
 But as far as actual routing protocols
 are concerned, your router in spoke

0:10:38.200000 --> 0:10:44.620000
 location one is actually forming an EIGRP
 or an OSPF neighbor relationship

0:10:44.620000 --> 0:10:48.420000
 with your hub router, which is hundreds
 or maybe even thousands of miles

0:10:48.420000 --> 0:10:55.320000
 away. And so the VPN is just being
 overlaid or laid on top of whatever

0:10:55.320000 --> 0:10:58.560000
 transport mechanism the ISP
 is actually giving you.

0:10:58.560000 --> 0:11:00.560000
 So they're just giving
 you the physical path.

0:11:00.560000 --> 0:11:03.680000
 They're providing like the street, but
 you're the one who's actually driving

0:11:03.680000 --> 0:11:06.000000
 the car across the street.

0:11:06.000000 --> 0:11:09.360000
 So that would be like
 an overlay VPN.

0:11:09.360000 --> 0:11:15.200000
 And a couple of additional terms,
 client side or site side VPN.

0:11:15.200000 --> 0:11:20.620000
 So all the examples I've given you so
 far are called site to site VPNs.

0:11:20.620000 --> 0:11:22.120000
 What does that mean?

0:11:22.120000 --> 0:11:27.060000
 Well, that means that there is some networking
 device, typically a router

0:11:27.060000 --> 0:11:29.440000
 or some sort of security
 appliance.

0:11:29.440000 --> 0:11:34.240000
 And that device sitting at the edge
 of your customer network is the one

0:11:34.240000 --> 0:11:35.900000
 that's implementing the tunnel.

0:11:35.900000 --> 0:11:40.020000
 That's the one that's encrypting and
 decrypting all the traffic that's

0:11:40.020000 --> 0:11:42.020000
 implementing all the VPN policies.


0:11:42.020000 --> 0:11:46.640000
 So the laptops, the PCs, the tablets
 in your company, they don't have

0:11:46.640000 --> 0:11:48.520000
 to know anything about what's
 getting involved.

0:11:48.520000 --> 0:11:51.600000
 All they're doing is just generating
 Ethernet frames, just generating

0:11:51.600000 --> 0:11:54.600000
 IP packets and folding
 into the network.

0:11:54.600000 --> 0:11:58.680000
 Eventually, those packets reach that edge
 router that does all the encryption

0:11:58.680000 --> 0:12:00.340000
 that does all the tunneling.

0:12:00.340000 --> 0:12:05.300000
 So from one site to another site, everything
 from one site to another

0:12:05.300000 --> 0:12:08.640000
 site is being encrypted by these
 network infrastructure devices.

0:12:08.640000 --> 0:12:11.780000
 That's called a site to site VPN.

0:12:11.780000 --> 0:12:16.200000
 A client VPN is like it says here,
 something typically initiated by a

0:12:16.200000 --> 0:12:19.780000
 client. For example, for those of you
 who are watching this video who

0:12:19.780000 --> 0:12:23.080000
 might be able to telecommute,
 maybe you work from home.

0:12:23.080000 --> 0:12:26.020000
 A lot of times what companies will do
 is if you work from home, they'll

0:12:26.020000 --> 0:12:30.440000
 install on your laptop some VPN software,
 which might look something like

0:12:30.440000 --> 0:12:36.520000
 this, where this is an example of Cisco's
 AnyConnect Secure Mobility Client.

0:12:36.520000 --> 0:12:38.840000
 This is an example
 of VPN software.

0:12:38.840000 --> 0:12:43.820000
 So on your laptop, you actually double
 click this, you open it up, you

0:12:43.820000 --> 0:12:47.040000
 type in your credentials, whatever
 your company has given you.

0:12:47.040000 --> 0:12:51.600000
 And now that tunnel that security is
 actually being implemented from your

0:12:51.600000 --> 0:12:56.120000
 laptop, your laptop is one end of the
 tunnel going all the way to probably

0:12:56.120000 --> 0:12:58.460000
 a router or something at your
 corporate headquarters.

0:12:58.460000 --> 0:13:01.560000
 And that's terminating the
 tunnel on the other side.

0:13:01.560000 --> 0:13:05.900000
 So now the VPN is extending all
 the way to you, the client.

0:13:05.900000 --> 0:13:07.680000
 You are one end of that VPN.

0:13:07.680000 --> 0:13:11.540000
 And so that is called
 a client side VPN.

0:13:11.540000 --> 0:13:15.900000
 So where are some typical
 expectations of a VPN?

0:13:15.900000 --> 0:13:17.740000
 You know, why would
 people use these?

0:13:17.740000 --> 0:13:20.180000
 What are they hoping
 to get out of a VPN?

0:13:20.180000 --> 0:13:22.900000
 Well, number one, route
 exchange privacy.

0:13:22.900000 --> 0:13:27.140000
 In other words, if I'm doing routing
 into this VPN, whether I am peering

0:13:27.140000 --> 0:13:31.140000
 with my service provider and I'm sending
 them my routes, or my service

0:13:31.140000 --> 0:13:34.560000
 provider is just providing me the pathway
 and I'm peering with the route

0:13:34.560000 --> 0:13:38.220000
 with my own router at the other end of
 that tunnel that might be 300 miles

0:13:38.220000 --> 0:13:43.620000
 away. Either way, when I send routes
 into that cloud that I don't own,

0:13:43.620000 --> 0:13:47.520000
 that network infrastructure that I'm
 renting, I need some assurances that

0:13:47.520000 --> 0:13:50.600000
 my routes will not
 go to anybody else.

0:13:50.600000 --> 0:13:55.080000
 My routes will only go to where they're
 supposed to go that I won't accidentally

0:13:55.080000 --> 0:13:57.480000
 learn of routes from
 somebody else.

0:13:57.480000 --> 0:14:01.900000
 If you watched the video I did before
 this one on MPLS VPNs, I mentioned

0:14:01.900000 --> 0:14:06.160000
 how one of the primary benefits of
 MPLS VPNs from a service provider's

0:14:06.160000 --> 0:14:09.620000
 perspective is that they could have
 two different customers and give the

0:14:09.620000 --> 0:14:12.260000
 customers the exact same networks.


0:14:12.260000 --> 0:14:15.980000
 This customer could be the 2020 network
 and this customer could be the

0:14:15.980000 --> 0:14:20.000000
 2020 network. Well, the only way that's
 going to work is if we have route

0:14:20.000000 --> 0:14:24.120000
 privacy. In other words, if the service
 provider somehow has some mechanisms

0:14:24.120000 --> 0:14:28.840000
 in place that he knows that packets
 from customer A should only go to

0:14:28.840000 --> 0:14:32.960000
 customer A and packets from customer
 B should only go to customer B.

0:14:32.960000 --> 0:14:36.940000
 Even if they're using the same subnet,
 the service provider, the VPN has

0:14:36.940000 --> 0:14:40.180000
 to have some way of keeping those
 separated from each other.

0:14:40.180000 --> 0:14:43.960000
 That's what we mean by
 route exchange privacy.

0:14:43.960000 --> 0:14:46.220000
 And path, determination
 for packets.

0:14:46.220000 --> 0:14:47.240000
 Same type of thing.

0:14:47.240000 --> 0:14:50.840000
 We want to make sure that when I put
 a packet into my VPN, there is no

0:14:50.840000 --> 0:14:54.100000
 way that packet could end up
 on my competitor's network.

0:14:54.100000 --> 0:14:57.620000
 There's no way that packet could accidentally
 be leaked out into the internet

0:14:57.620000 --> 0:14:58.860000
 for everybody to see.

0:14:58.860000 --> 0:15:00.820000
 It should only go to one place.

0:15:00.820000 --> 0:15:05.440000
 The other end of this VPN and the other
 end of the VPN belongs to me.

0:15:05.440000 --> 0:15:07.860000
 It's my site. It's my secure site.


0:15:07.860000 --> 0:15:11.260000
 So I want some assurance that my packets
 will go where they're supposed

0:15:11.260000 --> 0:15:15.280000
 to go. And then lastly,
 data security.

0:15:15.280000 --> 0:15:20.540000
 If Heavens forbid someone's able to actually
 intercept my packet, I don't

0:15:20.540000 --> 0:15:22.680000
 want them to be able to tell
 what's inside of it.

0:15:22.680000 --> 0:15:25.860000
 And this is where we would typically use
 something called IPsec, IP security,

0:15:25.860000 --> 0:15:30.580000
 which I'll look at in a real high level
 in just one second after the slide.

0:15:30.580000 --> 0:15:35.000000
 But data security says, I want to encrypt
 this packet so that only the

0:15:35.000000 --> 0:15:39.660000
 actual intended recipient, the person
 who's really supposed to get it,

0:15:39.660000 --> 0:15:42.240000
 will actually be able to read
 it and understand it.

0:15:42.240000 --> 0:15:46.420000
 If anybody else sees that packet who
 it is not meant for, they won't be

0:15:46.420000 --> 0:15:47.600000
 able to tell what's inside of it.

0:15:47.600000 --> 0:15:49.000000
 They won't know what it is.

0:15:49.000000 --> 0:15:51.400000
 So I want data security.

0:15:51.400000 --> 0:15:56.580000
 So typically, IPsec, which stands for
 IP security, is what's used for

0:15:56.580000 --> 0:16:01.660000
 this. So IP security is sort of like
 an umbrella term for a whole bunch

0:16:01.660000 --> 0:16:05.840000
 of protocols. And you sort of get to pick
 and choose which of these security

0:16:05.840000 --> 0:16:09.840000
 protocols that fall under the umbrella
 of IPsec that you actually want

0:16:09.840000 --> 0:16:13.640000
 to use to secure your network,
 to secure your VPN.

0:16:13.640000 --> 0:16:18.820000
 So depending on which protocols you
 choose, IPsec can provide any or all

0:16:18.820000 --> 0:16:22.560000
 of these four things right here.

0:16:22.560000 --> 0:16:27.160000
 So all these protocols within IPsec are
 defined in a wide variety of RFCs.

0:16:27.160000 --> 0:16:30.840000
 There's not just one RFC that
 says, here's how you do IPsec.

0:16:30.840000 --> 0:16:34.400000
 Because we're talking about literally
 dozens of different protocols that

0:16:34.400000 --> 0:16:38.320000
 can do these types of things,
 each one has its own RFC.

0:16:38.320000 --> 0:16:40.880000
 And a lot of times there's multiple
 versions of the RFC.

0:16:40.880000 --> 0:16:43.940000
 So IPsec is just the
 umbrella term.

0:16:43.940000 --> 0:16:47.740000
 So depending on what protocols you select,
 you might get confidentiality.

0:16:47.740000 --> 0:16:50.060000
 So confidentiality is like
 what I was talking about.

0:16:50.060000 --> 0:16:53.260000
 That's typically what we mean by
 when we say data encryption.

0:16:53.260000 --> 0:16:54.680000
 The data is confidential.

0:16:54.680000 --> 0:16:58.900000
 Someone can't see what's in the body
 of that packet unless they are the

0:16:58.900000 --> 0:17:00.240000
 intended recipient.

0:17:00.240000 --> 0:17:02.260000
 That packet is confidential.

0:17:02.260000 --> 0:17:07.900000
 Integrity means we have some way of
 checking to see if anything in that

0:17:07.900000 --> 0:17:11.100000
 packet has been changed
 in transit.

0:17:11.100000 --> 0:17:14.420000
 You know, when someone was sending
 a bank transfer and trying to do a

0:17:14.420000 --> 0:17:18.420000
 deposit, is there some way that a zero
 is lost and they're trying to deposit

0:17:18.420000 --> 0:17:22.120000
 $1,000 and it showed up
 at the bank as $100?

0:17:22.120000 --> 0:17:25.160000
 That would be an example
 of a loss of integrity.

0:17:25.160000 --> 0:17:27.700000
 So some IPsec protocols
 can detect that.

0:17:27.700000 --> 0:17:29.380000
 They can say, wait a second here.

0:17:29.380000 --> 0:17:35.960000
 This packet isn't exactly the same as
 when it first left the originator.

0:17:35.960000 --> 0:17:37.460000
 Something's been changed.

0:17:37.460000 --> 0:17:38.700000
 I've checked the integrity.

0:17:38.700000 --> 0:17:40.200000
 Something's wrong here.

0:17:40.200000 --> 0:17:42.760000
 Integrity checking.

0:17:42.760000 --> 0:17:45.160000
 Authentication. This is like what we
 talked about when we talked about

0:17:45.160000 --> 0:17:46.520000
 the point-to-point protocol.

0:17:46.520000 --> 0:17:50.420000
 Authentication simply means, hey, before
 I send something to you, I need

0:17:50.420000 --> 0:17:53.280000
 to make sure you are who
 you really say you are.

0:17:53.280000 --> 0:17:56.760000
 How do I know that you're the person
 I'm supposed to be talking to?

0:17:56.760000 --> 0:17:59.340000
 So there's IPsec protocols
 that can do that.

0:17:59.340000 --> 0:18:01.800000
 Do that verification
 of authentication.

0:18:01.800000 --> 0:18:04.540000
 And then the last one
 is anti-replay.

0:18:04.540000 --> 0:18:08.820000
 Anti-replay would be something like,
 okay, let's say that somebody was

0:18:08.820000 --> 0:18:14.020000
 watching our conversation and maybe they
 can't see the body of the packet,

0:18:14.020000 --> 0:18:18.320000
 but they get enough information that
 they can spoof me and now they can

0:18:18.320000 --> 0:18:22.900000
 get free internet access because they
 send packets to you that look like

0:18:22.900000 --> 0:18:25.540000
 they were coming from me when
 reality, they weren't.

0:18:25.540000 --> 0:18:29.520000
 They just took my packets, copied
 them, and recent them to you.

0:18:29.520000 --> 0:18:32.260000
 So you're actually getting duplicate
 copies of packets.

0:18:32.260000 --> 0:18:35.380000
 Packets are being replayed to you.


0:18:35.380000 --> 0:18:37.840000
 So anti-replay says, how
 do we prevent that?

0:18:37.840000 --> 0:18:41.300000
 How do we prevent people from capturing
 packets and replaying them back

0:18:41.300000 --> 0:18:42.500000
 into the network?

0:18:42.500000 --> 0:18:44.540000
 How do we detect that
 that's happening?

0:18:44.540000 --> 0:18:47.900000
 So there's various collections of security
 standards with an IPsec that

0:18:47.900000 --> 0:18:53.100000
 can prevent that kind of thing or detect
 that kind of thing from happening.

0:18:53.100000 --> 0:18:58.500000
 So that concludes this video on an overview
 and an introduction of virtual

0:18:58.500000 --> 0:18:59.760000
 private networks.

