Ability to Whitelist 3rd Party AV | Voters

Ability to Whitelist 3rd Party AV

Ryan Oakes

Some AVs do not register themselves with Windows Security and allow Defender to be run along side them. There should be an option to whitelist these so that the managed AV pages does not report endpoints with coexisting AV as an error.

August 29, 2023

Autopilot

Merged in a post:

Allowlist for "Other AV"

Jordy Minnebo

We have customer(s) that we co-managed that have Cortex or another product, it would be cool to have a clean dashboard with 0 unhealthy Defenders. But now we always have "errors" because of "Other AV". I would like to be able to override by creating a custom allowlist for AV per customer. Like

Cortex

or something.

5 hours ago

Braden Hansen

I can get behind this as I also have some customers that are required to use a specific AV product or choose to use a different product which is not Defender. it is an approved exception to our otherwise fully managed MAV customers.

Matt Yordy

I concur. This would make our daily checks on the Huntress antivirus console much easier. In our case, most of the Other AV would be ESET, but same concept.

Autopilot

Merged in a post:

Exceptions for Unhealthy Status - Other AV

Alex Mandarino

We are running SentinelOne in parallel with Windows Defender, but the endpoint status is reporting as 'unhealthy' due to this 'other av' being present.

I would love to see a feature added kind of like the unexpected login location (set to expected/not expected) feature works in ITDR - we could set S1 as 'expected' and would not flag as unhealthy.

March 3, 2025