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.

Sign up for GitHub

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

Jump to bottom

HIPAA Security - Implement dynamodb-table-encrypted-kms config rule #180

Closed
dontirun opened this issue Aug 10, 2021 · 0 comments · Fixed by #288
Closed

HIPAA Security - Implement dynamodb-table-encrypted-kms config rule #180

dontirun opened this issue Aug 10, 2021 · 0 comments · Fixed by #288
Milestone
HIPAA Security

Comments

@dontirun
Copy link
Collaborator

Summary

As a developer

I would like to implement the dynamodb-table-encrypted-kms config rule

So that I can check if qualified resources in my CDK app conforms to the following HIPAA Security control(s): 164.312(a)(2)(iv), 164.312(e)(2)(ii)

Details

ruleId: HIPAA.Security-DynamoDBTableEncryptedKMS

info: The DynamoDB table is not encrypted with KMS - (Control IDs: 164.312(a)(2)(iv), 164.312(e)(2)(ii))

Given Reason: Ensure that encryption is enabled for your Amazon DynamoDB tables. Because sensitive data can exist at rest in these tables, enable encryption at rest to help protect that data. By default, DynamoDB tables are encrypted with an AWS owned customer master key (CMK).

Acceptance Criteria

If the rule can be implemented

Given a CDK app with a non-compliant resource

  • When HIPAA Security Pack is enabled
  • Then the CDK stack does not deploy and the user receives an ERROR with relevant Control ID information about the non compliant resource

Given a CDK app with a compliant resource

  • When HIPAA Security Pack is enabled
  • Then the CDK stack deploys and the user does not receive an ERROR about the compliant resource

Given the cdk-nag RULES file

  • When the HIPAA.Security-DynamoDBTableEncryptedKMS rule is added to the rule pack
  • Then the HIPAA Security Errors section is updated with the rule information

If the rule cannot be implemented

Given the cdk-nag RULES file

  • When the dynamodb-table-encrypted-kms check is not added to the rule pack
  • Then the HIPAA Security Excluded Rules section is updated with the check information
@dontirun dontirun added this to the HIPAA Security milestone Aug 10, 2021
@dontirun dontirun mentioned this issue Aug 13, 2021
Merged
@mergify mergify bot closed this as completed in #288 Aug 19, 2021
mergify bot pushed a commit that referenced this issue Aug 19, 2021
@dontirun
feat(HIPAA Security): initializing rules pack with initial list of ex…
b2fa889 
…cluded rules (#288)

Resolves #157
Resolves #167
Resolves #170
Resolves #177
Resolves #178
Resolves #180
Resolves #181
Resolves #182
Resolves #183
Resolves #184
Resolves #186
Resolves #188
Resolves #240
Resolves #241
Resolves #245
Resolves #260
Resolves #261
Resolves #262
Resolves #192
Resolves #194
Resolves #197
Resolves #199
Resolves #204
Resolves #206
Resolves #207
Resolves #211
Resolves #218
Resolves #222
Resolves #265
Resolves #266
Resolves #267
Resolves #268
Resolves #271
Resolves #276
Resolves #224
Resolves #225
Resolves #226
Resolves #227
Resolves #229
Resolves #231
Resolves #233
Resolves #234
Resolves #236
Resolves #237       

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
HIPAA Security
Development

Successfully merging a pull request may close this issue.

feat(HIPAA Security): initializing rules pack with initial list of excluded rules cdklabs/cdk-nag
1 participant
@dontirun