One remote access tenant for two separated subnets with predefined connectors for each

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

One remote access tenant for two separated subnets with predefined connectors for each

L1 Bithead

Hello everyone

We have such a case

Remote access (Alero) - one connector is in one network subnet and communicates with dedicated PVWA/PSM in the same network.

The second connector in the second subnet and this one also communicates with dedicated PVWA/PSM in the "second" network.

There is no connection between subnets and there will be no connection.

 

Two separate applications (PWVA portals for each subnet)

 

Is something like this likely to work?

Because from the "Remote access" tenant console we are not able to determine which connector supports a given application and we do not know how it will behave

 

KR

Jakub

5 REPLIES 5

L1 Bithead

Yes! We have done this for many different sites(sites are the Alero term). You can also invite users/vendors to all or any combination of sites. We have also leveraged multiple sites with the same EPV infrastructure to overcome network routing outages in our network. Let me know if you need more details. Once I even set up a Site/Connector and connected to infrastructure with no EPV backend haha it was a cool test.

L1 Bithead

Hi Scot

Great, thanks for confirming. that's what I would like to know.

I was afraid of how the connectors would behave when they are in different subnets and how traffic is distributed to PVWA and HTML5gw-PSM. In our case, components from both subnets have dedicated EPV server.

so our case is:

  • one Remote Access tenant
  • 2 Cyberark full infrastructure (connectors, PVWA, PSM, Vault) in separate, unconnected subnets.

 

Yep that works, we have 4 separate EPV environments, they each have their own site configuration in Alero and each site has multiple connectors for redundancy.

L1 Bithead

Hi,

as Scot stated above, for your use cases in CyberArk Remote Access, the sites would be the solution.

 

Site is basically a segregation of environments and you can have multiple applications defined, each of them belonging to different site.

For your purpose, these applications would be to access PVWA portals in different zones.

 

And as stated above you would then be able to grant your users access to either of the sites(environments) or both if needed.

 

So the chain goes:

1, You define a site and deploy at least one connector in it, ideally at least 2 for redundancy

2, You define application, PVWA in your case, to access the site through remote access

3, you grant users access to this application

 

You can repeat the above process as many times as needed to deploy multiple sites or applications.

Once user would select certain application, CyberArk would rout him to available connector in the site, where the application is defined.

 

If user is not specifically granted access to the application, he would not even know such a site exist and CyberArk is routing the connections only through the connectors in the particular site.

if no connectors would be available in that site, it would not try ones from the other site, it would simply fail to connect.

 

Hope this helps.

 

BR, Lukas.

 

L1 Bithead

Hi,

as Scot stated above, for your use cases in CyberArk Remote Access, the sites would be the solution.

 

Site is basically a segregation of environments and you can have multiple applications defined, each of them belonging to different site.

For your purpose, these applications would be to access PVWA portals in different zones.

 

And as stated above you would then be able to grant your users access to either of the sites(environments) or both if needed.

 

So the chain goes:

1, You define a site and deploy at least one connector in it, ideally at least 2 for redundancy

2, You define application, PVWA in your case, to access the site through remote access

3, you grant users access to this application

 

You can repeat the above process as many times as needed to deploy multiple sites or applications.

Once user would select certain application, CyberArk would rout him to available connector in the site, where the application is defined.

 

If user is not specifically granted access to the application, he would not even know such a site exist and CyberArk is routing the connections only through the connectors in the particular site.

if no connectors would be available in that site, it would not try ones from the other site, it would simply fail to connect.

 

Hope this helps.

 

BR, Lukas.

 

  • 232 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!