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.

Sign up for GitHub

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

Jump to bottom

Option to have the GuardDuty control respect the regions in aws.spc #744

Open
georg-ikegps opened this issue Nov 29, 2023 · 3 comments
Open

Option to have the GuardDuty control respect the regions in aws.spc #744

georg-ikegps opened this issue Nov 29, 2023 · 3 comments
Assignees
@khushboo9024
Labels
enhancement New feature or request stale No recent activity has been detected on this issue/PR and it will be closed

Comments

@georg-ikegps
Copy link

Is your feature request related to a problem? Please describe.
In our case, we use AWS Control Tower to manage the regions available in our accounts.
The GuardDuty control audits all regions, as per the general AWS recommendation.

We discussed this with the Steampipe team in Slack.
https://turbot-community.slack.com/archives/C01UECB59A7/p1701230305915659

Describe the solution you'd like
It would be great if the GuardDuty control (and other controls that have this behavior) had an option only to audit the regions specified in aws.spc.

Describe alternatives you've considered
I don't know what options I should think.

Additional context
Please feel free to add any other context or screenshots about the feature request here.
Screenshot 2023-11-29 at 4 23 41 PM
Screenshot 2023-11-29 at 5 02 00 PM
@georg-ikegps georg-ikegps added the enhancement New feature or request label Nov 29, 2023
@khushboo9024 khushboo9024 transferred this issue from turbot/steampipe-mod-aws-insights Jan 9, 2024
@bigdatasourav bigdatasourav linked a pull request Jan 11, 2024 that will close this issue
Option to have the GuardDuty control respect the regions in aws.spc closes#744 #745
Closed
1 task
@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 9, 2024

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale No recent activity has been detected on this issue/PR and it will be closed label Mar 9, 2024
@misraved misraved removed the stale No recent activity has been detected on this issue/PR and it will be closed label Mar 29, 2024
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale No recent activity has been detected on this issue/PR and it will be closed label May 28, 2024
@misraved misraved removed the stale No recent activity has been detected on this issue/PR and it will be closed label May 29, 2024
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale No recent activity has been detected on this issue/PR and it will be closed label Jul 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@khushboo9024 khushboo9024

Labels
enhancement New feature or request stale No recent activity has been detected on this issue/PR and it will be closed
Projects
None yet
Milestone
No milestone
3 participants
@khushboo9024 @misraved @georg-ikegps