PAM multi tenant

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

PAM multi tenant

L3 Networker

Hi,

 

i cant find any document about multi tenant. Is it possible make PAM multi tenant in on prem Cyberark PAM. If yes pls share relevant docs with me

1 accepted solution

Accepted Solutions

L4 Transporter

By "mutli-tenant" do you mean a single instance of CyberArk that has multiple different 'customers', perhaps separate business units?

 

CyberArk self-hosted does not directly support multiple tenants; there is a single user database and a single vault. However....

 

The vault user database cannot be subdivided to permit different 'customers' to manage their own users and groups. But if each 'customer' has a separate AD (or other identity source) that they are responsible for then this might could give an experience similar to having multiple identity tenants.

 

Safe permissions can be configured very granularly, and it is good practice for CyberArk vault admins to not have access to all safes. Therefore CyberArk safe permissions work well with the concept of 'multi-tenanting'

 

Each safe is allocated to a single CPM, so it would also be possible to have CPMs that are 'owned' by different 'customers'.

 

PVWA servers normally be shared, however if you wanted to restrict certain PVWA servers to certain Safes then you can adjust the permissions on the safes to only permit certain PVWA servers on each safe. This would support the use of different 'customers'. This would also apply to API calls made through these PVWAs

 

There should be no difficulty in managing separate PSM clusters for different 'customers'.

 

Notwithstanding the above, this would still be some way short of a true multi-tenanted solution; many features and functions could not realistically be sub-divided.

 

A complex configuration like this would require significant expertise to design, I would suggest working with CyberArk or a partner organisation to architect this.

View solution in original post

3 REPLIES 3

L4 Transporter

By "mutli-tenant" do you mean a single instance of CyberArk that has multiple different 'customers', perhaps separate business units?

 

CyberArk self-hosted does not directly support multiple tenants; there is a single user database and a single vault. However....

 

The vault user database cannot be subdivided to permit different 'customers' to manage their own users and groups. But if each 'customer' has a separate AD (or other identity source) that they are responsible for then this might could give an experience similar to having multiple identity tenants.

 

Safe permissions can be configured very granularly, and it is good practice for CyberArk vault admins to not have access to all safes. Therefore CyberArk safe permissions work well with the concept of 'multi-tenanting'

 

Each safe is allocated to a single CPM, so it would also be possible to have CPMs that are 'owned' by different 'customers'.

 

PVWA servers normally be shared, however if you wanted to restrict certain PVWA servers to certain Safes then you can adjust the permissions on the safes to only permit certain PVWA servers on each safe. This would support the use of different 'customers'. This would also apply to API calls made through these PVWAs

 

There should be no difficulty in managing separate PSM clusters for different 'customers'.

 

Notwithstanding the above, this would still be some way short of a true multi-tenanted solution; many features and functions could not realistically be sub-divided.

 

A complex configuration like this would require significant expertise to design, I would suggest working with CyberArk or a partner organisation to architect this.

Okay i understood. Lets guess we created other safes and defined permissions granularly. But when 'customer' want to change something in 'Connection components' or "Platform mgmt' part they also can edit and change my 'Connection components' or "Platform mgmt' settings, am i right ?

 

Also, we have PAM cloud side, name is Alero u know. We are using it for VPN-less connection. Is it possible do multi-tenant in Alero which i asked ?

 

 

However, What steps need to doing multi-tenant in cloud(for every user has separate Servers, Vaults, Interfaces)? We need migrate all local things to cloud(is it hard or soft process) ?

L4 Transporter

"But when 'customer' want to change something in 'Connection components' or "Platform mgmt' part they also can edit and change my 'Connection components' or "Platform mgmt' settings, am i right?" yes, exactly.

 

Alero - not exactly multi-tenant stuff; you can delegate to a Vendor which provides one level of abstraction.

 

Privilege Cloud is largely the same as Self-Hosted for the safes and platform policies, but it has a benefit that it relies on CyberArk Identity, which does have a concept of multi-tenancy.

 

SIA and SCA can support granular policies, but there is only one permission level for setting/modifying the policies, and no granularity of audit/recordings.

 

As you say, configuration settings will be largely shared, same with SIEM integration, component monitoring etc.

  • 1 accepted solution
  • 88 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!