Benchmark: ACSC-EE-ML2-5.5: Restrict administrative privileges ML2
Description
Privileged users use separate privileged and unprivileged operating environments.
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 ACSC-EE-ML2-5.5: Restrict administrative privileges ML2.
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.acsc_essential_eight_ml_2_5_5Snapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.acsc_essential_eight_ml_2_5_5 --shareControls
- CodeBuild project environments should not have privileged mode enabled
- CodeBuild GitHub or Bitbucket source repository URLs should use OAuth
- EC2 instances should have IAM profile attached
- ECS containers should run as non-privileged
- ECS task definitions should not use root user.
- EventBridge custom event buses should have a resource-based policy attached
- Ensure managed IAM policies should not allow blocked actions on KMS keys
- Ensure inline policies attached to IAM users, roles, and groups should not allow blocked actions on KMS keys
- IAM policy should not have statements with admin access
- IAM root user should not have access keys
- SageMaker notebook instances root access should be disabled
- SSM managed instance associations should be compliant
- VPC security groups should restrict ingress SSH access from 0.0.0.0/0