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

Domain controller in DMZ, firewall rules needed

Hello, I'm migrating a mikrotik router to an XG, the domain controller was in another subnet. In the new schema, I placed them in the DMZ zone, but i do not know which firewall rules are needed to allow only the needed traffic for the domain to work witouth issue. 

The mk had this rules, which i dont look like the bare minium or even be the right ones

add chain=forward dst-port=7,9,13,17,19,53,88,123,137,138,161,162,389,464,4500 in-interface=ether3 out-interface=brServers protocol=udp
add chain=forward dst-port=7,9,13,17,19,53,80,81,88,135,138,139,389,443,445 in-interface=ether3 out-interface=brServers protocol=tcp
add chain=forward dst-port=464,515,2869,3268,3269,5000-5200,5722,9099,42424,53211 in-interface=ether3 out-interface=brServers protocol=tcp

 



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

    is your DC accessed from external to your company? Really depends on what your DC is used for?

    If internal use only then a Source LAN -> Any DST DMZ -> Any -> All and maybe log traffic?

    Ian

  • Hello, thanks,

    The server's IIS is exposed to the outside. As per the services in them, its domain controller, iis service an file server.

    I was looking to filtering communication between lan and dms to the bare minimum, this is how it is now in the mikrotik, we want to enhance the protection with the UTM, forwarding all traffic is not something i would feel confortable doing.

  • Hi,

    instead of the allow all entry you can select from the drop down list those ports you wish to allow or even create your own port group.

    Ian

Reply Children