1
00:00:01,240 --> 00:00:03,920
In summary, what have we learned in this first lesson?

2
00:00:03,920 --> 00:00:08,510
Well, there was certainly a time when Group Policy was the only way,

3
00:00:08,510 --> 00:00:13,090
the only first party Microsoft way, for truly enforcing system

4
00:00:13,090 --> 00:00:16,370
security. And we've seen subsequently a number of trends,

5
00:00:16,370 --> 00:00:19,470
most of which, let's see if all of these I've integrated into

6
00:00:19,470 --> 00:00:23,240
this training, yeah, cloud‑based AI algorithms,

7
00:00:23,240 --> 00:00:26,200
hybrid cloud integration, being able to reach across

8
00:00:26,200 --> 00:00:28,070
not just a dedicated connection,

9
00:00:28,070 --> 00:00:33,040
like a site‑to‑site virtual private network, or an ExpressRoute circuit,

10
00:00:33,040 --> 00:00:36,930
but also just simply native cloud deployments.

11
00:00:36,930 --> 00:00:39,850
You can include those machines and manage them centrally

12
00:00:39,850 --> 00:00:41,600
in Azure in a number of different ways.

13
00:00:41,600 --> 00:00:45,340
Azure Arc for servers comes to mind principally. We also have

14
00:00:45,340 --> 00:00:49,830
the trend of really working to lock down the hardware, such

15
00:00:49,830 --> 00:00:51,750
that the server, when it's booted,

16
00:00:51,750 --> 00:00:57,840
it will only boot trusted code. You've got hopefully drive encryption,

17
00:00:57,840 --> 00:01:03,290
like BitLocker, coming into the situation. And then once the server is

18
00:01:03,290 --> 00:01:07,560
booted and its services are running, only, again, trusted and allowed

19
00:01:07,560 --> 00:01:11,850
device drivers in code or running and anything that's not explicitly

20
00:01:11,850 --> 00:01:13,380
allowed will be blocked.

21
00:01:13,380 --> 00:01:17,340
That's an ideal situation, but it's a good one.

22
00:01:17,340 --> 00:01:20,450
So you might be saying now that's cool about the computers

23
00:01:20,450 --> 00:01:24,100
and the server security, but it's our users who tend to get

24
00:01:24,100 --> 00:01:25,500
into trouble most of the time.

25
00:01:25,500 --> 00:01:31,210
What can we do in the Hybrid Cloud Windows Server Administrator role to help

26
00:01:31,210 --> 00:01:34,470
these users and to protect their identities? Well, of course,

27
00:01:34,470 --> 00:01:39,210
as usual, I like to lead you and transition you from module to module.

28
00:01:39,210 --> 00:01:42,850
So I will see you in the next module entitled Secure

29
00:01:42,850 --> 00:01:48,000
Hybrid Active Directory Accounts. Thanks for your attention. Happy studying!