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

HIPAA Security - Implement beanstalk-enhanced-health-reporting-enabled config rule #247

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

HIPAA Security - Implement beanstalk-enhanced-health-reporting-enabled config rule #247

dontirun opened this issue Aug 10, 2021 · 0 comments · Fixed by #353
Assignees

Comments

@dontirun
Copy link
Collaborator

Summary

As a developer

I would like to implement the beanstalk-enhanced-health-reporting-enabled config rule

So that I can check if qualified resources in my CDK app conforms to the following HIPAA Security control(s): 164.312(b)

Details

ruleId: HIPAA.Security-ElasticBeanstalkEnhancedHealthReportingEnabled

info: The Elastic Beanstalk environment does not have enhanced health reporting enabled - (Control IDs: 164.312(b))

Given Reason: AWS Elastic Beanstalk enhanced health reporting enables a more rapid response to changes in the health of the underlying infrastructure. These changes could result in a lack of availability of the application. Elastic Beanstalk enhanced health reporting provides a status descriptor to gauge the severity of the identified issues and identify possible causes to investigate.

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-ElasticBeanstalkEnhancedHealthReportingEnabled 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 beanstalk-enhanced-health-reporting-enabled 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 self-assigned this Sep 14, 2021
@mergify mergify bot closed this as completed in #353 Sep 14, 2021
mergify bot pushed a commit that referenced this issue Sep 14, 2021
Closes #247 

----

*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
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant