Secure Cloud Access (SCA) FAQs

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Idira Success Blogs
20 min read
L4 Transporter

 

Table of Contents (expand each section to see relevant questions):

Before You Begin
  • Who should be involved from my organization for a successful SCA deployment?
  • What should I do before I begin?
  • Is there a way to receive updates of service interruptions or outages?
  • Are there any training resources to familiarize myself with SCA?
Getting Started
  • How do I activate my tenant?
  • I never received my tenant email.
  • My tenant activation is expired.
  • Where can I find my tenant ID?
  • What are the required permissions you need as a cloud admin?
  • Can we reduce the permissions outlined in the documentation?
Onboarding
  • I need to onboard manually. Is there documentation on this?
  • How do I create a web app from SCA?
  • How soon after onboarding workspaces to Cloud Visibility can I see them in SCA and start setting up cloud access policies?
  • Is it possible to delegate administration to control access to a specific Cloud provider (such as only AWS or GCP)?
  • Does SCA require Cloud Visibility (CV) to correctly function?
  • Do Cloud Visibility workspace limits apply to SCA?
  • How do Cloud Visibility and SCA handle secret rotation?
Policies
  • Are there any policy best practices Idira recommends?
  • What is the difference between pre-defined and on-demand SCA policies?
  • When should I use group binding vs. direct binding?
  • I’m not seeing AWS IAM roles in the SCA Policy Wizard.
  • Do I need to modify Permissions on the Web App (on Identity) for SCA?
  • How long does it take to revoke permissions from an identity after the access window closes, such as when a session with a configured length of 2 hours expires?
  • I can’t see roles in the policy. What should I do?
Discovery
  • Is there a way to manually discover and scan onboarded workspaces?
  • How do I discover new or changed roles?
Automation
  • What permissions are required to run APIs?
  • How do I avoid over-permissioning?
  • What can be automated?
Optimize (Advanced Use Cases)
  • My organization has a specific use case that may require a unique architecture configuration. Are there examples I can reference that other organizations may have requested?
General
  • How can I confirm how many SCA licenses we're using?
  • What if my organization uses a 3rd party IdP?
  • How do I comply with Microsoft's Multi-Factor Authentication (MFA) requirement on Azure?
  • Where is the authoritative source of the users? Do users need to reside in both the CSP’s, SCA, and IdP?
  • I can’t find the answer to my question.

 

Secure Cloud Access (SCA) FAQs

Before You Begin

Who should be involved from my organization for a successful SCA deployment?

  • We recommend bringing in the following teams from the start to ensure proper stakeholder participation:
    • DevSecOps
    • CloudOps
    • Site reliability engineers (SREs)
    • Cloud platform engineering
  • Review our Best Practices for Adopting and Implementing Secure Cloud Access for more information on who from your organization should be represented (it’s our very first best practice!)


What should I do before I begin?


Is there a way to receive updates of service interruptions or outages?

Subscribe to these pages to get updates in case of service interruptions or outages. Customers & partners can view SCA and Identity’s availability status, planned maintenance windows, and other service-related information via these sites.

Are there any training resources to familiarize myself with SCA?


Getting Started

How do I activate my tenant?

  • To activate your tenant for Secure Cloud Access (SCA), you will need to reference two emails from CyberArk:
    • To access the Identity Security Platform: You should have received an email from [email protected] with the subject line “Your new Idira tenant [tenant name] is ready!”. Please activate your tenant using the tenant URL included in this email.
      • Please note, the tenant URL expires after 96 hours. If the link has expired, please use the “Forgot Your Password?” link and follow the on-screen instructions to obtain access to your tenant.
    • To access your Secure Web Sessions (SWS) tenant: Your SWS tenant information is included in a separate email from [email protected] with the subject line “Idira e-Delivery [ACCOUNT NAME] , PO#”. This tenant activation URL does not expire. 


I never received my tenant email.

  • The tenant activation emails are sent to the delivery contact identified within your organization at the close of sale. Please check with your Identity admin or main admin for tenants at your organization if you did not receive these.
    • The tenant admin should have received two separate emails containing the tenant information:
      • To access the Identity Security Platform: You should have received an email from [email protected] with the subject line “Your new Idira tenant [tenant name] is ready!”. Please activate your tenant using the tenant URL included in this email.
        • Please note, the tenant URL expires after 96 hours. If the link has expired, please use the “Forgot Your Password?” link and follow the on-screen instructions to obtain access to your tenant.
      • To access your Secure Web Sessions (SWS) tenant: Your SWS tenant information is included in a separate email from [email protected] with the subject line “Idira e-Delivery [ACCOUNT NAME] , PO#”. This tenant activation URL does not expire. 
  • If you are unable to track down your tenant emails, please open a Support Ticket to reset your cloud admin password or to add a new cloud admin account to the tenant. Please choose Identity as the product.


