WEBVTT
Kind: captions
Language: en

1
00:00:00.000 --> 00:00:06.705
Welcome to Domain 2, Security and Compliance, which is thirty percent of the scored exam.

2
00:00:06.705 --> 00:00:13.712
This lesson covers task 2.1: the AWS shared responsibility model. It's one of the most tested

3
00:00:13.712 --> 00:00:20.870
ideas on the whole exam. We'll cover two ideas. First, the split between security of the cloud,

4
00:00:20.870 --> 00:00:28.479
which is AWS's job, and security in the cloud, which is yours. Second, how that split moves depending

5
00:00:28.479 --> 00:00:33.000
on the service, using Amazon EC2, Amazon RDS and AWS Lambda.

6
00:00:33.400 --> 00:00:39.758
In its own data center, our online store secured everything: the data and apps,

7
00:00:39.758 --> 00:00:45.955
the servers and network, even the building, the power and the guards. On AWS,

8
00:00:45.955 --> 00:00:53.520
the store rents part of a much larger system, so the work is split. AWS takes the lower layers

9
00:00:53.520 --> 00:01:01.086
and the store keeps the top ones. The model exists so that both sides know exactly where their

10
00:01:01.086 --> 00:01:06.800
duties begin and end, and nobody assumes the other side has it covered.

11
00:01:07.200 --> 00:01:13.326
Start at the bottom. AWS is responsible for security of the cloud: protecting the infrastructure

12
00:01:13.326 --> 00:01:19.068
that runs every AWS service. That means the hardware, software, networking and facilities.

13
00:01:19.068 --> 00:01:24.492
Think data center buildings, guards, power and cooling, the servers and network gear,

14
00:01:24.492 --> 00:01:30.426
the host operating system and virtualization layer, and the global infrastructure of Regions,

15
00:01:30.426 --> 00:01:35.148
Availability Zones and edge locations. Customers can't touch these layers,

16
00:01:35.148 --> 00:01:37.700
so they inherit these controls from AWS.

17
00:01:38.100 --> 00:01:43.181
Above the line is security in the cloud, and that's the customer's job.

18
00:01:43.181 --> 00:01:48.621
The store always owns its data, including how it's classified and encrypted,

19
00:01:48.621 --> 00:01:54.275
and who can access it through IAM users, roles and multi-factor authentication.

20
00:01:54.275 --> 00:02:00.429
On servers it runs, it patches the guest operating system and configures the firewall,

21
00:02:00.429 --> 00:02:07.300
called a security group. How much sits above the line depends on the services the store chooses.

22
00:02:07.700 --> 00:02:12.917
Some controls are shared: the same topic, but each side does it in its own layer.

23
00:02:12.917 --> 00:02:18.971
Patch management: AWS patches its infrastructure, and the customer patches its guest operating

24
00:02:18.971 --> 00:02:24.316
systems and applications. Configuration management: AWS configures its own devices,

25
00:02:24.316 --> 00:02:30.370
and the customer configures its operating systems, databases and apps. Awareness and training:

26
00:02:30.370 --> 00:02:36.295
AWS trains its employees, and the store trains its own. Physical and environmental controls,

27
00:02:36.295 --> 00:02:39.000
by contrast, are fully inherited from AWS.

28
00:02:39.400 --> 00:02:46.550
Now watch the line move. Amazon EC2 is infrastructure as a service. The store gets a virtual server,

29
00:02:46.550 --> 00:02:53.342
and everything from the guest operating system up is the store's job: installing OS updates and

30
00:02:53.342 --> 00:02:59.848
security patches, the software it adds, and the security group rules. AWS handles the host,

31
00:02:59.848 --> 00:03:06.068
the virtualization layer, the hardware and the facilities. With EC2, the line sits low,

32
00:03:06.068 --> 00:03:09.500
so the customer carries the most responsibility.

33
00:03:09.900 --> 00:03:15.362
Next, the store moves its database to Amazon RDS, a managed database service.

34
00:03:15.362 --> 00:03:20.682
Now AWS patches the database engine and the operating system underneath it,

35
00:03:20.682 --> 00:03:25.790
during a maintenance window the store can choose, and automates backups.

36
00:03:25.790 --> 00:03:31.748
The line moves up. But the store still creates database users and their permissions,

37
00:03:31.748 --> 00:03:36.927
sets the network rules in security groups, chooses to turn on encryption,

38
00:03:36.927 --> 00:03:38.700
and owns the data itself.

39
00:03:39.100 --> 00:03:45.458
With AWS Lambda, the line moves higher still. Lambda runs the store's code without servers to

40
00:03:45.458 --> 00:03:51.952
manage. AWS manages the infrastructure, the operating system and the managed language runtimes,

41
00:03:51.952 --> 00:03:58.310
including runtime security updates. The store is responsible for the security of its function

42
00:03:58.310 --> 00:04:05.078
code, the IAM permissions the function uses and the data it handles. Notice what never moves across

43
00:04:05.078 --> 00:04:10.000
all three services: your data and your access settings are always yours.

44
00:04:10.400 --> 00:04:15.937
Let's test it with the store's week. A disk fails in a data center: AWS.

45
00:04:15.937 --> 00:04:21.628
The web server on EC2 needs an operating system security patch: the store.

46
00:04:21.628 --> 00:04:27.396
A security group lets anyone on the internet reach the database: the store,

47
00:04:27.396 --> 00:04:34.394
because security group rules are customer configuration. RDS needs a database engine patch:

48
00:04:34.394 --> 00:04:41.392
AWS. A former employee still has an IAM user: the store. A flaw is found in the hypervisor:

49
00:04:41.392 --> 00:04:42.192
AWS.

50
00:04:42.100 --> 00:04:46.646
Here's how the exam asks about this. Physical security of data centers:

51
00:04:46.646 --> 00:04:52.474
AWS. Patching the guest operating system on EC2: the customer. Configuring security groups:

52
00:04:52.474 --> 00:04:58.301
the customer. Patching the database engine on RDS: AWS. Managing IAM users and permissions,

53
00:04:58.301 --> 00:05:04.832
and encrypting and classifying data: always the customer. Patch management and awareness and training:

54
00:05:04.832 --> 00:05:10.339
shared controls. And watch for questions about how responsibilities shift between EC2,

55
00:05:10.339 --> 00:05:11.300
RDS and Lambda.

56
00:05:11.700 --> 00:05:16.675
To recap: AWS is responsible for security of the cloud, the facilities,

57
00:05:16.675 --> 00:05:23.190
hardware, networking and virtualization behind every service. You're responsible for security

58
00:05:23.190 --> 00:05:29.987
in the cloud: your data, encryption choices, identities and access, and the settings you control.

59
00:05:29.987 --> 00:05:35.382
The more a service is managed, from EC2 to RDS to Lambda, the less you patch,

60
00:05:35.382 --> 00:05:42.318
but your data and access are always yours. Next, we'll lock down access itself with IAM essentials:

61
00:05:42.318 --> 00:05:44.700
the root user, users and policies.
