SCA Getting Started Guide

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Scheduled Maintenance: November 14–15 (starting Nov. 14 at 12:00 AM PST)
LIVEcommunity will temporarily operate in read-only mode as we prepare to welcome Idira!
Public content will remain accessible, but log-ins, posting and community interactions will be paused during this period. Thank you for your patience!
Secure Cloud Access Articles
11 min read
L4 Transporter
No ratings

SCA Getting Started Guide

Welcome to Secure Cloud Access (SCA)! Let’s get started on your journey. This “Getting Started Guide” is designed to help your organization configure and understand each of SCA's core capabilities, prior to performing an enterprise-wide rollout. We recommend completing the steps below in order. 

If you have any questions about this guide or Secure Cloud Access overall, ask us in our SCA community feed.

Content Overview

Get Prepared

  • Involve the right people: As with most areas of identity security, it’s often helpful (if not required) to engage various internal teams/resources beyond the security solution’s administrators when implementing a new security control. In the case of an SCA implementation, you’ll want people who can help provide access to your organization’s cloud environments (often a test environment, to start), assuming you don’t already have this access yourself. You’ll also want a few users to help test the solution. Ideally, these would be users who have an interest in security and are more likely to become champions for the controls being implemented. 

 

  • Activate Your Identity Security Platform Tenant and Secure Web Sessions 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. 

 

 

  • Review our Getting Started Guide flowchart
      • We've created the following flowchart to support you on your SCA journey. It’s meant to act as a visual aid that allows you to view the entire process, from start to finish, in a single view.

ka3Vy00000B3ztRIAR__eid=ka3Vy00000B3ztR&feoid=00N2J00000APFDu&refid=0EMVy00000Yfcdd.png

Get Started

The Basics

Now that you’ve logged into your tenant, let’s dive in. Once again, it’s recommended to follow these steps in order. 

Step 1: Set up users

Executed by: Cloud Security Admins

 

For your first step, let’s get users into SCA. Which direction you take depends on several factors, including whether you want to use an exclusive test account or a “real” user through an integration with an external IdP (whether said integration already exists or not). 

 

For most testing purposes, we recommend creating users directly in the Idira Cloud Directory, as it’s the easiest to get up and running. Even if your Idira environment is already integrated with an external IdP, if a relevant test user isn’t already provisioned into the Idira Cloud Directory, we still recommend going to the Idira Cloud Directory route to avoid any complications around existing permissions. 

 

Create users directly in the Idira Cloud Directory

 

Integrate with an external IdP 

This PowerPoint presentation will walk you through the various options, including use cases, benefits, and disadvantages, as well as links to how to configure them. 

Step 2: Connect your cloud environment

Executed by: Cloud Security Admins

 

In this step, you’ll add your cloud environment to the Idira platform and create a one-click access point for your users. 

Step 2 is organized by CSP, with each broken into two parts.  Part A involves onboarding your relevant CSP workspace(s) to CyberArk, and Part B outlines creating a web app for one-click user access. 

 

Note: Interested in seeing this step for all CSPs? See the two video summaries below: 

 

 

 

AWS

Step 2A: Onboard your AWS cloud workspace to CyberArk

Onboard an AWS single account 

 

Onboard an AWS Org 

 

Onboard an AWS Identity Center (IDC)

 

Step 2B: AWS Web App Creation 

AWS Web App Creation 

 

 

 

Azure

Step 2A: Onboard your Azure cloud workspace to CyberArk

 

Onboard Azure Entra ID 

Step 2B: Azure Web App Creation 

 

GCP

Step 2A: Onboard your GCP cloud workspace to CyberArk 

Onboard GCP

Step 2B: GCP Web App Creation 

GCP Web App Creation 

 

 

Step 3: Automate SCA Operations

Executed by: Cloud Security Admins & Platform Engineers 

 

In this step, learn about SCA operations that can be automated or performed programmatically. Although not all teams or organizations have the capacity to fully automate, it’s important to understand what’s possible to determine if automation is right for you. 

For example, you could automate policy creation or go even further and secure new cloud workspaces at birth by integrating SCA APIs in CI/CD pipelines or Infrastructure-as-Code.

 

Integrations that can assist with automation 

Review our SCA APIs

  • SCA APIs
    • See our Bruno collection for API usage examples here
      • Note: The GitHub resource above was created by Eli Hopkins and not by CyberArk. Idira disclaims any liability for the information provided in this resource.

Idira Community Resources

 

Secure Access to Cloud Service Providers

 

Step 4: Configure daily access

Define who can access what, when, and under what conditions. 

Executed by: Cloud Security Admins 

 

The most straightforward way to familiarize yourself with SCA’s capabilities is to create a pre-defined access policy, which defines who can access what, when, and under what conditions. This type of policy is most often used to provide users with the entitlements they require on a daily basis while allowing for the removal of standing privileges within the CSP, thus helping you achieve Zero Standing Privileges (ZSP) for your Cloud Service Providers. 

 

