Security and Compliance Flashcards

1
Q

What dictates who is responsible for security on different parts of AWS?

A

Shared Responsibility Model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is AWS responsible for in the Shared Responsibility Model?

A

The security of the cloud

- regions, edge locations, AZs, physical buildings, networking components, software/managed services, patching AMIs

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are you responsible for in the Shared Responsibility Model?

A

Security in the cloud

  • application data encryption
  • securing your account, VPCs, etc.
  • patching the guest OS on your EC2 instance
  • IAM
  • network traffic and firewall configuration
  • software that you build or install
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

EC2 Shared Responsibility Model

A

AWS: EC2 service, patching the host OS, security of the physical host server
You: installed applications, patching the guest OS, security controls

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Lambda Shared Responsibility Model

A

AWS: lambda service, language upgrades, underlying infrastructure and dependencies
You: security of the code, storage of sensitive data, IAM

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

How do you report abuse of AWS resources?

A

rotate your passwords when an incident occurs, then contact the AWS Trust and Safety Team

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Pillar 1 of the Well-Architected Framework

A

Operational Excellence
- The ability to support development and run workloads effectively, gain insight into their operations, and to continuously improve supporting processes and procedures to deliver business value.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Pillar 2 of the Well-Architected Framework

A

Security

- putting mechanisms in place that help protect your systems and data

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Pillar 3 of the Well-Architected Framework

A

Reliability
- to perform its intended function correctly and consistently when it’s expected to. This includes the ability to operate and test the workload through its total lifecycle.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Pillar 4 of the Well-Architected Framework

A

Performance Efficiency

  • effective use of computing resources to meet system and business requirements while removing bottlenecks
  • use serverless architures first
  • multi-AZ deployments
  • delegate tasks to a cloud vendor
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Pillar 5 of the Well-Architected Framework

A

Cost Optimization

- delivering optimum and resilient solutions at the least cost to the user

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is an example of Operational Excellence?

A

using CodeCommit to version control your code and IaC

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

what is an example of Security pillar?

A

configuring central logging using CloudTrail

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

what is an example of the Reliability pillar?

A

use multi-AZ deployments of RDS databases

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

what is an example of Performance Efficiency

A

use Lambda without administration overhead

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

what is an example of Cost Optimization pillar?

A

use S3 intelligent tiering to move data to the most cost-effective storage tier

17
Q

IAM

A

Identity and Access Management

- a free global service that helps you secure your cloud resources and define who has access to what

18
Q

Identities

A

who can access your resources

- root user, individual users, groups, roles

19
Q

Access

A

what resources someone can access

- policies, managed policies, permissions boundaries

20
Q

permissions boundaries

A

limit the scope of what a user can do

21
Q

root user permissions

A
  • manage your AWS account (close, change support plan, email address, etc.)
22
Q

applications as users

A

you can create a user with access keys to an on-prem application can access your cloud resources

23
Q

PLP

A

Principle of Least Privilege

- only giving a user the minimum amount of privileges to do their job

24
Q

access keys

A
  • needed when you use the CLI
  • generated by IAM
  • public key and private key
25
Q

IAM groups

A

a collection of IAM users that helps you apply common access controls to all group members

26
Q

EC2 groups

A

security groups that act as firewalls

27
Q

how is group access assigned?

A

using policies and roles

28
Q

roles

A

allow you to delegate access to users or services that normally don’t have access to your organization’s AWS resources. IAM users or AWS services can assume a role to obtain temporary security credentials that can be used to make AWS API calls.

29
Q

example use of roles:

A

attach a role to an EC2 instance for access to S3 so applications running on the instance can assess storage

30
Q

policies

A

a document in JSON format that defines permissions for IAM users, groups and/or roles

31
Q

Example use case for policies

A

limit access to an S3 bucket to specific users with a bucket access policy

32
Q

What are some IAM best practices?

A

1) enable MFA for privileged users
2) implement strong password policies
3) create individual users instead of using root
4) use roles for Ec2 instances for apps running on the instance

33
Q

IAM Credential Report

A

a list of all users in your account and the status of their credentials. used for auditing and compliance.

34
Q

What does the Well Architected Tool do?

A

provides recommendations for making your workloads more reliable, secure, efficient, and cost-effective.

35
Q

Component

A

the code, configuration, and AWS Resources that together deliver against a requirement. A component is often the unit of technical ownership, and is decoupled from other components.

36
Q

Workload

A

a set of components that together deliver business value. A workload is usually the level of detail that business and technology leaders communicate about.

37
Q

When making architecture trade-offs which two pillars are generally not traded-off?

A

Security and operational excellence are generally not traded-off against the other pillars.