The tenant email went to the wrong person.

  • Please open a support ticket to add a new cloud admin to the tenant. Please choose Identity as the product.


My tenant activation is expired.

  • The tenant URL included within the Identity Security Platform welcome email expires after 96 hours for security reasons. If 96 hours has passed, please use the “Forgot Your Password?” link found on the activation homepage and follow the on-screen instructions to obtain access to your tenant.
  • The Secure Web Sessions tenant URL does not expire.
  • If you are having issues accessing this tenant, please open a support ticket and choose Identity as the product


Where can I find my tenant ID?

  • Your tenant ID can be found within the platform. Go to the upper right-hand side under your name and select Tenant Details. Here you can find your ID, region, and additional Identity information.
ka3Vy00000ChcEPIAZ__eid=ka3Vy00000ChcEP&feoid=00N2J00000APFDu&refid=0EMHt0000077axe.png
ka3Vy00000ChcEPIAZ__eid=ka3Vy00000ChcEP&feoid=00N2J00000APFDu&refid=0EMHt0000077axf.png


What are the required permissions you need as a cloud admin?

  • Required permissions as an admin for each CSP:
    • If onboarding an AWS workspace to SCA:
    • If onboarding an Azure workspace to SCA:
    • If onboarding a Google Cloud workspace to SCA:
      • Ensure you have the required permissions on your Google Cloud organization.
      • A key callout: Ensure the Google Cloud admin user has been assigned the following permissions:
        • roles/resourcemanager.organizationAdmin
        • roles/owner
           
  • Required permissions as an admin for CyberArk:
RoleDescription
CS AdminStatic role. Users have full access permissions for the SCA service to manage all functionality, policies, access request settings, and integrations.

 

RoleDescription
CEMAdminStatic role. Users can onboard and manage cloud environments, configure integrations, and delegate cloud workspaces.
    • SWS:
      • To activate SWS, you must be listed as the tenant administrator of your Idira tenant and have received the activation email with a link to activate SWS. The tenant administrator is usually the person who received the initial access to the Idira Identity tenant or who was identified during the purchasing of the Idira solution. If you cannot identify who is the tenant administrator or cannot find the activation email, you can submit a ticket to Idira support or contact your account representative. For more details, see the SWS Activation Documentation.
      • Once activated, the tenant administrator can add additional admins by sending them an invitation link and adding them to the SWS Admins role. Full details can be found here.


Can we reduce the permissions outlined in the documentation?

  • No, these are the permissions required to install and operate SCA.

 

Onboarding

I need to onboard manually. Is there documentation on this?


How do I create a web app from SCA?

  • We recently introduced a more simplified way to create a web app from SCA to help you save time and reduce the need to jump between different pages and services.

    This new web app creation process:
    • Reduces the steps needed to create the web app
    • Provides the option of configuring trust automatically for AWS IAM accounts and organizations
    • Tracks web app creation events in the Audit service


How soon after onboarding workspaces to Cloud Visibility can I see them in SCA and start setting up cloud access policies?

  • This depends on whether you are onboarding new workspaces to Cloud Visibility, or whether the workspaces are part of a previously onboarded cloud organization/directory; for example, if you add new accounts to a previously onboarded AWS organization.
WorkspaceWorkspace Discovery and Resource Scan
NewWhen you onboard new workspaces, whether a standalone workspace or a full cloud organization or directory, we immediately run a full discovery of the workspaces that you're onboarding.
Depending on the size and structure of the workspaces, it can typically take a few minutes to a couple of hours before you can start working with them in SCA.
Previously onboardedIf structural changes are made in the cloud, for example accounts are added to an AWS organization that has been onboarded, these are picked up in SCA after our scheduled discovery and scan as follows:
  • Discovery - Once a day (every 24 hours) we run a discovery of all the onboarded workspaces in Cloud Visibility.
This process detects structural updates in the corresponding cloud environments and updates Cloud Visibility and SCA accordingly.
For example, if structural changes (add/delete/rename/move accounts) are made to an onboarded AWS organization, these changes are reflected in SCA after the scheduled daily discovery.
 
  • Scan - In parallel, for all onboarded workspaces, SCA directly scans the cloud environment twice a day (every 12 hours) for roles and permissions, and in the case of Microsoft Entra ID, it also scans for resources (resource groups and resources).
  


