Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 1 subscriber
  • Views 3282 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Application control Arghhhhhhhh!!!!!!!!!

MawfTech

Why is it that Sophos relase application control detection BEFORE they release the SEC console lists so that we, the administrators of sites, cannot release blocked programs without releasing 'all added by sophos ....'.  For example, GoogleEarth just got changed and the release in SEC doesn't apply to the version now being checked. PowerDVD doesn't exist in Media Players section but is now blocked. Infuriating and causing me to spend unnecessary time on support calls from people all round our global operations.

 

There clearly should be a QA procedure in place to prevent this kind of activity. Come on Sophos!

 

Matt

 

:12675


This thread was automatically locked due to age.
Parents
  • 0

    Hi Christian,

    The issue here is that there's clearly one team writing the application prevention system and another writing the SEC console updates. If the two teams are not collaborating on updates then these release issues will occur and it's down to QA @ Sophos to sort them out properly such that these occur in the right sequence. We're not talking about malware, we're talking about applications that potentially could be vital to a company e.g. Powerdvd is used to show a company media presentation we have.

    I can see the same issue with out dated entries in my SEC too which came over from a 3.1. To be honest, I don't really see a problem with this as long as the entries still work. In the case of GoogleEarth, clearly it doesn't and my released available application is not the same as the application detection. So it looks like my policy says allow access but SAV prevents it.

    Matt

    :12683
Reply
  • 0

    Hi Christian,

    The issue here is that there's clearly one team writing the application prevention system and another writing the SEC console updates. If the two teams are not collaborating on updates then these release issues will occur and it's down to QA @ Sophos to sort them out properly such that these occur in the right sequence. We're not talking about malware, we're talking about applications that potentially could be vital to a company e.g. Powerdvd is used to show a company media presentation we have.

    I can see the same issue with out dated entries in my SEC too which came over from a 3.1. To be honest, I don't really see a problem with this as long as the entries still work. In the case of GoogleEarth, clearly it doesn't and my released available application is not the same as the application detection. So it looks like my policy says allow access but SAV prevents it.

    Matt

    :12683
Children
No Data