Jump to content

ESET PROTECT - Whitelisting and disabling public access to the Web Console ?

Recommended Posts

We have ESET Protect v10 self-hosted in our Azure environment.

We're working on reducing attack surface by implementing stronger security around our tools like RMM, MDM, Management Portals.

Moving from AV to EDR and from VPN to SDP/ZTNA

1- Can we have whitelisting on the Web Console ?

2- Can we disable public access to the web console without blocking other critical ESET services

3- Does ESET Protect support SSO with Azure AD ?

4- Can we use a third-party MFA app (Google Auth, Authy, etc..) for the TOTP or we limited to using the ESET Authenticator mobile app ?


Link to comment
Share on other sites

Since 443 is being used as failover for the ESET Push Notification Service as mentioned here https://help.eset.com/protect_install/10.0/en-US/upgrade_procedures.html?ports_used.html
I changed the port being used by Apache Tomcat https://support.eset.com/en/kb7772-change-the-port-used-by-the-eset-protect-web-console to a different port and targeted that specific port with Azure NSG inbound policies to only allow certain IP addresses.
I left 443 open in the NSG Inbound policies to allow other ESET Services communicate via 443.
Can you please advise if 443 is indeed needed per the docs or should it be blocked if we are not serving the Tomcat web console ?
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...