Skip to content
Original file line number Diff line number Diff line change
Expand Up @@ -377,6 +377,8 @@ Resources:
- 'arn:aws:securityhub:::ruleset/cis-aws-foundations-benchmark/v/1.2.0/rule/4.1'
- 'arn:aws:securityhub:::ruleset/cis-aws-foundations-benchmark/v/1.2.0/rule/4.2'
- 'cis-aws-foundations-benchmark/v/1.4.0/3.5' # (IT-3619) "3.5 Ensure AWS Config is enabled in all regions"
# suppress cis-aws-foundations-benchmark/v/1.4.0/3.9 since we use GuardDuty to monitor flow logs:
- 'cis-aws-foundations-benchmark/v/1.4.0/3.9'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My understanding is that guard duty is good for detection but not for investigation so I think we should enforce this finding at least for production accounts, but I'm ok with suppressing it in non-prod accounts

Copy link
Contributor

@zaro0508 zaro0508 Jan 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it would probably be beneficial if you could add a reference to issue IT-4081 and provide justification for this suppression in the issue.

Workflow:
Status:
- NEW
Expand Down
Loading