Can Veeam ONE Help Distinguish New Malware Detection Events from Previously Investigated Ones?

[rin]

Hello Team,

I would like to better understand how Veeam ONE handles Malware Detection events generated by Veeam Backup & Replication.

My goal is not to suppress Malware Detection itself. Instead, I would like to understand whether Veeam ONE provides a way to help operators focus on newly generated malware-related alarms while avoiding confusion caused by previously investigated events.

Could you please clarify the following?

1. Are Malware Detection Events generated by Veeam Backup & Replication exposed as alarms/events in Veeam ONE?

2. If so, can these alarms be acknowledged in Veeam ONE?

3. After a Malware Detection alarm has been acknowledged, can operators filter or separate acknowledged alarms from newly generated alarms?

4. If the same Malware Detection condition is detected again, will Veeam ONE treat it as:
- a repeat occurrence of an existing alarm/event, or
- a newly generated alarm/event?

5. Is there a recommended way in Veeam ONE to help operators focus on newly generated malware-related alarms while keeping previously investigated alarms from cluttering the operational view?

My goal is to understand whether Veeam ONE provides any functionality that can help operators distinguish newly generated malware-related alarms from previously investigated ones.

This may include alarm acknowledgement, filtering, event correlation, alarm lifecycle management, or any other recommended operational approach.

Thanks in advance.

Best Regards,
Rintaro