Symantec Privileged Access Management

  • 1.  CA PAM Loop Back Addresses

    Posted Oct 18, 2017 04:22 PM

    I see the CA PAM accessing lot of loop back addresses.

    Eg - 127.0.0.200

     

    There are more. At our client location MacAfee blocks all local IP's other than 127.0.0.1.

     

    Is there a way to get around this. A resolution?



  • 2.  Re: CA PAM Loop Back Addresses

    Broadcom Employee
    Posted Oct 18, 2017 04:59 PM

    Hello Seema, No, there is not. This is a hardcoded local IP that is used by the built-in access methods. It is not configurable at this time. Do you know of a reason the customer has to continue blocking of this local IP?



  • 3.  Re: CA PAM Loop Back Addresses

    Posted Oct 18, 2017 05:08 PM

    The client does not approve of opening all loop back addresses. It is not safe for the environment. Is there a list of hardcoded local IP's that the access methods use? Could you please provide that?

     

    MacAfee blocks all loop back addresses for now. The client has to go through a approval process to get all the addresses unblocked. Without which they cannot use the product.



  • 4.  Re: CA PAM Loop Back Addresses
    Best Answer

    Broadcom Employee
    Posted Oct 18, 2017 05:53 PM

    Hi, there is conditional use of 127.<appliance ID>.0.X addresses where X is a number between 1 and 10, with 10 being selected first, and lower numbers next if for some reason the IP is not available. These will come into play if socket filter configurations are used in policies. <appliance ID> is an ID you define in the socket filter configuration, the default is 1.