Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible Compliance Checks for policr #21

Open
JonasSaegesser opened this issue Dec 6, 2017 · 0 comments
Open

Possible Compliance Checks for policr #21

JonasSaegesser opened this issue Dec 6, 2017 · 0 comments
Assignees

Comments

@JonasSaegesser
Copy link

Just a brainstorming of possible compliance checks for AWS deployments:

- Terraform specific: Credentials not in template
	- Use EC2 Roles, env vars, credentials file etc
- General
	- Every Resource has to have Tags defined in a Tagging Concept
	- A small number of services can't be tagged (i.e. Device Farm)
	- Region Enforcment
- DHCP Option Set
	- Enforce central dns server
- S3 Buckets encrypted
	- Deny incorrect encryption headers (enforce KMS)
	- Deny incorrect object uploads (enforce encryption)
- S3 Buckets private
	- acl private
- EBS Encrypted  true + KMS Key
- Security Group Rules
	- No Allow Any Any Inbound
	- Source: 0.0.0.0/0 or ::/0
	- and
	- Protocoll: All or Portrange: All
- IAM Policies
	- No * Trust policies
- RDS
	- KMS Encrypted
- Kinesis Streams
	- KMS Encrypted
- R53
	- External Zones have to be *.foo.bar.ch
	- Internal Zones have to be *.abc.xyz.ch
- EMR
	- only allow emr deployments with encryption enabled
	- http://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-encryption-enable-security-configuration.html

I will create terraform snippets for those cases when I have the time.

@LoooooKe LoooooKe self-assigned this Dec 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants