Port requirements for Privilege Cloud ISPSS

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

Port requirements for Privilege Cloud ISPSS

L4 Transporter

Use-Case: ISPSS Customer. EntraID auth, PSM, CPM, SIA, Remote Access

From Connector machines, below 3 ports are failing. is it expected ?

  1. unable to telnet XXXXXXX.id.cyberark.cloud over 443.
  2. 2 out of the 4 pod addresses are reachable over telnet over 443 ?

 

1 accepted solution

Accepted Solutions

L7 Applicator

Hi @Amit Maharana​ 

 

A reason being the specific IP addresses of these ISPSS can change dynamically for various reasons, including load balancing, automatic scaling, and maintenance.

 

They are not static IP addresses.

 

Please talk to your network team and they should allow outbound access to the FQDNs with wildcards

*.cyberark.cloud instead of specific IP addresses to accommodate the dynamic nature of the service.

 

Privilege Cloud Connector

  • Destination: Privilege Cloud Vault
  • Protocol: TCP
  • Port: 1858
  • Direction: Outbound
  • Purpose: Connects to the backend vault in the Privilege Cloud environment for secrets management. FQDN is
  • https://vault-<subdomain>.privilegecloud.cyberark.cloud

 

Privilege Cloud Connector

  • Destination: CyberArk Cloud Services
  • Protocol: TCP
  • Port: 443 (HTTPS)
  • Direction: Outbound
  • Purpose: General communication with the Privilege Cloud backend. FQDNs include
  • *.privilegecloud.cyberark.cloud

 

SIA Connector

  • Destination: CyberArk Cloud Service
  • Protocol: TCP
  • Port: 443 (HTTPS)
  • Direction: Outbound
  • Purpose: Main communication with the SIA backend for REST API calls. FQDN is
  • *.cyberark.cloud

 

 

https://docs.cyberark.com/privilege-cloud-standard/latest/en/content/pas%20sysreq/standard%20ports%20-%20cpm.htm

 

https://docs.cyberark.com/privilege-cloud-standard/latest/en/content/privilege%20cloud/privcloud-sys-req-networks.htm

 

https://docs.cyberark.com/ispss-deployment/latest/en/content/introduction/dpa_network-requirements.htm#Configur

 

 

 

Hope it helps !

 

 

View solution in original post

2 REPLIES 2

L7 Applicator

Hi @Amit Maharana​ 

 

A reason being the specific IP addresses of these ISPSS can change dynamically for various reasons, including load balancing, automatic scaling, and maintenance.

 

They are not static IP addresses.

 

Please talk to your network team and they should allow outbound access to the FQDNs with wildcards

*.cyberark.cloud instead of specific IP addresses to accommodate the dynamic nature of the service.

 

Privilege Cloud Connector

  • Destination: Privilege Cloud Vault
  • Protocol: TCP
  • Port: 1858
  • Direction: Outbound
  • Purpose: Connects to the backend vault in the Privilege Cloud environment for secrets management. FQDN is
  • https://vault-<subdomain>.privilegecloud.cyberark.cloud

 

Privilege Cloud Connector

  • Destination: CyberArk Cloud Services
  • Protocol: TCP
  • Port: 443 (HTTPS)
  • Direction: Outbound
  • Purpose: General communication with the Privilege Cloud backend. FQDNs include
  • *.privilegecloud.cyberark.cloud

 

SIA Connector

  • Destination: CyberArk Cloud Service
  • Protocol: TCP
  • Port: 443 (HTTPS)
  • Direction: Outbound
  • Purpose: Main communication with the SIA backend for REST API calls. FQDN is
  • *.cyberark.cloud

 

 

https://docs.cyberark.com/privilege-cloud-standard/latest/en/content/pas%20sysreq/standard%20ports%20-%20cpm.htm

 

https://docs.cyberark.com/privilege-cloud-standard/latest/en/content/privilege%20cloud/privcloud-sys-req-networks.htm

 

https://docs.cyberark.com/ispss-deployment/latest/en/content/introduction/dpa_network-requirements.htm#Configur

 

 

 

Hope it helps !

 

 

L4 Transporter

I learnt that CyberArk has changed this address from XXXXXXX.id.cyberark.cloud to XXXXXXX.cyberark.cloud.

But the script still has this address.

 

Also, podXXXX.b1.id.cyberark.cloud & podXXXX.b2.id.cyberark.cloud are DR side conatiners which are expected to be inactive when Services are running from Primary site and are to be reachable when services are running on DR site.

  • 1 accepted solution
  • 307 Views
  • 2 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!