Need a refresher on the principle of ZSP? Review our glossary article, found here. 

 

For a video outlining how to create policies for the CSPs listed click below.

Before diving into the individual CSPs below, we’d encourage you to familiarize or refresh yourself on our SCA policy best practices, using the resources below. While some of the content is more applicable to preparing for the full enterprise rollout, much of it will still be helpful to keep in mind as you begin your journey with SCA.

AWS IAM and AWS Identity Center (IDC)

Azure Entra ID and Azure Resource

 

 

GCP

 

Step 5: Connect to your cloud environment

Executed by: End-Users

Now that you’ve onboarded your workspace(s), created one or more web apps for the relevant CSPs and a policy or two, it’s time for your initial users to make their first connections. Provide your users with the relevant content below, which will teach them how to connect to their CSP workspace(s) using SCA. The links below will direct users to short videos that provides instructions for AWS, Azure, and GCP. If your users prefer written guides instead, we’ll supply links to those guides in the subsections below. 

Video - Learn how to connect to your CSP workspace(s) within AWS, Azure, or GCP

 

Connect to AWS IAM and IDC (Console & CLI)

Connect to Azure (Console to CLI)

Connect to GCP (Console to CLI)

Step 6: On-Demand Access

Executed by: Cloud Security Admins & End-Users

 

While daily access is generally covered with pre-defined SCA policies, users may need to further elevate their access. This may come in the form of accessing a different workspace than normal (such as a Production environment, perhaps) or accessing the same workspace(s) they normally do but with additional privileges than allowed through pre-defined SCA policies. 

This step is therefore about configuring on-demand access workflows that allow for such usage, and it’s a combo step for both Cloud Security Admins and end-users. Details for each role are outlined in the documentation linked below, but if a video summarizing both is preferred, see here: 

 

Video Overview - Request on Demand Access for a Different Role in the Same Account

 

YouTube video: For the full, on-demand user experience for AWS access (using an integration with ServiceNow click below.

 

Note: Before providing end-users links to the written documentation, Admins should first determine whether their Idira tenant has the “Secure Access” space. The documentation for on-demand access will differ slightly based on whether your tenant includes this space, so it’s important to direct them to the correct location. 

 

For the admins: Learn how to configure the SCA approval mechanism so that end-users can request temporary access to web apps. 

 

For the end-users: Learn how to make a one-time, on-demand access request to a different CSP role. 

 

Expand 

Step 7: Enforce Session Recording

 

You’re almost there! For our next step, it’s time for some (very important) extra credit. Check out this additional use case focused on session recording, a key defense layer in further reducing risk. 

Step 8: Audit

With new security controls come new events to monitor. Let’s make sure your auditors and managers have the information they need to ensure compliance with your security policies. Leverage the content below to learn how to monitor SCA system activities and user sessions. 

 

[OPTIONAL] Step 9: Configure general SCA settings  

Executed by: Cloud Security Admins

[OPTIONAL] Step 10: Delegate Workspace Ownership 

Executed by: Cloud Security Admins

Although this step is not required, if you (as the admin) would like to delegate access policy management for one or more cloud workspaces in the organization, review the resources listed below. 

 

Congratulations!

You’ve reached the end of our Getting Started Guide for SCA. Ideally, you’ve come away with a foundational understanding of how SCA operates and are now better situated to begin planning your enterprise rollout. If you have any questions on this guide or on SCA overall, ask in our SCA Community or review our FAQs. 

What's Next?

As you begin your full enterprise implementation of SCA, you’re bound to have questions. Depending on the nature of your questions or the type of assistance you require, we have several options to help keep you moving forward: 

 

Additional Resources

Use these practical resources to get your setup right the first time. Bookmark them for later or share them with your team.

  • SCA FAQs – Find answers to common questions from the SCA community. 
  • Success Office Hours - Join us for our regularly scheduled, live Success Office Hours to learn more SCA best practices and connect directly with the Idira team.
  • SCA Architecture Hub - Our library where you can review design guides for unique architecture use cases and documentation on the permissions SCA requires within AWS, Azure, and GCP environments. 
  • Idira Community: Join the Secure Cloud Access Resource Center. Join this SCA community group to stay informed on the latest product news and best practices. Use the community feed to ask questions and collaborate with your peers and the Idira team.  
  • Idira Marketplace - Visit the Marketplace to discover our C3 integrations and partnerships to further strengthen your organization’s cloud security. 
  • E-Learning Module: Cloud Security Learning Path
  • Product Documentation: Learn more about Secure Cloud Access

Expert Guided Options

  • Engage Idira Professional Services 
  • Engage a delivery partner 

 

Thank you,
Idira Customer Success

 

 

Rate this article:
  • 2660 Views
  • 0 comments
  • 0 Likes
Article Dashboard
Version history
Last Updated:
‎11-05-2026 11:46 AM
Updated by: