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

detect configuration of AWS-managed CMK's #5180

Open
FireballDWF opened this issue Dec 20, 2019 · 1 comment
Open

detect configuration of AWS-managed CMK's #5180

FireballDWF opened this issue Dec 20, 2019 · 1 comment

Comments

@FireballDWF
Copy link
Collaborator

Need ability to filter on resource configurations which use AWS-managed CMK's. Use case is where customers with security sensitive (such as FSIs) workloads mandate the usage of Customer-Managed CMKs, thus need to detect resources which are configured to use AWS-Managed CMKs. (detecting AES256 and non-encrypted is already covered in bucket-encryption examples).

Potential syntax:

policies:
  - name: s3-bucket-encryption-KMS-aws-managed-cmk
    resource: s3
    region: us-east-1
    filters:
      - type: bucket-encryption
        state: True
        crypto: aws:kms
        key: KMSMasterKeyID
        op: regex
        value: ^(.*:alias\/aws\/.*)$

Design and implementation should factor in the need to support the same detection on EBS volumes, RDS instances, DynamoDB Tables, EFS. And eventually Redshift and Elasticache

@cpollard0
Copy link
Contributor

cpollard0 commented Jun 30, 2020

I think you can get some of these already, i.e. below does RDS, same can be done for EBS.

Should we implement the same type: kms-alias filter on the additional resources?

---
policies:
  - name: identify-rds-using-default-kms
    resource: aws.rds
    description: |
      Identify RDS instances using default KMS key
    filters:
      - type: kms-alias
        key: AliasName
        value: ^(alias/aws/)
        op: regex

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