Benchmark: 500.02(b)(3)
Description
The cybersecurity program shall be based on the Covered Entity’s Risk Assessment and designed to perform the following core cybersecurity functions: detect Cybersecurity Events.
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 500.02(b)(3).
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.nydfs_23_500_02_b_3Snapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.nydfs_23_500_02_b_3 --shareControls
- API Gateway stage logging should be enabled
- At least one multi-region AWS CloudTrail should be present in an account
- All S3 buckets should log S3 data events in CloudTrail
- CloudTrail trails should be integrated with CloudWatch logs
- CodeBuild projects should have logging enabled
- EC2 instance detailed monitoring should be enabled
- ELB application and classic load balancer logging should be enabled
- Elasticsearch domain should send logs to CloudWatch
- GuardDuty should be enabled
- OpenSearch domains should have audit logging enabled.
- OpenSearch domains logs to AWS CloudWatch Logs
- RDS DB instance and cluster enhanced monitoring should be enabled
- Database logging should be enabled
- AWS Redshift audit logging should be enabled
- Redshift cluster audit logging and encryption should be enabled
- S3 bucket logging should be enabled
- AWS Security Hub should be enabled for an AWS Account
- SSM managed instance associations should be compliant
- VPC flow logs should be enabled
- Logging should be enabled on AWS WAFv2 regional and global web access control list (ACLs)