Does SCA provision JIT users or entitlements to Azure?

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

Does SCA provision JIT users or entitlements to Azure?

L3 Networker

Does SCA provision ephemeral users with selected entitlements/roles in Azure for Web Console access? Or is it simply providing entitlements JIT to the normal user account (user logged into CyberArk)?

 

TIA

4 REPLIES 4

L4 Transporter

SCA does not create an ephemeral user, instead it adds the existing user to a new role. Which user is elevated depends on how the Web App and SSO are configured.

 

For instance, CyberArk Identity is configured to trust Azure Entra ID as the IdP then a user might login to CyberArk with their Entra ID account. With minimal configuration SCA could elevate this account dynamically into privileged roles within Azure.

 

But in a different use-case you might login to CyberArk with a CyberArk Cloud identity, and configure AWS or Azure to trust CyberArk as the IdP. You could then use outbound SSO from the AWS Portal / Azure Portal Web App to log the user in to the the target with a different username to their CyberArk username. SCA would then apply the privileged roles to whichever account is defined to Web App.

Much thanks @Jon Musker​ . I went through the docs, but the Azure CLI access workflow is where I realized that and wanted to confirm.

 

If we are using Azure as IdP with SSO set up for CyberArk portal access (aligned with above), is it possible to use a different username when the user is logs into Azure or AWS via SCA with JIT?

for example - username-admin@domain? as most companies prefer not to use the normal accounts for Privileged access.

 

Just wondering where that option might be if its possible. May be in Azure/AWS app settings> Account Mapping>Account Mapping Scripts?

 

Thanks

Hi @Jinal Jayawardhana​ 

 

The sample way is the user has 2 accounts (one for normal access, one for privileged access via SCA with JIT) in Entra ID, the one for JIT will not have standing permission unless elevated by SCA. But this method will duplicated the number of accounts to be managed.

 

If you want to enforce JIT access via CyberArk, the user need to be federated from CyberArk Identity, that mean the account should be under a dedicated domain (e.g. username@sca.domain.com).

 

It is not something that you can't do if you also want the user logging in with normal account (e.g. username@domain.com) and connected to admin account (e.g. username@sca.domain.com). That will involves additional configurations, such as, account mapping, account provisioning (if you want to auto provision users to the dedicated domain), etc.

 

Note: afaik, there is no articles mentioned about these configuration yet.

 

 

As @Argon Lau​ says, it can involve a few steps - but it all works!

  • 241 Views
  • 4 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!