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

Exchange 2019 and WAF configuration - how to get ActiveSync working ?

Dear Sophos support team,

there have been several requests about this topic, but digging through them didn't provide a proper solution.
In the past Sophos provided a guideline for the UTM how to publish an Exchange server with WAF.

I did not find an equivalent for the XG.

So can you please provide a guideline how to publish Exchange over XG WAF with ActiveSync working and keeping WAF as secure as possible ?
Any help is appreciated.

Best Regards
ranX



This thread was automatically locked due to age.
Parents Reply
  • I understand this, and i am coming from Germany as well, but the pure number of customers using Exchange online in Germany (even in the public sector) is stunning to me, if your case is correct. Because there are certain lawyers out there, using such grounds to sue every company (see Uploadfilter policies and German Copyright). I dont understand, why they do not start to sue every company based on GPDR, if its easy to win? 

    I am not here to bring arguments for or against Microsoft Cloud, but i am just curious. There are to many customers, like you said, ignore GDPR. And this does not make sense to me. Especially as i know plenty of public (government) customers using O365. 

    Microsoft came recently with a 90 Day plan to cover GDPR concerns. https://docs.microsoft.com/de-de/compliance/regulatory/gdpr-action-plan

    My question would be, what is worse: Leaking all Emails cause of vulnerabilities, which are clearly in weekly cycle on Exchange on Prem, or a stable version, hosted by Microsoft? 

    __________________________________________________________________________________________________________________

Children
  • About your first request:
    The intention of GDPR is, to protect the single individual from misuse of it's personal data.
    A third person (e.g. a "lawyer") is not able to charge you money, when you or your company violates GDPR.
    So they cannot earn any money on this, like it was the case with copyright infringment.

    The only party getting money, are the authorities supervising GDPR.
    Just like the street authorities, charging you for speeding or parking tickets.
    So it's the same principle: many go too fast or park at the wrong place - but as controlling personnel is limited by far not all of them are caught.
    But still the most of us agree, it's a reasonable behaviour, to keep an eye on the pace most of the time.

    GDPR is realtively new; so there is little common experience and lots of confusion.
    And for a long time there had been no court decisions.
    In this vacuum many customers started with O365.

    But there were also many, that were aware, they couldn't make legal use of O365, the way, it is designed now.
    Those asked MS to provide a GDPR compliant solution.
    Therefore MS published this "pseudo" guideline.
    "Pseudo" because ist doesn't name a solution to the most crucial point:
    all data is processed on MS systems, which can be accessed by US government authorities.
    As long as these have access, O365 will not be GDPR compliant.

    From admin sight there's no good solution:
    - Exchange on prem is unsafe, due to missing updates
    - Exchange online is also no good advice because of missing GDPR compliance

    Possible workarounds:
    - to stop publishing the on prem Webservices use VPN as entrypoint
    - switch to other mailservice+groupware, which has less known vulnerabilities


  • I cannot comment on such topics, as i am not a IT lawyer nor have the experiences. I just acknowledge the big movement to O365 and still consider this to be a valid path, even for GDPR concerns. But this is something, which needs to be discussed in different forms on different levels. 

    __________________________________________________________________________________________________________________