Benchmark: 164.308(a)(4)(ii)(B) Access authorization
Description
Implement policies and procedures for granting access to electronic protected health information, for example, through access to a workstation, transaction, program, process, or other mechanism.
Usage
Install the mod:
mkdir dashboardscd dashboardspowerpipe mod initpowerpipe mod install github.com/turbot/steampipe-mod-aws-compliance
Start the Powerpipe server:
steampipe service startpowerpipe server
Open http://localhost:9033 in your browser and select 164.308(a)(4)(ii)(B) Access authorization.
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.hipaa_final_omnibus_security_rule_2013_164_308_a_4_ii_b
Snapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.hipaa_final_omnibus_security_rule_2013_164_308_a_4_ii_b --share
Controls
- EC2 instances should have IAM profile attached
- EMR cluster Kerberos should be enabled
- IAM password policies for users should have strong configurations
- Ensure IAM policy should not grant full access to service
- IAM groups should have at least one user
- IAM groups, users, and roles should not have any inline policies
- IAM policy should not have statements with admin access
- IAM user access keys should be rotated at least every 90 days
- IAM users should be in at least one group
- IAM user MFA should be enabled
- IAM user should not have any inline or attached policies
- IAM user credentials that have not been used in 90 days should be disabled
- S3 bucket policy should prohibit public access
- Secrets Manager secrets should have automatic rotation enabled
- Secrets Manager secrets should be rotated within specific number of days
- Secrets Manager secrets should be rotated as per the rotation schedule
- Secrets Manager secrets that have not been used in 90 days should be removed
- SSM documents should not be public
- VPC security groups should restrict ingress access on ports 20, 21, 22, 3306, 3389, 4333 from 0.0.0.0/0
- VPC security groups should restrict ingress SSH access from 0.0.0.0/0