WEBVTT

1
00:00:00.000 --> 00:00:01.260
In this lesson,

2
00:00:01.260 --> 00:00:04.230
we will learn about application management.

3
00:00:04.230 --> 00:00:07.110
Application management involves overseeing

4
00:00:07.110 --> 00:00:09.060
and controlling applications

5
00:00:09.060 --> 00:00:12.090
to ensure they do not introduce vulnerabilities

6
00:00:12.090 --> 00:00:16.440
into the network or compromise enterprise system integrity.

7
00:00:16.440 --> 00:00:21.060
Application management concepts include application control

8
00:00:21.060 --> 00:00:22.950
and browser isolation.

9
00:00:22.950 --> 00:00:26.160
Application control utilizes policies

10
00:00:26.160 --> 00:00:27.810
and tools to restrict

11
00:00:27.810 --> 00:00:31.410
what applications can run on a given system.

12
00:00:31.410 --> 00:00:34.260
Browser isolation uses technology

13
00:00:34.260 --> 00:00:36.750
to separate web browsing activities

14
00:00:36.750 --> 00:00:39.210
from the rest of the operating system.

15
00:00:39.210 --> 00:00:42.240
Let's learn more about application control

16
00:00:42.240 --> 00:00:44.280
and browser isolation.

17
00:00:44.280 --> 00:00:47.400
First, we have application control.

18
00:00:47.400 --> 00:00:51.750
Application control is a security measure that uses policies

19
00:00:51.750 --> 00:00:56.190
and tools to decide which applications can run on a system,

20
00:00:56.190 --> 00:00:58.200
helping to prevent unauthorized

21
00:00:58.200 --> 00:01:01.530
or malicious software from compromising the network.

22
00:01:01.530 --> 00:01:04.170
This approach allows organizations

23
00:01:04.170 --> 00:01:07.110
to implement a granular level of control

24
00:01:07.110 --> 00:01:10.740
using application allow lists and block lists,

25
00:01:10.740 --> 00:01:14.910
which were formally known as whitelists and blacklists.

26
00:01:14.910 --> 00:01:16.980
Allow lists are used to manage

27
00:01:16.980 --> 00:01:19.380
which applications are permitted.

28
00:01:19.380 --> 00:01:22.650
Block lists specifically identify applications

29
00:01:22.650 --> 00:01:24.330
which are not permitted.

30
00:01:24.330 --> 00:01:27.240
For example, companies can block games

31
00:01:27.240 --> 00:01:30.840
or unapproved software that could distract employees

32
00:01:30.840 --> 00:01:32.610
or contain malicious code,

33
00:01:32.610 --> 00:01:36.180
ensuring that only safe and productive applications

34
00:01:36.180 --> 00:01:37.110
are used.

35
00:01:37.110 --> 00:01:39.750
Application control can be implemented

36
00:01:39.750 --> 00:01:43.380
through technologies like Windows Group Policy,

37
00:01:43.380 --> 00:01:46.830
where administrators define rules that restrict

38
00:01:46.830 --> 00:01:49.290
or allow software installations.

39
00:01:49.290 --> 00:01:53.160
Once complete, allow and block list rules are pushed

40
00:01:53.160 --> 00:01:55.590
to all workstations in the domain,

41
00:01:55.590 --> 00:01:58.860
preventing unauthorized or unapproved software

42
00:01:58.860 --> 00:02:01.470
from being installed on the systems.

43
00:02:01.470 --> 00:02:04.290
More advanced solutions like host-based

44
00:02:04.290 --> 00:02:07.230
intrusion prevention systems can go beyond

45
00:02:07.230 --> 00:02:09.810
and block not just installations,

46
00:02:09.810 --> 00:02:13.050
but also the execution of certain files,

47
00:02:13.050 --> 00:02:15.270
such as portable executables,

48
00:02:15.270 --> 00:02:18.120
which can run without needing to be installed.

49
00:02:18.120 --> 00:02:21.360
This provides even tighter security measures

50
00:02:21.360 --> 00:02:24.900
by stopping potentially harmful software applications

51
00:02:24.900 --> 00:02:26.970
from running in the first place.

52
00:02:26.970 --> 00:02:28.680
By using these controls,

53
00:02:28.680 --> 00:02:32.040
organizations can maintain a secure baseline,

54
00:02:32.040 --> 00:02:33.990
reduce the risk of attacks,

55
00:02:33.990 --> 00:02:37.590
and ensure that only authorized applications operate

56
00:02:37.590 --> 00:02:39.180
within their environment.

57
00:02:39.180 --> 00:02:42.330
Second, we have browser isolation.

58
00:02:42.330 --> 00:02:45.330
Browser isolation is a security technique

59
00:02:45.330 --> 00:02:47.820
that separates web browsing activities

60
00:02:47.820 --> 00:02:49.740
from the rest of the system,

61
00:02:49.740 --> 00:02:52.530
preventing web-based threats from spreading

62
00:02:52.530 --> 00:02:54.480
to other parts of the network.

