In C:\Program Files\Common Files\Veeam\Backup and Replication\Mount Service\AntivirusInfos.xml the version of SentinelOne is hard coded. This is suboptimal and prevents this from working unless the info in AntivirusInfos.xml is manually kept in sync with the installed version of S1. As S1 upgrades could easily be done by a separate team (security team vs backup team etc) - this is likely to lead to VBR's ability to scan using S1 to be broken when first installed, and to break again each time S1 is upgraded on the mount server.
Hi Fabian,
Based on the limited data I can get right now - it looks like irregularly 3-4 times a year.
The location of the SentinelCtl is an ongoing pain for scripting etc too. We use a slight inelegant approach, but it works except if S1 version has been rolled back for some reason - which is rare.
For completeness of this thread. S1 have confirmed their CLI is not suitable for integration with VBR currently. They already have an open enhancement request to make it compatible.
Thanks
AlexHeylin wrote: ↑Feb 20, 2024 10:46 am
For completeness of this thread. S1 have confirmed their CLI is not suitable for integration with VBR currently. They already have an open enhancement request to make it compatible.
Thanks
Thanks, that is good info to have - Did they give any impression on priority/timeline of this enhancement request?