3 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
If using the CLI is acceptable to your use case, this documentation shows how to filter based on ResourceTags:
https://docs.aws.amazon.com/cli/latest/reference/securityhub/get-findings.html.
beantwortet vor 8 Monaten
0
I did see a feature request for using resource tags within AWS Security Hub has been filed, but there isn't a timeline for release yet. You can monitor the AWS What's New Blog for the latest news though.
beantwortet vor 7 Monaten
0
I encountered a similar problem with our Security Hub automation rules. Regrettably, I discovered that Security Hub doesn't offer support for tag-based automation during my interaction with AWS support
beantwortet vor 7 Monaten
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 2 Jahren- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
Doesn't work, I tested filtering by tag (with CLI), but he retrieves only GuardDuty finding resources, the Security Hub findings, doesn't have tags.
I opened a case and AWS confirmed that :-(
I think that I want it's a little bit simple, to build a automation way to hide or suppress some resources or controls that I don't want to see (preferably using tags based).