Jump to content

Why do File/Folder exclusions suddenly REQUIRE version 7 endpoints?


hsmithjtek
 Share

Recommended Posts

I went to create a policy for a new client to exclude some folders from scanning and now the policy requires Endpoints to be on v7? Why? What's going to happen to the current polices that exclude paths from scanning? Will they no longer work without v7? 

We need to exclude certain paths because ESET breaks business applications.

whyv7.jpg

Link to comment
Share on other sites

1 minute ago, Marcos said:

I have tested it with ERA v6.5 and Endpoint v6.6 and it worked. Only exclusions by hash require Endpoint v7.

Well, they really ought to update that to only show when you select Exclude Hash for the Type. It gives the v7 warning for each type of exclusion. Seems like a bug?

 

Thanks for the info.

Link to comment
Share on other sites

  • Administrators
2 hours ago, hsmithjtek said:

Well, they really ought to update that to only show when you select Exclude Hash for the Type. It gives the v7 warning for each type of exclusion. Seems like a bug?

I'm not sure if it's technically possible. It could be that we'll end up with two exclusion settings; one for v6.6 and and older and the other one for v7 and newer. We'll see.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...