Virtual Secure Web Gateway

 View Only
Expand all | Collapse all

SWG 5.1 Deployment Digram

Migration User

Migration UserFeb 14, 2014 01:57 AM

Migration User

Migration UserFeb 14, 2014 04:35 AM

Migration User

Migration UserFeb 14, 2014 05:18 AM

SMLatCST

SMLatCSTFeb 14, 2014 05:41 AM

  • 1.  SWG 5.1 Deployment Digram

    Posted Feb 14, 2014 01:17 AM
      |   view attached

    Hello all,

     

    I need your suggestions and advice for the Deployment design of SMG . Design Digram is attached please provide me with the suggestions that can SWG be deployed in the following envoirment or not. It is kinda urgent , waiting for your kind replies

     

    regards,



  • 2.  RE: SWG 5.1 Deployment Digram

    Posted Feb 14, 2014 01:57 AM

    Any 1 ? Symantec people ?



  • 3.  RE: SWG 5.1 Deployment Digram

    Posted Feb 14, 2014 04:09 AM

    At a high level that looks fine. It's clearly missing lots of IP addresses and further detail, but I'll assume you have those in order.
    I still don't understand why you insist on Inline+Proxy and not just Inline Only?  IIRC, your client machine must use the TMGs as their proxy in your environment right?



  • 4.  RE: SWG 5.1 Deployment Digram

    Posted Feb 14, 2014 04:19 AM

    Well clients will be using SWG as their proxy, TMG can't be removed becuase it is doing consolidation and redundency for difrrent ISP's

     



  • 5.  RE: SWG 5.1 Deployment Digram

    Posted Feb 14, 2014 04:35 AM

    What kind of further details are missing ?



  • 6.  RE: SWG 5.1 Deployment Digram

    Posted Feb 14, 2014 04:57 AM

    So if we back up a moment, are you now saying that the TMGs are no longer used as proxies, but as the gateways instead?



  • 7.  RE: SWG 5.1 Deployment Digram

    Posted Feb 14, 2014 05:18 AM

    Yes in the future TMG wont be used as proxies.



  • 8.  RE: SWG 5.1 Deployment Digram

    Posted Feb 14, 2014 05:29 AM

    Looks fine to me.  Though I find it a bit odd both SWG's are using teh same gateway IP, when they are connected to different gateway devices



  • 9.  RE: SWG 5.1 Deployment Digram

    Posted Feb 14, 2014 05:31 AM

    Both SWG will be deoyed on the same ESXi server machine



  • 10.  RE: SWG 5.1 Deployment Digram

    Posted Feb 14, 2014 05:33 AM

    I need 6 physical NIC's on the same ESXi machine for both SWG's for their respective LAN,MAN and WAN interfaces which will be mapped to their virtual LAN Switches ?



  • 11.  RE: SWG 5.1 Deployment Digram

    Posted Feb 14, 2014 05:41 AM

    Yup, that's what Symantec recommend



  • 12.  RE: SWG 5.1 Deployment Digram

    Posted Feb 14, 2014 07:16 AM

    Is chain of proxy recommended ? as you can see in the attached document.

     



  • 13.  RE: SWG 5.1 Deployment Digram

    Posted Feb 14, 2014 07:23 AM

    As I mentioned in your other thread (below), the SWGs cannot be used as part of a proxy chain I'm afraid.

    https://www-secure.symantec.com/connect/forums/swg-51#comment-9764491



  • 14.  RE: SWG 5.1 Deployment Digram

    Posted Feb 14, 2014 07:32 AM

    thanks , now in my diagram should i replace TMG as proxy or use SWG as inline mode ?



  • 15.  RE: SWG 5.1 Deployment Digram

    Posted Feb 14, 2014 07:49 AM

    I'm afraid I have insufficient information to provide a suggestion, and is the kind of thing I'd normally cover in a workshop session.

    That said, Inline should work fine, it just won't be supported because of the use of the virtual SWG.



  • 16.  RE: SWG 5.1 Deployment Digram

    Posted Feb 16, 2014 11:36 PM

    thanks, If I am using SWG in an inline mode then how can I tell the SWG to use an external proxy TMG in this case ? Do I have to define static route in SWG to use TMG as the next hope for outbound traffic ?

    Regards,



  • 17.  RE: SWG 5.1 Deployment Digram

    Posted Feb 16, 2014 11:44 PM

    what does this  option do

    "Use proxy for Web Gateway secure communication(SSL) with Symantec Threat Center"


  • 18.  RE: SWG 5.1 Deployment Digram

    Posted Feb 17, 2014 03:41 AM

    The SWG currently can only use an external proxy for its own downloads (threat info, defs and DB updates), and not for routing users' web traffic.

    As far as Inline mode goes, the SWG doesn't do any routing of user traffic, it just repeats the traffic from one interface out the other.  Therefore, it's down to whatever route the network device (whether that's the source machine, or router) thinks the packet should take.



  • 19.  RE: SWG 5.1 Deployment Digram

    Broadcom Employee
    Posted Feb 24, 2014 02:28 PM

    What is the business reason for needing the Web Gateways to be inline? As SML stated, this is not supported in a virtual environment.

    Is there a reason that you cannot use Span/Tap mode?



  • 20.  RE: SWG 5.1 Deployment Digram

    Posted Feb 26, 2014 04:05 AM

    Span/Tap mode does not achieve the required functionality