Is it possible to delegate administration to control access to a specific Cloud provider (such as only AWS or GCP)?

  • Yes, there is a concept of delegation for SCA that is currently located in the Cloud Visibility interface, under Setting -> Workspace Delegation. Screenshot below.
 
ka3Vy00000ChcEPIAZ__eid=ka3Vy00000ChcEP&feoid=00N2J00000APFDu&refid=0EMHt00000785ll.png


Does SCA require Cloud Visibility (CV) to correctly function?

  • As of today, SCA is utilizing Cloud Visibility for 2 functionalities: (1) SCA uses the Cloud Visibility user interface for onboarding Cloud ‘workspaces’, and (2) SCA consumes configuration of Delegation from Cloud Visibility and enforces it in the Policy management part.
  • Cloud Visibility and SCA are functionally separate:
    • Once the initial Cloud Visibility onboarding of the CSP ‘workspaces’ is done, SCA communicates directly to them (including retrieval of Cloud Roles and cloud workspaces).
    • Cloud Visibility does not show the state of onboarding from an SCA perspective. 
    • Successful CSP Workspace onboarding to Cloud Visibility doesn't indicate the SCA functionality.
    • SCA is independently retrieving the information from the CSP using its own AWS Roles, Azure app registrations and GCP service account.


Do Cloud Visibility workspace limits apply to SCA?

  • No, there are no defined limits with regards to the number of onboarded workspaces. There is currently a limit on the number of workspaces that you can ‘Connect’ to Cloud Visibility and scan with Cloud Visibility (the limit is 100).


How do Cloud Visibility and SCA handle secret rotation?

  • Review our Knowledge Base Article here, which outlines how Cloud Visibility and SCA handle secret rotation, and how you can manually rotate or regenerate a secret if it expires, becomes invalid, or becomes compromised.


Policies

Are there any policy best practices Idira recommends?


What is the difference between pre-defined and on-demand SCA policies?

  • Pre-defined policies are created manually by an administrator to address specific use cases in the organization.
  • On-demand policies are created automatically by SCA when an on-demand access request is approved. These policies are deleted when the access window of the on-demand session closes.


When should I use group binding vs. direct binding?

Binding MethodMethodProsCons
GroupWhen policy is created, it creates a group per role and the selected scopeSignificantly utilize less role bindings in scope level.Might have latency when add / remove user to / from group.
Some constraints might be on adding members to a group that are not of the same domain.
DirectWhen policy is created, nothing happens. The assignment is done only when the user connects, on the user itself.No latency when connecting.For large organizations with hundreds of users and roles, the quota limit can be reached faster.
  • Use group binding when you manage access to hundreds of users and roles.
  • Shifting from group binding to direct binding can be done without re-creating the policies, the opposite can't be done without re-creating the policies.
     
  • GCP:
  • Azure:
    • Limit of 4,000 role assignments per subscription
    • Limit of 5,000 role assignments per management group
    • More on Azure quota limitation information is available in the Microsoft Azure documentation


I’m not seeing AWS IAM roles in the SCA Policy Wizard.


Do I need to modify Permissions on the Web App (on Identity) for SCA?

  • No, SCA is managing the permissions part of the Web Apps that it uses (for all clouds). Creation of an SCA policy for user Bob (or Role 'c App X Support') will add that user (or Role) to the list under Permissions of the Web App and as a result publish the WebApp to Bob (or members of the App X Support Role).


