Symantec Privileged Access Management

 View Only
  • 1.  Access CA PAM from outside network

    Posted Jul 20, 2019 10:24 AM

    Could you please assist us with an architecture problem: Our current CA PAM setup is that it is only accessible from within our network. Now we want to make it accessible from the Internet as well (we have MFA enabled anyway) – as we have several service companies which need to access our environment. Currently they need to log in to our VPN and then to PAM. We want to get rid of VPN log on when we have MFA enabled in PAM anyway.

     

    What is the best approach to realize this? Is there something like a CA PAM gateway we could put in our DMZ? How are other customers implementing this?

     

    It would be great to receive feedback. I would have get in touch with your Broadcom architect who was helping us the last months, but apparently he is not working for your anymore.
    Thanks
    Nadja



  • 2.  RE: Access CA PAM from outside network
    Best Answer

    Broadcom Employee
    Posted Jul 22, 2019 05:20 AM
    Hi Nadja, 2 options which can remove the need for a VPN:

    1. Provide a VDI/VM in your DMZ which your contractors can log into. The PAM client can be installed on those VMs and they can work on PAM from there. 
    2. Setup routing on an external IP address to forward port 443 to PAM on your internal network. That way they can browse to PAM's web console or connect with the java client.

    443

    Client workstations

    Appliance

    Required for HTTPS access to Appliance.

    CA PAM Client

    Appliance Users without installed Java can use the client instead of a browser.

    CA PAM Access Agent

    Appliance

    Required for HTTPS access to Appliance.




  • 3.  RE: Access CA PAM from outside network

    Broadcom Employee
    Posted Jul 22, 2019 04:59 PM
    In addition to the options specified by Gregory, you could also connect one of the ports on your PAM appliance to your DMZ LAN and assign it a public IP.  (still would want a firewall in place to ensure it's not fully exposed).  You would need to change your default gateway to use that interface and add an additional route/gateway for your internal IP range so that it can communicate on both networks.