Benchmark: 4 Monitoring
Overview
This section contains recommendations for configuring AWS to assist with monitoring and responding to account activities.
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 4 Monitoring.
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.cis_v140_4Snapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.cis_v140_4 --shareControls
- 4.1 Ensure a log metric filter and alarm exist for unauthorized API calls
- 4.2 Ensure a log metric filter and alarm exist for Management Console sign-in without MFA
- 4.3 Ensure a log metric filter and alarm exist for usage of 'root' account
- 4.4 Ensure a log metric filter and alarm exist for IAM policy changes
- 4.5 Ensure a log metric filter and alarm exist for CloudTrail configuration changes
- 4.6 Ensure a log metric filter and alarm exist for AWS Management Console authentication failures
- 4.7 Ensure a log metric filter and alarm exist for disabling or scheduled deletion of customer created CMKs
- 4.8 Ensure a log metric filter and alarm exist for S3 bucket policy changes
- 4.9 Ensure a log metric filter and alarm exist for AWS Config configuration changes
- 4.10 Ensure a log metric filter and alarm exist for security group changes
- 4.11 Ensure a log metric filter and alarm exist for changes to Network Access Control Lists (NACL)
- 4.12 Ensure a log metric filter and alarm exist for changes to network gateways
- 4.13 Ensure a log metric filter and alarm exist for route table changes
- 4.14 Ensure a log metric filter and alarm exist for VPC changes
- 4.15 Ensure a log metric filter and alarm exists for AWS Organizations changes