CCP same machine as the Privilege Cloud Connector alongside CPM/PSM

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

CCP same machine as the Privilege Cloud Connector alongside CPM/PSM

L3 Networker

We currently have a Privileged Cloud Connector server in Production and are planning to implement the Central Credential Provider (CCP). While the documentation indicates that CCP can be installed alongside CPM/PSM on the Connector server, I wanted to check whether others are following this approach or if you're deploying CCP on a separate server.

1 accepted solution

Accepted Solutions

L7 Applicator

Hi @Mark _​ 

 

I understand your point about the documentation.

 

For a smaller environments consolidating components can reduce the number of VMs/servers required and in that case having CCP installed along side CPM and PSM, can work well. However in Privilege Cloud, the Connector server is already a key component and installing CCP there can cause performance to existing infrastructure.

 

The best practice is to install CCP on a different server. There are good reasons,

 

  • Installing multiple components CPM, PSM, CCP all in one server increases the attack surface.
  • Also PSM and CPM servers have very stringent hardening requirements and having CCP on the same server can sometimes lead to conflicts.
  • Having all of these components on the same server can lead to performance bottlenecks during peak usage.
  • Having separate severs for each of these components makes it easier to scale each one independently as your environment grows.
  • If all components are on one server, a problem with one of the components could potentially impact the others.
  • Then it's much easier to isolate the problem to a specific component when they are on separate servers.

 

Hope it helps !

View solution in original post

5 REPLIES 5

L3 Networker

It depends upon the client requirement. If they are good with separate server, then its better to have a dedicated server for CCP.

L4 Transporter

Hello @Mark _​ 

 

Have you received an answer to your question? If so, we kindly encourage you to share it with us.

Your insights could be valuable to other community members in the future.

 

Thank you, Isar.

I have not received an answer. @Isar Shmueli​ 

L7 Applicator

Hi @Mark _​ 

 

I understand your point about the documentation.

 

For a smaller environments consolidating components can reduce the number of VMs/servers required and in that case having CCP installed along side CPM and PSM, can work well. However in Privilege Cloud, the Connector server is already a key component and installing CCP there can cause performance to existing infrastructure.

 

The best practice is to install CCP on a different server. There are good reasons,

 

  • Installing multiple components CPM, PSM, CCP all in one server increases the attack surface.
  • Also PSM and CPM servers have very stringent hardening requirements and having CCP on the same server can sometimes lead to conflicts.
  • Having all of these components on the same server can lead to performance bottlenecks during peak usage.
  • Having separate severs for each of these components makes it easier to scale each one independently as your environment grows.
  • If all components are on one server, a problem with one of the components could potentially impact the others.
  • Then it's much easier to isolate the problem to a specific component when they are on separate servers.

 

Hope it helps !

Thanks for the information that helps.

  • 1 accepted solution
  • 196 Views
  • 5 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!