2개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
1
Any news on this or work arounds? We got exactly the same issue and we generate automated emails on critical findings of the amazon event bridge. Getting false alerts is a bit annoying.
답변함 9달 전
-1
All snapshots are evaluated by RDS.1. Findings are triggered by the evaluation of the config rule backed by RDS.1. When the snapshot is deleted Config produces a NOT_AVAILABLE finding for the deleted resource which is translated in Security Hub as Record State = ARCHIVED.
답변함 2년 전
Seems like there is some sort of bug in the config rule because we are also getting these CRITICAL SecurityHub findings saying that our automated RDS snapshots are public, which is impossible since they are encrypted (and we have never set them public to begin with).
관련 콘텐츠
- AWS 공식업데이트됨 2년 전
- AWS 공식업데이트됨 2년 전
Same here, we keep getting alerts from our CSOC about these "critical" findings...
We appear to have the same issue as well