Public ip address for Cyberark lab deployment

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Public ip address for Cyberark lab deployment

L3 Networker

We are setting up cyberark p cloud lab envrionment , where cyberark components are hosted on google cloud PSM, PSMP, CPM identity connector etc .

We will be installing active directory on google cloud VM . Do i need following to setup the lab successfully

1.Do i need  public DNS or domain name to connect target system through PSM session in cyberark p cloud since i have private AD and not entra ID

2.Do we need public ip address to connect Cyberark p cloud with cyberark components ? or port opening is enough ?i.e HTTPS 443

3.Is there any further pre requisities which i am missing

  1. please note secure tunnel deployment is mandate ?
1 accepted solution

Accepted Solutions

L4 Transporter

Hi @Manisha R​ 

 

From a deployment perspective, you will have a Connector Server that will have PSM, CPM, SIA, Connector Manager, and Secure Tunnel components installed. This server will communicate with your hosted CyberArk services. To enable these communications, you must list your public IP address (or addresses, if you use load balancing) as an approved IP address via the Pcloud Portal.

 

To ensure that your server can reach CyberArk as expected, I strongly recommend running the Connector Manager Pre-requisite PowerShell script. This script will verify that everything can be reached and that the server meets the requirements. Additionally, please perform the CPM test when prompted. This test must pass before you attempt the installation. For more information, please see CyberArk Privilege Cloud Tools

 

Please see below links for Firewall and Network Requirements

 

Outbound Requirements - Outbound traffic network and port requirements | CyberArk Docs

Internal Requirements to talk to targets - Connector ports and protocols | CyberArk Docs

 

With regards to your Active Directory - please the following link that discussed deploying an Identity Connector to integrate with AD - Install the Identity Connector | CyberArk Docs

 

Hope this helps

 

Thanks

 

Michael

View solution in original post

3 REPLIES 3

L4 Transporter

Public IP is only used by components to communicate to Vault and other external service hosted in AWS by CyberArk in backend. For internal communication it is only Private IPs.

 

Please refer Outbound traffic network and port requirements | CyberArk Docs for outbound communication to be opened from firewall.

 

To ensure you connector satisfies Connector server requirements. Run the Connectorcheckprerequisites script.

 

L3 Networker

1.Do i need public DNS or domain name to connect target system through PSM session in cyberark p cloud since i have private AD and not entra ID

 

You just need Public NAT IP. That's enough

2.Do we need public ip address to connect Cyberark p cloud with cyberark components ? or port opening is enough ?i.e HTTPS 443

Yes you need it

3.Is there any further pre requisities which i am missing

  1. please note secure tunnel deployment is mandate ?

It is mandate

L4 Transporter

Hi @Manisha R​ 

 

From a deployment perspective, you will have a Connector Server that will have PSM, CPM, SIA, Connector Manager, and Secure Tunnel components installed. This server will communicate with your hosted CyberArk services. To enable these communications, you must list your public IP address (or addresses, if you use load balancing) as an approved IP address via the Pcloud Portal.

 

To ensure that your server can reach CyberArk as expected, I strongly recommend running the Connector Manager Pre-requisite PowerShell script. This script will verify that everything can be reached and that the server meets the requirements. Additionally, please perform the CPM test when prompted. This test must pass before you attempt the installation. For more information, please see CyberArk Privilege Cloud Tools

 

Please see below links for Firewall and Network Requirements

 

Outbound Requirements - Outbound traffic network and port requirements | CyberArk Docs

Internal Requirements to talk to targets - Connector ports and protocols | CyberArk Docs

 

With regards to your Active Directory - please the following link that discussed deploying an Identity Connector to integrate with AD - Install the Identity Connector | CyberArk Docs

 

Hope this helps

 

Thanks

 

Michael

  • 1 accepted solution
  • 207 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!