Benchmark: Access Enforcement (AC-3)
Description
Enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.
Usage
Install the mod:
mkdir dashboardscd dashboardspowerpipe mod initpowerpipe mod install github.com/turbot/steampipe-mod-aws-complianceStart the Powerpipe server:
steampipe service startpowerpipe serverOpen http://localhost:9033 in your browser and select Access Enforcement (AC-3).
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.nist_800_53_rev_5_ac_3Snapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.nist_800_53_rev_5_ac_3 --shareBenchmarks
- AC-3(1) Restricted Access To Privileged Functions
- AC-3(2) Dual Authorization
- AC-3(3) Mandatory Access Control
- AC-3(4) Discretionary Access Control
- AC-3(7) Role-Based Access Control
- AC-3(8) Revocation Of Access Authorizations
- AC-3(10) Audited Override Of Access Control Mechanisms
- AC-3(12) Assert And Enforce Application Access
- AC-3(13) Attribute-Based Access Control
- AC-3(15) Discretionary And Mandatory Access Control
Controls
- Auto Scaling launch config public IP should be disabled
- DMS replication instances should not be publicly accessible
- EBS snapshots should not be publicly restorable
- EC2 instances should have IAM profile attached
- EC2 instances should not have a public IP address
- EC2 instances should use IMDSv2
- ECS task definition container definitions should be checked for host mode
- EMR cluster master nodes should not have public IP addresses
- ES domains should be in a VPC
- Ensure IAM policy should not grant full access to service
- IAM groups, users, and roles should not have any inline policies
- IAM policy should not have statements with admin access
- IAM users should be in at least one group
- IAM user should not have any inline or attached policies
- IAM user credentials that have not been used in 90 days should be disabled
- Lambda functions should be in a VPC
- Lambda functions should restrict public access
- RDS DB instances should prohibit public access
- RDS snapshots should prohibit public access
- Redshift clusters should prohibit public access
- S3 buckets should prohibit public read access
- S3 buckets should prohibit public write access
- S3 public access should be blocked at account level
- S3 public access should be blocked at bucket levels
- SageMaker notebook instances should not have direct internet access
- VPC subnet auto assign public IP should be disabled