Loading controls...
Benchmark: 164.308(a)(6)(ii) Response and Reporting
Description
Identify and respond to suspected or known security incidents; mitigate, to the extent practicable, harmful effects of security incidents that are known to the covered entity; and document security incidents and their outcomes.
Usage
Browse dashboards and select 164.308(a)(6)(ii) Response and Reporting:
steampipe dashboardOr run the benchmarks in your terminal:
steampipe check aws_compliance.benchmark.hipaa_security_rule_2003_164_308_a_6_iiSnapshot and share results via Steampipe Cloud:
steampipe loginsteampipe check --share aws_compliance.benchmark.hipaa_security_rule_2003_164_308_a_6_iiControls
- 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
- At least one enabled trail should be present in a region
- CloudTrail trails should be integrated with CloudWatch logs
- CloudTrail trail log file validation should be enabled
- ELB application and classic load balancer logging should be enabled
- GuardDuty should be enabled
- GuardDuty findings should be archived
- Ensure a log metric filter and alarm exist for AWS Management Console authentication failures
- Ensure a log metric filter and alarm exist for usage of 'root' account
- S3 bucket logging should be enabled
- AWS Security Hub should be enabled for an AWS Account
- VPC flow logs should be enabled