How long does it take to revoke permissions from an identity after the access window closes, such as when a session with a configured length of 2 hours expires?

  • SCA revokes permissions immediately after the session expires (~1 minute). However, each cloud provider has its own method for calculating and re-evaluating the active permissions for an identity, so the new (reduced) permissions may take anywhere from a few seconds to several (up to 15) minutes to become effective.
  • Note: AWS IAM Identity Center has a known issue where it lets the identity stay connected to the management console even after permissions are revoked. The new permissions only take effect when the identity disconnects (and therefore can't connect again). Idira is working with AWS to resolve this issue.


I can’t see roles in the policy. What should I do?

  • If you have recently scanned a new instance, it may take up to three and a half hours to fully scan and populate the fields in a policy. If this is an older environment: in CyberArk, please go to a new policy, and click on the scan button in the top right when on the entitlement assignment page. This scan should look for new roles or changes to roles in your environment.
  • If neither of these have worked, please open a ticket with support.

 

Discovery

Is there a way to manually discover and scan onboarded workspaces?

  • Yes. You can manually trigger an SCA discovery using Terraform or SCA's Discovery API (/policies/discovery). By default, this API:
    • Discovers of all the workspaces that are already onboarded to Cloud Visibility,
    • Scans for roles and permissions, and in the case of Microsoft Entra ID, it also scans for resources (resource groups and resources).

For details, see SCA policy APIs.

  • Alternatively, if you only want to scan for roles and resources, and you are not concerned with structural changes in your cloud environment, you can run a scan either from the SCA UI, or using the SCA API:
    • SCA UI: When creating a policy in the Create policy wizard, in the Select roles dialog box, click Scan again
    • SCA API: Send a /cloud/rescan API request - see SCA general cloud activity APIs

Note: Scan again and /cloud/rescan scan the cloud environment directly.

How do I discover new or changed roles?

  • Please go to an old or new policy and go to the role selection screen. In the top right there is a scan button, press this to issue a role re-scan with SCA.  Alternatively, you can use the API to do the same action.


Automation

What permissions are required to run APIs?

  • CEMAPIAdmin
    • Users can perform all available API operations including onboarding and delegating cloud workspaces. This role should only be assigned to tenant owners and administrators.
       
  • CEMAPIUser
    • Users can perform API operations that don't require admin privileges.
       
  • SCA ApiFullAccess
    • Users have full access permissions for SCA APIs.
       
  • SCA APIReadOnly
    • Users have read-only permissions for SCA APIs.


How do I avoid over-permissioning?

  • For SCA, there is a single way to gain access to the API to carry out a task. Because of this, the only suggestion is to make sure you have two service accounts for running the API. One service account is to read the current policies for automation and discovery purposes that utilizes SCA APIReadOnly, while the other service account is for policy creation and role scanning and should only be checked out for those processes.


What can be automated?

  • Automation can be done using Terraform (TF). When using TF to onboard new workspaces to your cloud environment, you can add SCA onboarding to your existing automation. This ensures that the new workspaces have SCA policies in place with zero standing permissions as soon as they are added to your cloud environment. Keep in mind, SCA supports using automation to add workspaces to organizations and directories that were previously onboarded to SCA using Cloud Visibility. 

 

Optimize/Advanced Use Cases

My organization has a specific use case that may require a unique architecture configuration. Are there examples I can reference that other organizations may have requested?

  • Check out our Design Guides for Unique Architecture for some inspiration. If you have a specific architectural scenario not included here, please reach out to your Idira Account Representative.


General

How can I confirm how many SCA licenses we're using without engaging Palo Alto?

  • SCA's licensing is based on the number of active users over the last 30 days. To generate a count of the number of unique users who have used SCA over the last 30 days, do the following:
    • Export an Audit report with the following filters:
      • Time range: Last 30 days
      • Action: Login
      • Service Name: Secure Cloud Access
    • Deduplicate the UserID column
      • Google sheets: Data > Data Cleanup > Remove duplicates
      • Excel: Data tab > Data Tools > Remove Duplicates
    • Obtain a count of the remaining rows (e.g., unique UserIDs/usernames)

What if my organization uses a 3rd party IdP?

  • Idira Identity can be federated with a 3rd party IDP to authenticate users into CyberArk. The question becomes how Idira integrates with the CSP which is as follows:
    • AWS IAM – Idira can be configured as a secondary IDP in each AWS account.
    • AWS IIC –  SCA supports the customer keeping their IDP configured in AWS.
    • IDC.GCP – SCA supports the customer keeping their IDP configured in AWS. IDC.GCP also allows for a secondary IDP to be configured if necessary but this is an unlikely scenario for the customer to choose.
    • Azure – Idira does not need to be configured as an IDP in Azure.


How do I comply with Microsoft's Multi-Factor Authentication (MFA) requirement on Azure?


Where is the authoritative source of the users? Do users need to reside in both the CSP’s, SCA, and IdP?

  • The authoritative source of users can be any of your IDP’s (Okta, Entra ID, Idira Identity, Google Workspaces, etc.).
  • Do users need to reside in both the CSP’s, SCA, and IdP? See below:
    • AWS IAM : No, we use SAML federation to assign the AWS IAM Role to the user that is logged into Identity.
    • AWS IIC: Yes, AWS IIC requires that a user be provisioned into AWS IIC before that user can login. We can provision using SCIM, the customer can use their SCIM tool of choice, or the user can be manually created.
    • GCP: Yes, SCA expects that the user requesting to elevate their access has a GCP user account of the same name.
    • Azure: Yes, SCA expects the user requesting to elevate their access has a matching user account in Azure AD.


I can’t find the answer to my question.

  • 5687 Views
  • 0 comments
  • 0 Likes
Top Liked Authors