Skip to content
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

cis_v140_3_5 #279

Closed
ecktom opened this issue Sep 15, 2021 · 2 comments
Closed

cis_v140_3_5 #279

ecktom opened this issue Sep 15, 2021 · 2 comments
Assignees
Labels
blocked Work on this issue is currently blocked bug Something isn't working

Comments

@ecktom
Copy link
Contributor

ecktom commented Sep 15, 2021

Again the CIS benchmark is not explicit enough. At says that AWS Config needs to be enabled in every region and:

Evaluate the output to ensure that there's at least one recorder for which recordingGroup object includes "allSupported": true AND "includeGlobalResourceTypes": true

The AWS docs says:

allSupported=true – AWS Config records configuration changes for every supported type of regional resource. When AWS Config adds support for a new type of regional resource, it automatically starts recording resources of that type.

includeGlobalResourceTypes=true – AWS Config includes supported types of global resources with the resources that it records. When AWS Config adds support for a new type of global resource, it automatically starts recording resources of that type.

While I understand that we need includeGlobalResourceTypes just once, from a security point of view I think allSupported should be included in every region.
cis_v140_3_5 does currently fail for us as looking for allSupported=true + includeGlobalResourceTypes=true in the main region and allSupported=true +includeGlobalResourceTypes=false in every other region which does not match the at least one term from the benchmark

@ecktom ecktom added the bug Something isn't working label Sep 15, 2021
@rajlearner17 rajlearner17 self-assigned this Sep 15, 2021
@rajlearner17
Copy link
Contributor

rajlearner17 commented Sep 15, 2021

@ecktom thanks for your continuous input, we have already this backlog to work out, we have started looking into it.

@rajlearner17 rajlearner17 added the blocked Work on this issue is currently blocked label Sep 21, 2021
@rajlearner17
Copy link
Contributor

Marking this closed reported here to track

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Work on this issue is currently blocked bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants