Secure Cloud Access Articles
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!
Idira Secure Cloud Access (SCA) Architectural Design Guide CSP use: Google Cloud Platform (GCP) Use case description A customer wants to provide access for external users and vendors into their cloud environment, and the vendors’ identities are not part of the company directory. The customer is using Idira Secure Cloud Access (SCA) for zero standing privileges, Idira Identity as the IDP, and Google Cloud Platform (GCP) as the cloud provider. An external user / vendor wants to log in into a company's GCP project with CyberArk’s web app. Since the external user’s (or vendor’s) identity is not provided by the customer, the user has a different email address from this company.   Steps Architectural scenario Idira is used to provision an external user/vendor (that is not managed by the company’s directory), and to facilitate access to the company’s Google Cloud Platform (GCP) project. This architectural design lets you use an external entity’s (user/vendor’s) email address that has a different domain from the company domain (user/vendors’ identities are not part of the company's directory) to allow access to GCP through the company’s Idira portal web app.   Prerequisites The customer needs to create and configure two GCP web apps: A web app for the connection to GCP with SCA enabled and a GCP web app with outbound provisioning to GCP from Idira Identity (Idira must be the IDP, i.e. The “Idira as the IDP” checkbox is selected within the Secure Cloud Access section of the web app). The customer must also configure the web app to work with SCA. Expected behavior A vendor logs in to CyberArk’s Identity Portal and gets a GCP web app tile. The vendor / user clicks the GCP tile and gets the GCP project with the specific roles attached for them in the SCA policy. Architecture configuration This configuration is unique where the user’s identifier (email address) differs from what GCP expects (the company’s domain) and therefore uses an account mapping approach for vendor access to GCP. In this scenario, two web apps are necessary: one for GCP access, the other for provisioning. The basic provisioning works as required (the user account is provisioned to GCP with the correct domain suffix). However, when SCA tries to assume the role on the GCP project, SCA takes the username from the Email attributes of the user in Idira Identity. Since this user is an external vendor, the Email field is not from the customer’s organization domain (it could be, for example, “cyberark.com” or “gmail.com” or any other domain that is different from the organization domain). Since this user, which was taken from the Email field, has not been provisioned to GCP, they cannot assume any role and an error is generated. The solution for this use case is to use the Account Mapping feature in the web app configuration to let SCA assume the role to the correct username (caution must be taken to ensure a unique identity, ex  <alias>[email protected] is used). But, since provisioning is configured, account mapping is disabled and cannot be configured together with the provisioning configuration (this is by design in Idira Identity). The workaround for this situation is to create two web apps: one for provisioning and one for SCA, as detailed below. Implementation steps To use provisioning and the account mapping for SCA, do the following: Create two GCP web apps: One web app only for the connection to GCP with SCA enabled. One web app for the outbound provisioning to GCP without SCA enabled.   In the GCP web app with SCA enabled, configure a one row script in Account Mapping to let SCA get the correct username with the correct organization domain. Script:   LoginUser.Username = LoginUser.Shortname + "@[ORGANIZATION DOMAIN]";   In the GCP web app without SCA enabled, configure a script in Provisioning within the Provisioning Script area as shown below (ensuring the use of your respective values).  The web app for provisioning does not need to be available for the users, so it can be hidden from the Idira Identity user portal (deselecting “show in user app list” under Settings of the web app). Example of provisioning script (requires some customization) if (source.Classification == "User") { destination.DisplayName = source.DisplayName + source.DisplayName.split("@")[0] + "@Add-Domain-Name.com" ; destination.Username = source.DisplayName + source.DisplayName.split("@")[0] + "@Add-Domain-Name.com" ; destination.Email = source.DisplayName + source.DisplayName.split("@")[0] + "@Add-Domain-Name.com" ; trace('DisplayName=' + destination.DisplayName); destination.PrimaryEmail = source.Email.split("@")[0] + "@" + GoogleDomain; //Obtain First and Last name by splitting DisplayName on space char. //Token 0 is FirstName, Token 1..N is LastName. var nameTokens = source.DisplayName.split(" "); destination.FirstName = nameTokens[0]; if (nameTokens.length == 1) { destination.LastName = nameTokens[0]; } else { destination.LastName = nameTokens.slice(1, nameTokens.length).join(" "); } destination.HomePhone = source.HomePhone; destination.MobilePhone = source.MobilePhone; destination.OfficePhone = source.OfficePhone; // The code below is to set the user's Aliases by the Proxy Addresses. // Alternatively, you can set the user's Aliases by the syntax: // destination.Aliases = "[email_address_1],[email_address_2]"; // Note: The email addresses must be in verified domain and not exist in the account. var proxyAddresses = source.GetDsProperty("ProxyAddresses"); if (proxyAddresses !== null && proxyAddresses.Length > 0) { var addrString = ""; for (var i = 0; i < proxyAddresses.Length; i++) { if (addrString) { addrString += "," + proxyAddresses[i]; } else { addrString = proxyAddresses[i]; } } destination.Aliases = addrString; } } if (source.Classification == "Group") { var propArr = getSourcePropertyByName("description"); if (propArr && propArr.Length) { destination.Description = propArr[0]; } destination.Email = DefaultEmail.split("@")[0] + "@" + GoogleDomain; propArr = getSourcePropertyByName("name"); if (propArr && propArr.Length) { destination.Name = propArr[0]; } } // to filter/omit groups from sync use the reject() method. // the example below skips the sync of groups based on elements // in the distinguished name (any group in org unit of accounts, is skipped) // you can uncomment the code below and replace ou=accounts with // applicable name component for your org. /* if (source.Classification == "Group") { var dnArray = getSourcePropertyByName("distinguishedname"); if (dnArray && dnArray.Length) { var dn = String(dnArray[0]).toLowerCase(); if (dn.indexOf("ou=accounts") >= 0) { reject("ou=accounts, is rejected"); } } } */
View full article
When you register apps in Azure or add service accounts in Google Cloud for SCA and Cloud Visibility, these platforms provide the apps/service accounts with secrets so that they can get permissions to perform necessary activities. This document describes how SCA and Cloud Visibility handle secret rotation, and how you can manually rotate or regenerate a secret if it expires, becomes invalid, or becomes compromised.       Steps Solution This section describes how to manually rotate or regenerate secrets for your Azure apps or Google Cloud service accounts. Cloud Provider Solution Azure Cloud Visibility - When you register Cloud Visibility in Azure, we recommend that you create a secret that is valid for 24 months. When the secret expires or if it becomes invalid, Cloud Visibility displays an error. Click the error to get online instructions for creating a new secret in Azure and updating it in Cloud Visibility. If the secret is compromised, delete it manually from Azure. Cloud Visibility detects that the secret is missing and displays an error. Click the error to get online instructions for creating a new secret in Azure and updating it in Cloud Visibility. For more information, see the Cloud Visibility docs.   SCA - When you register SCA in Azure, we recommend that you create a secret that is valid for 60 days. SCA automatically rotates this secret every 30 days. If you want to manually generate a new secret before the scheduled automatic rotation, please open a support case with Idira Customer Support. GCP Secrets for Cloud Visibility and SCA service accounts are created with no expiration date. If you want to manually generate a new secret, see the instructions in our Cloud Visbility (CV) docs here.  
View full article
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 Get Started The Basics Secure Access to Cloud Service Providers Expand 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.    Other tenant questions? Refer to our Common FAQs here.     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. 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 Add Idira Cloud Directory Users Assign Users to any necessary roles SCA Users and Roles   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:    Onboard all CSP Workspaces   Web App Creation for all CSPs   AWS Step 2A: Onboard your AWS cloud workspace to CyberArk Onboard an AWS single account  Add an AWS Standalone Account Video - Onboard AWS Standalone Account   Onboard an AWS Org  Discover a new AWS organization Video - Onboard AWS   Onboard an AWS Identity Center (IDC) Discover a new AWS organization Video - Onboard AWS with IDC   Step 2B: AWS Web App Creation  AWS Web App Creation  AWS Web App Creation Video - AWS Web App Creation Standalone   AWS Web App Creation Org   Video - AWS Web app creation with IDC   Azure Step 2A: Onboard your Azure cloud workspace to CyberArk   Onboard Azure Entra ID  Add Azure Microsoft Entra ID Video - Onboard Entra ID Step 2B: Azure Web App Creation  Create a Web App for Microsoft Entra ID Video - Azure   GCP Step 2A: Onboard your GCP cloud workspace to CyberArk  Onboard GCP Add Google Cloud Video - Onboard GCP Step 2B: GCP Web App Creation  GCP Web App Creation  Create a Web App for Google Cloud Video - GCP     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  Automate Onboarding and Policy Creation with Terraform Wiz Integration 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 Automation section of FAQs    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. Idira Secure Cloud Access (SCA) Policy Best Practices  Policies FAQs  AWS IAM and AWS Identity Center (IDC) Access policies for AWS IAM and AWS Identity Center AWS IAM AWS IDC Azure Entra ID and Azure Resource Create Policies for Azure Resources and Microsoft Entra ID Directories Video - Create a Policy for Azure Resource Roles   Video - Create a Policy for Entra ID Roles   GCP Access policies for GCP Video - Create a Google Cloud Policy   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 AWS Connect to Azure (Console to CLI) Connect to Microsoft Azure Connect to GCP (Console to CLI) Connect to Google Cloud 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.  [ADMINS] Setup on-demand access for your end-users:    For the end-users: Learn how to make a one-time, on-demand access request to a different CSP role.  Video Overview - Request on Demand Access for a Different Role in the Same Account   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.  Secure Web Sessions Video - How to Configure SWS 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.  Assign Auditor Access Audit service: Assign (a) user(s) the “global auditor” role, as mentioned here.  SWS Service View System Activities Monitor User Sessions Check out audit events and codes   [OPTIONAL] Step 9: Configure general SCA settings   Executed by: Cloud Security Admins Learn how to configure service settings to optimize Secure Cloud Access for your organization’s CSPs  [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.  Manage Workspace Delegation Video - Delegate Workspace Owners   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    
View full article
Idira SCA Policy Best Practices Purpose This document is to help Idira customers to implement Secure Cloud Access (SCA) and focuses on best practices for creating and applying SCA policies. The overall objective of using the SCA solution is to enhance security by implementing better controls around human access to your cloud environments and enabling transition from standing assignment of privileges to zero standing privileges (ZSP). This document assumes that the reader is familiar with cloud technologies, particularly with human access to a Cloud environment, and has a basic understanding of Idira Secure Cloud Access and how to create/apply SCA policy types.   Steps Definitions Cloud role - A collection of permissions that determine which actions a user can perform on a specific resource within the cloud environment. For example, in GCP, predefined roles give granular access to specific Google Cloud resources and are created and maintained by Google. CSP – Cloud Service Provider. Specifically, AWS, GCP, Azure. Job function/role – Represents a person’s job and the function they perform, such as a DB admin. Workspace – A general term used within this document to represent an AWS Account, a GCP Project, or an Azure Subscription. Model  The Idira SCA policy model is composed of two elements: What the SCA policies specify: Which cloud roles within each cloud environment can be assigned. Which principals (users, groups, job roles, etc.) can get the cloud roles assigned. The duration and time window when the assignment is made. The two types of SCA policies: Long-lived: Typically assigned to groups of users (per job role, team, etc.) Short-lived: On-demand policies that are requested when needed, granted for short periods of time and to specific users. For some cloud roles, these policies should not exist at all, but should be created on-demand and granted when needed. Top five best practices Apply least privilege. Configuring the correct policy definitions is fundamental to ensure the required security for your system. Apply least privilege by granting users only the minimum permissions that they need to perform their daily tasks. Providing more permissions than needed can lead to unwanted activity in the Cloud environments, either maliciously or accidentally. Implement least privilege by: Assigning policies only to required cloud roles. For example, a policy used by a DBA for accessing S3 buckets. Including only those identities that need specific role access. Leverage automation. Automate policy creation via API/Terraform. Audit/remove standing access.  Remove assignments from existing CSP policies that are now defined by Idira SCA policies, such as those from Identity Center permission sets. Limit the policy timeframe when applicable. Ensure that policies are created with appropriate time limitations and an expiration date (if applicable) to a specific workspace. Use short-term policies for temporary access. For extended, time-limited, or project work, use a defined timeframe (for example, 2-4 weeks).  This configuration ensures that developer eligibility and access permissions are only active with each request. Set appropriate access rules.   Add identities (groups, Idira Identity roles) to the policy according to least privilege. Use groups instead of individuals (specific user accounts) for general access. Set maximum session lengths based on the workspace. For example, four hours for Development, one hour for Production. Define explicit work hours per region. If necessary, duplicate the policy for different time zones, to enable more granular access restrictions.  Additional policy best practices Establish a policy naming standard. See our dedicated SCA policy naming convention best practices article for information about this subject. Use clear policy descriptions. Add a description about the purpose of the policy. For example: APAC team accessing the Contributor Cloud role for production Azure Intune. Developer team for full access to EC2 during CHG63287. Use custom permissions. Use customized cloud entitlements when possible.  Start with pre-defined permissions and create custom roles or policies, because cloud providers' managed policies (e.g., AWS managed policies, Azure built-in roles, GCP predefined roles) may change and may not always adhere to least privilege.  Clean up policies regularly. Review and remove unused policies every six months. Use conditions for access. In addition to SCA limitations, some CSPs let you add extra restrictions to entitlement usage, such as limiting access to specific resources, time of day, or MFA status. Have break-glass access policies ready.  These policies grant emergency access to critical systems and should be used in exceptional circumstances, such as during a security incident or primary identity provider (IdP) failure. Ensure these policies are available for SCA access and CSP access. Leverage PAM, if possible, for break-glass identities. Manually approve high-level (root) access. All high privilege requests should undergo manual approval. Basic/native or lower-level access, such as read-only or audit trail for developers, can be automatically approved (with tags when possible). Specific guidelines with Tags. A Ensure seamless developer productivity by enabling auto-approval based on tags tied to workspaces.  This automates the provision of necessary permissions for existing and new team members without manual approval delays.  For example, a tag “Payment-Dev-Team” can be created for an application development team working on payment services, with automatic approval for team requesting access with this tag for a developer role.   Define policies for every environment. Ensure that SCA policies are defined for development teams in all environments (development, test, staging, and prod, etc.). This will ensure that developers can build, test, and deploy their code up to the stage environments. In production, grant access on-demand for visibility and troubleshooting, and revoke it afterwards. Leverage delegation. Development team managers can create policies for themselves and their teams by using the delegation module to grant policy creation rights to sub-members, reducing dependency on approvals and maintaining development velocity. Manual approval for production access should remain in place, requiring approval from the appropriate approvers. Idira recommends reviewing any admin-created policy to ensure it aligns with company security goals. Audit policies that were created via delegation every 90 days to ensure least privilege. Understand max session length. Maximum session lengths are set by cloud providers, with a minimum of one hour. Within SCA, a session length of 1 - 4 hours is recommended for all tasks, to limit exposure of entitlements in the cloud provider environment. Session length should be based on the company’s risk tolerance. Record sessions. Engineering team leads and managers should leverage session recordings for audit purposes. Session length should be aligned with the company’s risk tolerance.
View full article
  • 4 Posts
  • 7 Subscriptions