WEBVTT - This file was automatically generated by VIMEO

1
00:00:08.600 --> 00:00:11.100
 Tell me one, welcome back. Let's take a

2
00:00:11.100 --> 00:00:15.200
 look at. How do you secure the Network's? Such an eye chart in attacks?

3
00:00:16.700 --> 00:00:19.600
 One of the biggest things that I would really like to touch upon is

4
00:00:19.600 --> 00:00:22.300
 that it will be open in such a way that

5
00:00:22.300 --> 00:00:24.800
 a communication is always being sent in plain text.

6
00:00:25.800 --> 00:00:29.000
 As we have looked at the various attack vectors, most

7
00:00:28.100 --> 00:00:31.400
 of the cases tackle sitting on the same network,

8
00:00:31.600 --> 00:00:34.300
 was able to snap the data since it was been sent in,

9
00:00:34.300 --> 00:00:37.800
 plain text format, and either reader sensitive information,

10
00:00:37.100 --> 00:00:40.300
 or he was able to read the package that

11
00:00:40.300 --> 00:00:43.300
 are being sent and perform various applicable such

12
00:00:43.300 --> 00:00:44.300
 an adjustment techniques.

13
00:00:45.500 --> 00:00:48.200
 So, in order to prevent all of this mandible attack, we should

14
00:00:48.200 --> 00:00:50.900
 ensure that we Implement PLS in please.

15
00:00:52.500 --> 00:00:55.200
 So what do I mean by that? Is that the name of you

16
00:00:55.200 --> 00:00:58.200
 protocols starting with HTTP. That

17
00:00:58.200 --> 00:01:02.500
 is being used by all of our web servers by default. So

18
00:01:02.500 --> 00:01:06.300
 if we Implement HTTP as a protocol, that

19
00:01:06.300 --> 00:01:09.200
 is going to ensure that all the data is being sent in plain

20
00:01:09.200 --> 00:01:09.700
 text.

21
00:01:10.800 --> 00:01:14.000
 We need to ensure that we add an additional capability

22
00:01:13.400 --> 00:01:16.900
 of SSL layer. That

23
00:01:16.900 --> 00:01:19.900
 means we need to generate SSL certificates that

24
00:01:19.900 --> 00:01:22.600
 are added on top of this protocol in

25
00:01:22.600 --> 00:01:25.600
 such a way that the data is being sent on HTTP

26
00:01:25.600 --> 00:01:28.400
 protocol, one link. So that even though

27
00:01:28.400 --> 00:01:31.400
 attacker title snifter data, it will always be encrypted

28
00:01:31.400 --> 00:01:34.500
 in nature. One of the protocol that

29
00:01:34.500 --> 00:01:37.500
 is commonly used in the industry is FTP.

30
00:01:38.400 --> 00:01:40.600
 This is useful for file transfer mechanisms.

31
00:01:41.800 --> 00:01:44.100
 So even this spring protocol horses, the

32
00:01:44.100 --> 00:01:47.100
 same Threat by default FTP, you

33
00:01:47.100 --> 00:01:50.100
 always send data in plain text. In

34
00:01:50.100 --> 00:01:53.400
 order to prevent this either. We have an

35
00:01:53.400 --> 00:01:56.700
 alternative of adding SSL here so that we

36
00:01:56.700 --> 00:01:59.800
 initiate ftps connection. So

37
00:01:59.800 --> 00:02:01.300
 that data is always encrypted.

38
00:02:02.500 --> 00:02:07.100
 One of the alternative could be using SFTP, SFTP

39
00:02:06.100 --> 00:02:09.800
 would be running on top of SSH, and ensuring the

40
00:02:09.800 --> 00:02:11.200
 data is always encrypted.

41
00:02:12.800 --> 00:02:15.600
 On a fur companies use

42
00:02:15.700 --> 00:02:18.500
 email exchange protocol such as IMAP and POP

43
00:02:18.500 --> 00:02:22.000
 and even SMTP all of these particular protocols.

44
00:02:23.100 --> 00:02:26.200
 Can also be implemented using TLS and SSL so

45
00:02:26.200 --> 00:02:29.700
 that always sensitive communication. Always happen to

46
00:02:29.700 --> 00:02:30.500
 encrypted Channel.

47
00:02:31.600 --> 00:02:34.300
 So now, take a let's take a look at different secure.

48
00:02:34.300 --> 00:02:37.700
 Protocols. For example, when we talk about

49
00:02:37.700 --> 00:02:40.300
 telnet itself, which we actually

50
00:02:40.300 --> 00:02:43.400
 saw, which actually opens up a

51
00:02:43.400 --> 00:02:46.200
 bi-directional connection and it also has

52
00:02:46.200 --> 00:02:49.800
 the same vulnerability, but instead of using telnet

53
00:02:49.800 --> 00:02:52.500
 as a protocol itself, we can actually switch to

54
00:02:52.500 --> 00:02:55.400
 SSH as a protocol that says it

55
00:02:55.400 --> 00:02:56.500
 will also provide.

56
00:02:57.500 --> 00:03:01.100
 The same mechanism in order to login and this

57
00:03:00.100 --> 00:03:03.700
 will actually create an encrypted tunnel. Ensuring

58
00:03:03.700 --> 00:03:06.300
 the data is always encrypted and solid between the

59
00:03:06.300 --> 00:03:07.100
 two endpoints.

60
00:03:08.300 --> 00:03:11.200
 In cases where SSH can Darcy not

61
00:03:11.200 --> 00:03:15.800
 be used and we want to connect to and critical infrastructure. We

62
00:03:15.800 --> 00:03:18.400
 can use VPN. So these would be the

63
00:03:18.400 --> 00:03:22.600
 virtual private networks. That always run establishing

64
00:03:21.600 --> 00:03:24.300
 a secret tunnel between the

65
00:03:24.300 --> 00:03:27.200
 endpoint and the network. So in even trying

66
00:03:27.200 --> 00:03:29.900
 to skip the traffic between the endpoint,

67
00:03:31.100 --> 00:03:34.300
 And the particular for such a network. It will always

68
00:03:34.300 --> 00:03:37.800
 be encrypted. So these two protocol can

69
00:03:37.800 --> 00:03:40.600
 always suffice the need wherever we

70
00:03:40.600 --> 00:03:43.500
 need to have secure, protocols

71
00:03:43.500 --> 00:03:45.300
 implemented to encrypt traffic.

72
00:03:47.100 --> 00:03:48.700
 That's it for this video. Thank you.
