<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Idira Secure Cloud Access (SCA) Policy Best Practices in Secure Cloud Access Articles</title>
    <link>https://live.paloaltonetworks.com/t5/secure-cloud-access-articles/idira-secure-cloud-access-sca-policy-best-practices/ta-p/1430028</link>
    <description>&lt;H2 style="margin-top: 11px;margin-bottom: 5px;"&gt;&lt;SPAN style="font-size: 16pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: &amp;quot;Aptos Display&amp;quot;,sans-serif;"&gt;&lt;SPAN style="color: #0f4761;"&gt;&lt;SPAN style="font-weight: bold;"&gt;Idira SCA Policy Best Practices&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: &amp;quot;Aptos Display&amp;quot;,sans-serif;"&gt;&lt;SPAN style="color: #0f4761;"&gt;Purpose &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/H2&gt;
&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;This document is to help Idira customers to implement Secure Cloud Access (SCA) and focuses on best practices for creating and applying SCA policies.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;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).&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;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.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;

&lt;H3&gt;Steps&lt;/H3&gt;
&lt;H2 style="margin-top: 11px;margin-bottom: 5px;"&gt;&lt;STRONG&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: 'Aptos Display',sans-serif;"&gt;&lt;SPAN style="color: #0f4761;"&gt;Definitions&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/H2&gt;
&lt;UL style="margin-bottom: 11px;"&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Cloud role&lt;/B&gt; - 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. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;CSP &lt;/B&gt;– Cloud Service Provider. Specifically, AWS, GCP, Azure.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Job function/role&lt;/B&gt; – Represents a person’s job and the function they perform, such as a DB admin.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-bottom: 11px;margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Workspace &lt;/B&gt;– A general term used within this document to represent an AWS Account, a GCP Project, or an Azure Subscription. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;H2 style="margin-top: 11px;margin-bottom: 5px;"&gt;&lt;STRONG&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: 'Aptos Display',sans-serif;"&gt;&lt;SPAN style="color: #0f4761;"&gt;Model&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/H2&gt;
&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&amp;nbsp;The Idira SCA policy model is composed of two elements:&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;OL&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;What the SCA policies specify:&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;OL style="list-style-type: lower-alpha;"&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;Which cloud roles within each cloud environment can be assigned.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;Which principals (users, groups, job roles, etc.) can get the cloud roles assigned.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;The duration and time window when the assignment is made.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;The two types of SCA policies: &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;OL style="list-style-type: lower-alpha;"&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;Long-lived: Typically assigned to groups of users (per job role, team, etc.)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 8px;margin-bottom: 11px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;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.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;H2 style="margin-top: 11px;margin-bottom: 5px;"&gt;&lt;STRONG&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: 'Aptos Display',sans-serif;"&gt;&lt;SPAN style="color: #0f4761;"&gt;Top five best practices&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/H2&gt;
&lt;OL style="margin-bottom: 11px;"&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Apply least privilege.&lt;/B&gt; 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:&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;OL style="list-style-type: lower-alpha;"&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;Assigning policies only to required cloud roles. For example, a policy used by a DBA for accessing S3 buckets.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;Including only those identities that need specific role access. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Leverage automation.&lt;/B&gt; &lt;B&gt;Automate&lt;/B&gt;&lt;B&gt; &lt;/B&gt;policy creation via API/Terraform. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="tab-stops: list .5in;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Audit/remove standing access. &lt;/B&gt;&amp;nbsp;Remove assignments from existing CSP policies that are now defined by Idira SCA policies&lt;B&gt;, &lt;/B&gt;such as those from Identity Center permission sets.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Limit the policy timeframe when applicable.&lt;/B&gt; &lt;SPAN style="background: white;"&gt;Ensure that policies are created with appropriate time limitations and &lt;/SPAN&gt;an expiration date (if applicable)&lt;SPAN style="background: white;"&gt; to a specific workspace&lt;/SPAN&gt;. Use&lt;SPAN style="background: white;"&gt; short-term policies &lt;/SPAN&gt;for temporary access&lt;SPAN style="background: white;"&gt;. For extended, time-limited, or project work, use a defined timeframe (&lt;/SPAN&gt;for example,&lt;SPAN style="background: white;"&gt; 2-4 weeks).&lt;/SPAN&gt; &lt;SPAN style="background: white;"&gt;&amp;nbsp;This configuration ensures that developer eligibility and access permissions are only active with each request.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="tab-stops: list .5in;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Set appropriate access rules. &amp;nbsp;&lt;/B&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;UL style="list-style-type: circle;"&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;Add identities (groups, Idira Identity roles) to the policy according to least privilege. Use groups instead of individuals (specific user accounts) for general access.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="tab-stops: list .5in;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;Set maximum session lengths based on the workspace. For example, four hours for Development, one hour for Production. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 8px;margin-bottom: 11px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="tab-stops: list .5in;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;Define explicit work hours per region. If necessary, duplicate the policy for different time zones, to enable more granular access restrictions.&amp;nbsp; &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;H2 style="margin-top: 11px;margin-bottom: 5px;"&gt;&lt;STRONG&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: 'Aptos Display',sans-serif;"&gt;&lt;SPAN style="color: #0f4761;"&gt;Additional policy best practices&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/H2&gt;
&lt;UL style="margin-bottom: 11px;"&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="tab-stops: list .5in;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Establish a policy naming standard.&lt;/B&gt; See our dedicated &lt;A href="https://community.cyberark.com/s/article/Best-Practice-SCA-Policy-Naming-Convention" target="_self"&gt;SCA policy naming convention best practices article&lt;/A&gt; for information about this subject.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Use clear policy descriptions.&lt;/B&gt; Add a description about the purpose of the policy. For example:&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;UL style="list-style-type: circle;"&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;APAC team accessing the Contributor Cloud role for production Azure Intune.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;Developer team for full access to EC2 during CHG63287.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Use custom permissions. &lt;/B&gt;Use customized cloud entitlements when possible. &amp;nbsp;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.&amp;nbsp; &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Clean up policies regularly.&lt;/B&gt; Review and remove unused policies every six months.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Use conditions for access.&lt;/B&gt; 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.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="tab-stops: list .5in;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Have break-glass access policies ready&lt;/B&gt;. &amp;nbsp;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. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="tab-stops: list .5in;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Manually approve high-level (root) access. &lt;/B&gt;All high privilege requests should undergo&lt;B&gt; &lt;/B&gt;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).&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Specific guidelines with Tags&lt;/B&gt;. A Ensure seamless developer productivity by enabling auto-approval based on tags tied to workspaces. &amp;nbsp;This automates the provision of necessary permissions for existing and new team members without manual approval delays. &amp;nbsp;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.&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;&lt;SPAN style="background: white;"&gt;Define policies for every environment.&lt;/SPAN&gt;&lt;/B&gt;&lt;SPAN style="background: white;"&gt; 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.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;&lt;SPAN style="background: white;"&gt;Leverage delegation.&lt;/SPAN&gt;&lt;/B&gt;&lt;SPAN style="background: white;"&gt; 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.&lt;/SPAN&gt; Audit &lt;SPAN style="background: white;"&gt;policies that were&lt;/SPAN&gt; created via delegation every 90 days to ensure least privilege.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;&lt;SPAN style="background: white;"&gt;Understand max session length. &lt;/SPAN&gt;&lt;/B&gt;&lt;SPAN style="background: white;"&gt;Maximum session lengths are set by cloud providers, with a&lt;B&gt; &lt;/B&gt;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.&lt;/SPAN&gt; Session length should be based on the company’s risk tolerance. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;margin-bottom: 11px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;&lt;SPAN style="background: white;"&gt;Record sessions. &lt;/SPAN&gt;&lt;/B&gt;&lt;SPAN style="background: white;"&gt;Engineering team leads and managers should leverage session recordings for audit purposes.&lt;/SPAN&gt; Session length should be aligned with the company’s risk tolerance. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Thu, 05 Nov 2026 19:43:16 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2026-11-05T19:43:16Z</dc:date>
    <item>
      <title>Idira Secure Cloud Access (SCA) Policy Best Practices</title>
      <link>https://live.paloaltonetworks.com/t5/secure-cloud-access-articles/idira-secure-cloud-access-sca-policy-best-practices/ta-p/1430028</link>
      <description>&lt;H2 style="margin-top: 11px;margin-bottom: 5px;"&gt;&lt;SPAN style="font-size: 16pt;"&gt;&lt;SPAN style="line-height: 107%;"&gt;&lt;SPAN style="font-family: &amp;quot;Aptos Display&amp;quot;,sans-serif;"&gt;&lt;SPAN style="color: #0f4761;"&gt;&lt;SPAN style="font-weight: bold;"&gt;Idira SCA Policy Best Practices&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: &amp;quot;Aptos Display&amp;quot;,sans-serif;"&gt;&lt;SPAN style="color: #0f4761;"&gt;Purpose &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/H2&gt;
