3 Replies Latest reply on May 19, 2017 8:21 AM by pejacoby

    Disabling SMBv1 on NTLM AD Host

    kbjja

      Hello,

       

      We are trying to secure our environment against the SMBv1 exploits that are being flagged by nessus. (https://support.microsoft.com/en-us/help/2696547/how-to-enable-and-disable-smbv1 ,-smbv2,-and-smbv3-in-windows-vista,-win… ) (Stop using SMB1 | Server Storage at Microsoft  )

       

      https://support.microsoft.com/en-us/kb/2696547

      http://www.nessus.org/u?8dcab5e4

      http://www.nessus.org/u?36fd3072

      http://www.nessus.org/u?4c7e0cf3

       

       

      This article says that mcafee uses SMB for part of it's NTLM auth procedure.: Web Gateway domain communication for NTLM authentication

       

       

      We attempted disabling SMBv1 on one of our ADFS Hosts that MWG connects to - after reboot it was unable to communicate with it.

       

      Is there a reliance on SMBv1 that can be circumvented with a configuration change or is this a issue with the product?

        • 1. Re: Disabling SMBv1 on NTLM AD Host
          pejacoby

          See KB89350 -- MWG requires SMBv1 to be active on your ADFS or Domain Controller.

          https://kc.mcafee.com/agent/index?page=content&id=KB89350

           

          This is a ridiculous requirement, especially in light of Microsoft encouraging everyone to turn off the legacy protocol.  Hopefully the MWG team is working to support SMBv2 or later.

          • 2. Re: Disabling SMBv1 on NTLM AD Host
            jebeling

            The McAfee Web Gateway NTLM integration does currently require SMBv1 to be enabled on the domain controllers used for authentication. McAfee is actively working on an integration using SMBv2 but that will take at least several months. In the interim there are many secure authentication options for our customers that would enable them to disable rather than patch SMBv1 on many or all DCs.

             

            1. Stand up or use patched domain controllers that still run SMBv1 for MWG to use (could be firewalled instead of patched so only allows SMB connections from other DCs and MWGs).
            2. Use the NTLM agent (does not need SMB)
            3. Use Kerberos with user group lookups via LDAP (does not need SMB)
            4. Use MCP for redirection to MWG when on premise (does not need SMB)

             

            The cloud service never interacts directly with AD so it is unaffected by the disabling of SMBv1.

             

            Official McAfee KB article here https://kb.mcafee.com/agent/index?page=content&id=KB89350

            1 of 1 people found this helpful
            • 3. Re: Disabling SMBv1 on NTLM AD Host
              pejacoby

              Thanks for the response and updates. Could you add the info about Kerberos/LDAP into KB89350 as well?