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

Sophos DLP rule block internal network links

Dear all,

We have following issues with a couple of users - They not able to open a link in Outlook, it doesnt matter if its link to a local or a network file.Most after hours the link opens, somtimes they not able to upload files in the webbrowser, for example when you click choose files and the explorer should open - this happens after minimum 1 hour, till then the browser is freezed.

We able to identifyed that our DLP Rule is the reason for this - if DLP is disabled links work fine - The dlp contain just 2 rules which alert when a specific number of email addresses exported to any file or device.

Anyone had something similar ?

Thanks



This thread was automatically locked due to age.
Parents
  • Hi Supporter0711,

    Thank you for reaching out. Is this only affecting Windows Endpoints? We have released the core agent 2022.1.1.3 which has a fix for the issue you reported. We recommend that you check whether these devices had already received the update.

    The release is scheduled to take place as follows:
    •16th June: All accounts on Core Agent 2022.1.0.78 and customer fix requests
    •21st June: Start date for remaining customers
    •07th July: End date

    Let us know if you require additional information. Thank you.

    Gladys Reyes
    Global Community Support Engineer
    Are you a Sophos Partner? | Product Documentation | @SophosSupport | Sign up for SMS Alerts
    If a post solves your question, please use the "Verify Answer" button.
    The New Home of Sophos Support Videos!  Visit Sophos Techvids
  • Gladys -- question -- it appears the core agent version number format you are discussing (year followed by other version numbers) is different than what supporter0711 and I see when we go to the about link in the endpoint agent itself.  Now, Intercept X uses that numbering scheme (and appears to be recently updated) but the Core Agent uses an entirely different numbering scheme.  Is there somewhere else we should be looking to see what the real version of the core agent is, or does this indicate that the rollout was not successful (none of the computers on our central account have a core agent version different than 2.20.13 -- all show successful "last update" statuses.  I'll attach a screenshot.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Sophos Platinum Partner

    --------------------------------------

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

  • Hi ,

    Based on the screenshot that you shared, your device still have not received the latest core version. In this case, we recommend that you open a support ticket so our team can further look into it. You might need to join the devices into the EAP for Endpoints, but there's also a possibility that controlled updating is enabled for your devices which could affect things.

    Kindly open a support case or call our support hotline (support.sophos.com/.../ in order for us to further investigate. Thank you.

    Gladys Reyes
    Global Community Support Engineer
    Are you a Sophos Partner? | Product Documentation | @SophosSupport | Sign up for SMS Alerts
    If a post solves your question, please use the "Verify Answer" button.
    The New Home of Sophos Support Videos!  Visit Sophos Techvids
  • Hi all,

    we are in the same situation. No controller for update is enabled in our sophos management console. Check the screen below for update status:

  • I created a ticket and talked to the support team, it seems there must be a special flag in the sophos backend to enable the update per customer. Waiting for the implementation

Reply Children
No Data