Security and Governance Flashcards
1
Q
Shared Responsibility Model
A
managed by AWS
Compute - ec2 instances
Storage - S3, EBS
Networking - VPC, Routing
Regions -
Availability Zones
## managed by Clients o/s config firewall applications client side encryption server side encryption authentication and access control
2
Q
IAM User
A
- never use root account to do anything, create other iam user with admin role
- delete root user keys
- assign policies to groups not users
- customize sign-in link rather than have something random
- use MFA
3
Q
IAM Role
A
- instead of using an IAM user credentials on an EC2 instance to interact with AWS use just assign an IAM Role to that EC2 instance. Then define all the required permissions in the role.
- when you create an IAM role it will create two policies
1. permissions
2. trust policy - defines which service (i.e. ec2, IAM user) can assume this role
4
Q
S3 Bucket Policy
A
## open policy { Version: "", Statement: [ { Effect: "Allow", Ection: "s3:*", Resource: "*" } ] }
## restrictive policy { version: "", Statement: [ { Effect: "Allow", Action: [ "s3:ListBucket", "s3:ListObject" ], Resource: [ "arn:aws:s3:::", "arn:aws:s3:::/*" ] } ] }
5
Q
Securing EC2 access
A
- do not allow 0.0.0.0/0 port 22 access
- put all EC2 containers in private subnet
- put bastion host in public subnet
- allow client ip access to port 22 on bastion host
- allow bastion host SG access to internal SG port 22
6
Q
AWS Cost Estimation and Compliance Tools
A
- Trusted Advisor
- Cloudcheckr
7
Q
Cross Account Access
A
enable sharing of roles between two AWS accounts
8
Q
S3 Encryption
A
need to encrypt data in transit and at rest
In transit - all endpoints have TLS enabled
At Rest
1. client side encryption
- client needs to encrypt the object before its send to S3 and then decrypt it
- server side encryption
- SSE-S3 - keys provided by S3
- SSE-KMS - keys provide by KMS
- SSE-C - client need to provide the keys
9
Q
EBS volume encryption
A
- when you create the volume you have the option to encrypt the volume
- you can also choose to encrypt the root volume - but or that you need to create an encrypted AMI and use that to create the instance
10
Q
RDS Encryption
A
- just need to select encryption option when creating the database
- aws will create a new key called aws/rds and use it to encrypt the data at rest
11
Q
Access Control
A
- Cloudtrail
- MFA
- Password policies
- IAM Roles/ Policies / Permissions
- Trusted Advisor
- Bucket Policies / ACL
12
Q
Securing IT Resources
A
- isolate servers at hardware level i.e. dedicated instances instead of hypervisor level
- security groups
- Network ACL
- VPC
- VPN
13
Q
Logging
A
- vpn flow logs
- S3 logs
- cloudtrail - primary logging tool
14
Q
Monitoring
A
Cloudwatch alarms
ec2 instance status
amazon SNS