&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;This document is to help Idira customers to implement Secure Cloud Access (SCA) and focuses on best practices for creating and applying SCA policies.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;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).&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;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.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;

&lt;H3&gt;Steps&lt;/H3&gt;
&lt;H2 style="margin-top: 11px;margin-bottom: 5px;"&gt;&lt;STRONG&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: 'Aptos Display',sans-serif;"&gt;&lt;SPAN style="color: #0f4761;"&gt;Definitions&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/H2&gt;
&lt;UL style="margin-bottom: 11px;"&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Cloud role&lt;/B&gt; - 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. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;CSP &lt;/B&gt;– Cloud Service Provider. Specifically, AWS, GCP, Azure.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Job function/role&lt;/B&gt; – Represents a person’s job and the function they perform, such as a DB admin.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-bottom: 11px;margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Workspace &lt;/B&gt;– A general term used within this document to represent an AWS Account, a GCP Project, or an Azure Subscription. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;H2 style="margin-top: 11px;margin-bottom: 5px;"&gt;&lt;STRONG&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: 'Aptos Display',sans-serif;"&gt;&lt;SPAN style="color: #0f4761;"&gt;Model&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/H2&gt;
&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&amp;nbsp;The Idira SCA policy model is composed of two elements:&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;OL&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;What the SCA policies specify:&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;OL style="list-style-type: lower-alpha;"&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;Which cloud roles within each cloud environment can be assigned.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;Which principals (users, groups, job roles, etc.) can get the cloud roles assigned.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;The duration and time window when the assignment is made.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;The two types of SCA policies: &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;OL style="list-style-type: lower-alpha;"&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;Long-lived: Typically assigned to groups of users (per job role, team, etc.)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 8px;margin-bottom: 11px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;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.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;H2 style="margin-top: 11px;margin-bottom: 5px;"&gt;&lt;STRONG&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: 'Aptos Display',sans-serif;"&gt;&lt;SPAN style="color: #0f4761;"&gt;Top five best practices&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/H2&gt;
&lt;OL style="margin-bottom: 11px;"&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Apply least privilege.&lt;/B&gt; 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:&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;OL style="list-style-type: lower-alpha;"&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;Assigning policies only to required cloud roles. For example, a policy used by a DBA for accessing S3 buckets.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;Including only those identities that need specific role access. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Leverage automation.&lt;/B&gt; &lt;B&gt;Automate&lt;/B&gt;&lt;B&gt; &lt;/B&gt;policy creation via API/Terraform. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="tab-stops: list .5in;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Audit/remove standing access. &lt;/B&gt;&amp;nbsp;Remove assignments from existing CSP policies that are now defined by Idira SCA policies&lt;B&gt;, &lt;/B&gt;such as those from Identity Center permission sets.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Limit the policy timeframe when applicable.&lt;/B&gt; &lt;SPAN style="background: white;"&gt;Ensure that policies are created with appropriate time limitations and &lt;/SPAN&gt;an expiration date (if applicable)&lt;SPAN style="background: white;"&gt; to a specific workspace&lt;/SPAN&gt;. Use&lt;SPAN style="background: white;"&gt; short-term policies &lt;/SPAN&gt;for temporary access&lt;SPAN style="background: white;"&gt;. For extended, time-limited, or project work, use a defined timeframe (&lt;/SPAN&gt;for example,&lt;SPAN style="background: white;"&gt; 2-4 weeks).&lt;/SPAN&gt; &lt;SPAN style="background: white;"&gt;&amp;nbsp;This configuration ensures that developer eligibility and access permissions are only active with each request.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="tab-stops: list .5in;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Set appropriate access rules. &amp;nbsp;&lt;/B&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;UL style="list-style-type: circle;"&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;Add identities (groups, Idira Identity roles) to the policy according to least privilege. Use groups instead of individuals (specific user accounts) for general access.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="tab-stops: list .5in;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;Set maximum session lengths based on the workspace. For example, four hours for Development, one hour for Production. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 8px;margin-bottom: 11px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="tab-stops: list .5in;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;Define explicit work hours per region. If necessary, duplicate the policy for different time zones, to enable more granular access restrictions.&amp;nbsp; &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;H2 style="margin-top: 11px;margin-bottom: 5px;"&gt;&lt;STRONG&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: 'Aptos Display',sans-serif;"&gt;&lt;SPAN style="color: #0f4761;"&gt;Additional policy best practices&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/H2&gt;
&lt;UL style="margin-bottom: 11px;"&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="tab-stops: list .5in;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Establish a policy naming standard.&lt;/B&gt; See our dedicated &lt;A href="https://community.cyberark.com/s/article/Best-Practice-SCA-Policy-Naming-Convention" target="_self"&gt;SCA policy naming convention best practices article&lt;/A&gt; for information about this subject.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Use clear policy descriptions.&lt;/B&gt; Add a description about the purpose of the policy. For example:&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;UL style="list-style-type: circle;"&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;APAC team accessing the Contributor Cloud role for production Azure Intune.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 8px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;Developer team for full access to EC2 during CHG63287.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Use custom permissions. &lt;/B&gt;Use customized cloud entitlements when possible. &amp;nbsp;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.&amp;nbsp; &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Clean up policies regularly.&lt;/B&gt; Review and remove unused policies every six months.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Use conditions for access.&lt;/B&gt; 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.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="tab-stops: list .5in;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Have break-glass access policies ready&lt;/B&gt;. &amp;nbsp;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. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="tab-stops: list .5in;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Manually approve high-level (root) access. &lt;/B&gt;All high privilege requests should undergo&lt;B&gt; &lt;/B&gt;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).&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;Specific guidelines with Tags&lt;/B&gt;. A Ensure seamless developer productivity by enabling auto-approval based on tags tied to workspaces. &amp;nbsp;This automates the provision of necessary permissions for existing and new team members without manual approval delays. &amp;nbsp;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.&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;&lt;SPAN style="background: white;"&gt;Define policies for every environment.&lt;/SPAN&gt;&lt;/B&gt;&lt;SPAN style="background: white;"&gt; 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.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;&lt;SPAN style="background: white;"&gt;Leverage delegation.&lt;/SPAN&gt;&lt;/B&gt;&lt;SPAN style="background: white;"&gt; 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.&lt;/SPAN&gt; Audit &lt;SPAN style="background: white;"&gt;policies that were&lt;/SPAN&gt; created via delegation every 90 days to ensure least privilege.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;&lt;SPAN style="background: white;"&gt;Understand max session length. &lt;/SPAN&gt;&lt;/B&gt;&lt;SPAN style="background: white;"&gt;Maximum session lengths are set by cloud providers, with a&lt;B&gt; &lt;/B&gt;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.&lt;/SPAN&gt; Session length should be based on the company’s risk tolerance. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI style="margin-left: 32px;margin-bottom: 11px;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="line-height: 115%;"&gt;&lt;SPAN style="font-family: Aptos,sans-serif;"&gt;&lt;B&gt;&lt;SPAN style="background: white;"&gt;Record sessions. &lt;/SPAN&gt;&lt;/B&gt;&lt;SPAN style="background: white;"&gt;Engineering team leads and managers should leverage session recordings for audit purposes.&lt;/SPAN&gt; Session length should be aligned with the company’s risk tolerance. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Thu, 05 Nov 2026 19:43:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secure-cloud-access-articles/idira-secure-cloud-access-sca-policy-best-practices/ta-p/1430028</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-11-05T19:43:16Z</dc:date>
    </item>
  </channel>
</rss>

