-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IT-4081: suppress cis-aws-foundations-benchmark/v/1.4.0/3.9 since we use GuardDuty to monitor flow logs #1319
base: master
Are you sure you want to change the base?
Conversation
…use GuardDuty to monitor flow logs
@@ -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' |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
@@ -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' |
There was a problem hiding this comment.
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.
suppress cis-aws-foundations-benchmark/v/1.4.0/3.9 since we use GuardDuty to monitor flow logs