AWS Security Fundamentals Flashcards
1
Q
Components of a strong identity foundation
A
- implement principles of least privilege, start with denying access, then grant access as needed
- enforce separation of duties
2
Q
Components of traceability
A
- enable the following
- monitoring
- alerting
- audit actions and changes
- integrate logs and metrics with automated systems to respond and take action
3
Q
Defense in depth
A
- apply security at all layers, not just at the perimeter
4
Q
Automate security best practices
A
- define and implement controls as managed code, which will allow you security mechanisms to scale with your applications
5
Q
Protect data in transit and at rest
A
- classify your data into sensitivity levels and apply the appropriate encryption and access control
6
Q
Prepare for security events
A
- create incident management processes
- run incident response simulations
- use tools to automate detection, investigation and recovery
7
Q
Shared security model
A
- AWS is responsible for securing: hardware, software, networking and facilities running AWS services
- Customer is responsible for securing: your data, OSes, networks, platforms, and other resources you create in AWS
8
Q
AWS Availability Zones
A
- logical groupings of physical data centers that are interconnected with low latency, redundant circuits
9
Q
AWS Regions
A
- regions usually contain two or more availability zones, which are physically isolated from each other
10
Q
Considerations when choosing an AWS Region
A
- distance from your users
- compliance requirements for data locality
- service availability, not all AWS services are available in all regions
- cost, some regions have cost savings over others
11
Q
AWS physical data center security
A
- follows principles of least privilege, only pre-approved access is granted to employees and contractors
- only AWS employees who require routine access are granted permissions to the relevant areas. Other AWS employees must go through the visitors process and be escorted during their visit
- professional security staff use video surveillance, intrusion detection and access log monitoring
- AWS data centers are housed in nondescript, undisclosed facilities
12
Q
AWS physical data center environment considerations
A
- AWS data center locations are chosen to mitigate risks like flooding, extreme weather and seismic activity
- AWS performs regular business continuity plan simulations
13
Q
AWS physical data center infrastructure
A
- fully redundant electrical systems, UPS units provide backup power for critical loads, generators provide backup power for the entire facility
- climate control maintain a constant operating temperature
- automatic fire detection and suppression reduces the risk of fire
14
Q
AWS data layer
A
- storage devices are decommissioned by using NIST800-88 techniques to deploy customer data
- AWS is audited by external auditors who inspect the data centers
- AWS servers notify employees of any attempts to remove data and automatically disable the server
15
Q
AWS IAM
A
- Identity and access management
- every interaction you make with AWS is authenticated, IAM is the centralized mechanism for creating and managing individual users and their permissions
16
Q
Types of credentials supported by AWS
A
- username and password - password policies define the requirements for the passwords set by IAM users
- MFA - more than one authentication factor is checked before access is granted
- user access keys - used when making programmatic calls to AWS using the CLI, SDKs or HTTPS API. Each access key credential has an access key ID and a secret key. Each user can have two active access keys, which is useful when rotating keys or revoking permissions.
- EC2 key pairs - used for SSH or RDP connections to EC2 instances. You can provide your own or let AWS generate them for you
17
Q
Authentication vs Authorization
A
- Authenticate is who you are (username & password, access keys, etc)
- Authorization is what you can do (RBAC, Service Control Policy (SCP), etc)
18
Q
AWS Secrets Manager
A
- designed to centrally manage secrets used to access resources on AWS, on-premises and 3rd party services
- can be database credentials, passwords, 3rd party API keys, even arbitrary text
- allows code to make API calls to retrieve the secret
- can automatically rotate the secret on a schedule
19
Q
AWS Single Sign-On (SSO)
A
- enables users to sign in to a user portal with their existing corporate credentials and access all of their assigned accounts and applications
- includes built-in SAML integrations to many business applications
- may be integrated with Microsoft Active Directory, so users can authenticate with their AD credentials
20
Q
AWS Security Token Service (STS)
A
- a web service that enables you to request temporary, limited-privilege credentials for IAM users who are taking on a different role or for users who are being federated
21
Q
AWS Directory Service
A
- enables your domain workloads and AWS resources to use managed Active Directory in the AWS Cloud. AWS Managed Microsoft AD is built on actual Microsoft Active Directory and does not require you to synchronize or replicate data from your existing Active Directory to the cloud.
22
Q
AWS Organizations
A
- lets you centrally manage and enforce policies for multiple AWS accounts
- allows grouping accounts into organizational units and use service control policies to centrally control AWS services across multiple AWS accounts.