Why do you not want to aggregate the information?
If GD was to raise separate findings customers would quickly be overwhelmed with findings and would find it hard to address the issue. By having a single finding and then updating it continuously, it is easier for you to then see which findings to fix (you can see which findings have been open for the longest time for example), then when you fix the issue you can close that single finding down.
It is not currently possible to have new findings raised for the same security issue on the same instance - that is by design.
- Perché Amazon GuardDuty ha rilevato un tipo di risultato Denial of Service (DoS) nell’istanza Amazon EC2?AWS UFFICIALEAggiornata un anno fa
- Come posso risolvere i problemi relativi alle notifiche Amazon SNS personalizzate di GuardDuty che non vengono recapitate?AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- Ho ricevuto avvisi di forza bruta UnauthorizedAccess da GuardDuty per l’istanza Amazon EC2. Cosa devo fare?AWS UFFICIALEAggiornata 2 anni fa