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

SEC 5.2.0.644 Application Control Modul - App not blocked in spite of policy settings

Hi there!

I set up an application control policy in Sophos Enterprise Console 5.2.0.644 to block some programms. Amongst office suites I wanted OpenOffice to be blocked, but it still can be started on my Win 7 Professional client. All other settings, e.g. Internet Browser (Firefox, MS IE) work fine, including user popup, info at quarantine manager, email to admin and SEC status change.

Is it possible that the identity of OpenOffice has been changed recently? In the policy settings it is named OpenOffice.org, on it's homepage the name changed to Apache Open Office, even if the application version's name is still "OpenOffice.org 3.4.1". I'm a little confused by now because I expected SEC App Control to recognize OpenOffice.

Could anybody check please if the identity has changed? If it has not, I think I mixed up some settings... maybe. Thanks a lot!

Cheers,

Ina

:38535


This thread was automatically locked due to age.
  • Hello Ina,

    can't test with AOO 3.4.1 right now - maybe someone else can. Contacting Support will likely be your best option to get a quick response. Name changed to AOO almost a year ago (with 3.4.0) and 3.4.1 is out for months as well thus I'd be somewhat surprised if it weren't covered - but it's possible (and there's not much you could have done wrong).

    Christian 

    :38541
  • Hi Christian,

    thanks for your reply.

    Oh, ok. I did not notice the change of name at all, because we do not use OO at work. I just installed it for testing the blocking of office suites. Everybody uses MS Office here, so it was almost "just for fun".

    But I think I will contact support anyway because if the identity has not been fixed yet, other companies might get some trouble with AOO because they depend on it. Fixing the identity would be very useful, I guess. Seems to be an updating issue not a problem I triggered myself.

    If I get any information by SOPHOS support, I will tell you here.

    Cheers,


    Ina

    :38547