63
00:02:54.480 --> 00:02:57.570
It works by isolating the browser environment

64
00:02:57.570 --> 00:03:02.040
on a virtual machine, remote server, or secure container,

65
00:03:02.040 --> 00:03:04.170
creating a protective barrier

66
00:03:04.170 --> 00:03:06.930
between potentially dangerous websites

67
00:03:06.930 --> 00:03:09.270
and the main operating system.

68
00:03:09.270 --> 00:03:12.900
This approach ensures that any malicious content,

69
00:03:12.900 --> 00:03:17.730
such as drive by downloads, malware, or harmful scripts

70
00:03:17.730 --> 00:03:21.090
remain contained within the isolated environment,

71
00:03:21.090 --> 00:03:24.780
keeping the host and its connected systems safe.

72
00:03:24.780 --> 00:03:26.790
In an enterprise environment,

73
00:03:26.790 --> 00:03:29.010
browser isolation can be applied

74
00:03:29.010 --> 00:03:31.560
as either a cloud-based service

75
00:03:31.560 --> 00:03:33.870
or an on-premises solution,

76
00:03:33.870 --> 00:03:36.900
integrated with existing security infrastructure,

77
00:03:36.900 --> 00:03:40.440
such as secure web gateways or firewalls.

78
00:03:40.440 --> 00:03:44.160
Furthermore, administrators can configure these solutions

79
00:03:44.160 --> 00:03:46.020
to route all web traffic

80
00:03:46.020 --> 00:03:50.310
through isolated environments based on predefined policies.

81
00:03:50.310 --> 00:03:54.120
For instance, high risk websites or browsing activities

82
00:03:54.120 --> 00:03:58.260
by specific user groups can be automatically isolated,

83
00:03:58.260 --> 00:04:00.420
ensuring threats are processed

84
00:04:00.420 --> 00:04:03.420
and contained away from the endpoint.

85
00:04:03.420 --> 00:04:06.690
Additionally, policies can be fine tuned

86
00:04:06.690 --> 00:04:09.450
to control which websites are isolated,

87
00:04:09.450 --> 00:04:11.880
enforce read-only browsing modes,

88
00:04:11.880 --> 00:04:14.400
or block downloads entirely

89
00:04:14.400 --> 00:04:17.250
to prevent potential malware infection.

90
00:04:17.250 --> 00:04:21.390
In enterprise systems, browser isolation solutions

91
00:04:21.390 --> 00:04:25.350
can be managed through centralized administration consoles,

92
00:04:25.350 --> 00:04:28.950
where security teams can monitor browsing activities,

93
00:04:28.950 --> 00:04:30.990
adjust isolation rules,

94
00:04:30.990 --> 00:04:34.350
and update security policies as needed.

95
00:04:34.350 --> 00:04:38.760
Some advanced configurations allow for dynamic isolation

96
00:04:38.760 --> 00:04:41.190
based on real-time risk assessments,

97
00:04:41.190 --> 00:04:43.560
adapting the level of isolation

98
00:04:43.560 --> 00:04:47.580
based on the site's reputation or the user's behavior.

99
00:04:47.580 --> 00:04:50.010
By implementing browser isolation,

100
00:04:50.010 --> 00:04:53.400
organizations not only reduce the attack surface

101
00:04:53.400 --> 00:04:54.900
from web-based threats,

102
00:04:54.900 --> 00:04:59.400
but they also maintain control over web browsing activities.

103
00:04:59.400 --> 00:05:01.350
So remember,

104
00:05:01.350 --> 00:05:04.500
application management involves controlling

105
00:05:04.500 --> 00:05:06.720
and overseeing applications

106
00:05:06.720 --> 00:05:09.870
to ensure they do not introduce vulnerabilities

107
00:05:09.870 --> 00:05:12.330
or compromise system integrity.

108
00:05:12.330 --> 00:05:15.150
Key aspects of application management

109
00:05:15.150 --> 00:05:19.500
include application control and browser isolation.

110
00:05:19.500 --> 00:05:22.200
Application control uses policies

111
00:05:22.200 --> 00:05:26.430
and tools to decide which applications can run on a system,

112
00:05:26.430 --> 00:05:29.160
helping to prevent unauthorized software

113
00:05:29.160 --> 00:05:31.320
from compromising the network.

114
00:05:31.320 --> 00:05:33.570
Browser isolation, on the other hand,

115
00:05:33.570 --> 00:05:38.130
separates web browsing activities from the operating system,

116
00:05:38.130 --> 00:05:40.260
creating a secure barrier

117
00:05:40.260 --> 00:05:42.600
that contains any malicious content

118
00:05:42.600 --> 00:05:44.790
within a protected environment.

119
00:05:44.790 --> 00:05:49.620
Together these measures maintain security, minimize risks,

120
00:05:49.620 --> 00:05:53.160
and ensure that only safe and approved applications

121
00:05:53.160 --> 00:05:56.493
and activities are allowed within networks.