Sentinel one EDR
Comments
-
It would be nice if Atera worked with S1 to be included in the Exclusion catalog. In the meantime, I simply added the following exclusions to resolve the issue:
NOTE: Two separate exclusions, one for each path.
Exclusion Type: Path and subfolders
OS: Windows
Path: C:\Program Files (x86)\Atera Networks\
Path: C:\Program Files\Atera Networks\
Mode: Interoperability - Extended
S1 was also flagging the installation script so I hashed the script and added a Hash Exclusion type entry with the Hash from my script.
I have not had any issues since.
NOTE: I've read in another thread related to Bitdefender that Atera support allegedly recommended adding a path exclusion for C:\Windows\Temp\AteraUpgradeAgentPackage\. S1 does not recommend this because it includes the windows temp folder. It will let you create it but a caution bubble will be visible in the value field in dashboard. I opted to not include it and have not had any issues so far.
1 -
Hi @jcleary99 - I spoke with our Security Team; there are no issues with Atera in the latest SentinelOne update.
If you are still experiencing issues, you can whitelist Atera by adding the following paths:
C:\Program Files\Atera Networks (or C:\Program Files (x86)\ATERA Networks for 32bit)
C:\Windows\Temp\AteraUpgradeAgentPackage
You may need to enable or add an exemption policy for scanning password-protected ZIP files, or allow unscannable content to pass.For more information, click here.
0
Topics
- All Topics
- 18 Getting started
- 12 Read before posting
- 6 Meet and greet
- 113 General
- 38 News and announcements
- 29 Resources
- 5 Knowledge Base
- 5 Webinars
- Shared Script Library
- Blog
- 3 Pro Tips
- 16 Got an idea?
- 66 Remote Monitoring and Management
- 54 Remote Monitoring
- 12 Patch Management
- 50 Professional Services Automation
- 30 Helpdesk
- 7 Billing
- 13 Reporting
- 15 Integrations & add-ons
- 10 Integrations
- 4 Add-ons
- 45 Scripting and automations
- 34 Scripts
- 10 Automations