DennisT 0 Posted May 6, 2019 Share Posted May 6, 2019 Is there a way to mark a rogue computer as known and to ignore it going forward? With all the printers, switches, timeclocks, IP to whatever devices, etc I have over 250 rogue devices I know of and don't care about as far as AV is concerned. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,274 Posted May 6, 2019 Administrators Share Posted May 6, 2019 You can enable filters via a policy: Link to comment Share on other sites More sharing options...
DennisT 0 Posted May 6, 2019 Author Share Posted May 6, 2019 Do I have to add each device by its IP/MAC? I don't see a way to mark items in the Rogue List as ignore/add to the policy. Link to comment Share on other sites More sharing options...
DennisT 0 Posted May 6, 2019 Author Share Posted May 6, 2019 Ugh, I tried using a IPV4 whitelist filter, doesn't work properly (scans IPs outside the range I entered). Link to comment Share on other sites More sharing options...
DennisT 0 Posted May 6, 2019 Author Share Posted May 6, 2019 After a few minutes the outside range items dropped off. Appears to be working now. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 384 Posted May 6, 2019 ESET Staff Share Posted May 6, 2019 For future reference: there is a client task Rogue Detection Sensor Database Reset that is supposed to speed up cleanup of cache after changing detection filters. Just be aware that sensor does not utilize active scanning which mans it might take some time after all device are detected again. Link to comment Share on other sites More sharing options...
Recommended Posts