we're publishing the owa/outlook through f5 ltm and yesterday we received and update that new kind of attack is targeting exchange servers
is there anything else we can do on f5 machine other than updating our exchange servers to prevent this kind of attack?
today we are implementing owa web access through apm and 2fa , and direct access to other URLs like:
"/microsoft-server-activesync*" "/ews*" "/enterprisevault/*" "/autodiscover*" "/mapi*" "/ecp*" "/oab*"
Has anyone went through this?
APM seems like the way to go, if you add authentication before traffic reaching the Exchange server you have a good protection.
it remains kinda unclear in which path the attacks focus, this website suggests one. but things move quickly probably.
Thank you boneyard 🙂 Great articles
We do have the APM along with 2fa on the OWA
we'll check also the ASM option
I saw also that DevCentral published ASM template to have OWA in blocking mode from day one