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.