Other Articles
- Secure AWS Deployments with OIDC
- Build Secure Network Subnet Topology
- Instance/Host Roles in AWS
- Enable AWS GuardDuty for Threat Detection
- AWS CloudTrail: API Logging and Activity Monitoring
- Data Protection Using Envelope Encryption
- Restricting SSH Access on AWS Using IP Whitelisting
- GitHub – Enabling and Managing Dependabot Scans
- Removing Default VPCs and Blocking Their Recreation with an AWS SCP
- Secure Build Pipeline Controls: How to Protect Your CI/CD Process
- Production Access Control and Management
Infrastructure Environment Segmentation and Access Management
Overview
This article explains how to separate cloud infrastructure into distinct environments and manage who can access each one. It describes the controls that help keep access secure, controlled, and authorized across cloud platforms.
The examples use AWS, Microsoft Azure, and Google Cloud, but the principles apply to other cloud platforms as well.
What Is Environment Segmentation and Access Management?
Environment segmentation means keeping development, testing, staging, and production in separate, isolated areas of your cloud rather than running them together in one environment. In AWS, these areas are typically separate accounts; in Azure, they are subscriptions; and in Google Cloud, they are projects.
Access management determines who can sign in to each environment and what they are allowed to do. It is most effective when centralized, allowing access to be granted, changed, and revoked through a consistent process.
Why Segment Your Environments?
- A mistake or security compromise in one environment is less likely to spread to another.
- Production systems and data remain separate from the people and tools used to build and test software.
- Developers can experiment in development without putting live customer systems at risk.
- Costs, quotas, and permissions can be managed independently for each environment.
- Security frameworks such as ISO 27001 and SOC 2 emphasize appropriate separation of development, testing, and production, depending on the applicable requirements.
- Clear boundaries make it easier to identify who has access to each environment.
Benefits
- Live systems are better protected from accidental changes.
- Each environment has a clearly defined purpose and owner.
- Role-based access makes permissions more consistent and easier to review.
- Joiners, movers, and leavers can be managed through a centralized identity system.
- Security incidents are easier to isolate and contain when environments are properly separated.
How It Works
Secure environment segmentation and access management rely on the following six controls.
1. Use a Separate Account for Each Environment
- Keep development, testing or QA, staging, and production in separate accounts, subscriptions, or projects.
- Use production only to run the live application. Do not use it for development or experimentation.
- Keep staging sufficiently similar to production to validate changes before release, while protecting production data and credentials.
- Consider separate accounts or projects for shared services, such as centralized logging and security tooling.
2. Manage Accounts Through One Organization
- Group cloud accounts or projects under a central organization so that they can be governed consistently.
- Apply organization-level guardrails, such as restrictions on which regions can be used, where supported.
- Define clear ownership and billing arrangements for each account or subscription.
3. Use a Central Identity Provider and Single Sign-On
- Connect your cloud environments to your company's identity provider, such as Google Workspace, Microsoft Entra ID, or Okta.
- Allow employees to sign in using their company identities instead of maintaining separate cloud usernames and passwords wherever centralized identity is available.
- Enforce multi-factor authentication (MFA) through the identity provider.
- When someone leaves the company, disable their company identity and revoke any remaining sessions or credentials as part of the offboarding process.
4. Grant Access Through Groups and Roles
- Create groups based on job functions, such as developers, QA engineers, DevOps engineers, and read-only viewers.
- Assign each group only the permissions it needs in each environment. Avoid granting permissions directly to individuals unless there is a justified exception.
- Update group membership when a person's role or responsibilities change.
5. Apply the Strictest Controls to Production
- Limit production access to a small, authorized group, such as the DevOps team and designated senior personnel.
- Give developers and testers access to the environments they need, rather than granting production access by default.
- Make routine production changes through an approved deployment pipeline instead of making manual changes wherever possible.
- Record production access and administrative actions so that activity can be audited.
6. Apply Least Privilege and Review Access Regularly
- Give each person the minimum permissions required to perform their responsibilities.
- Use temporary, time-limited access for sensitive tasks wherever possible.
- Review access to every environment regularly, for example, every quarter, and remove permissions that are no longer needed.
- Never share accounts or credentials between people.
Applying These Controls in Your Cloud
The same six controls can be applied across cloud platforms, although service names and implementation details differ. Use the following examples as starting points, and consult your provider's documentation for current capabilities and configuration requirements.
- AWS: Use AWS Organizations to group accounts and establish separate accounts for each environment. Use AWS IAM Identity Center to connect an identity provider and assign permission sets to groups.
- Microsoft Azure: Use separate subscriptions grouped under management groups. Use Microsoft Entra ID for sign-in and assign Azure role-based access control (RBAC) roles to groups.
- Google Cloud: Use separate projects grouped into folders under an organization. Use Cloud Identity or Google Workspace for sign-in and assign IAM roles to groups.
- Other platforms: Look for equivalent features, including isolated accounts or projects, single sign-on through your identity provider, organization-wide guardrails, and group-based role assignment.
Common Use Cases
- Setting up a new cloud environment for a product or team.
- Separating production from development and testing workloads that currently share an account or project.
- Supporting users in different geographic regions while applying consistent access controls.
- Reviewing and tightening permissions after a team or organizational change.
- Giving new employees and contractors the appropriate access quickly and removing it when it is no longer needed.
Example Scenario
- A company maintains separate cloud accounts for development, testing, staging, and production.
- Developers work in the development account, while the QA team tests changes in the testing account.
- The staging environment closely resembles production, allowing the team to validate changes before release.
- The production account runs only the live application, and access is limited to the DevOps team and designated senior personnel.
- The company connects its identity provider to the cloud through single sign-on, allowing employees to use their company credentials.
- Access is assigned through groups. A new developer added to the developer group receives the permissions associated with that group, subject to the configured access policies.
- The production application can run in multiple regions to serve users in different locations, with consistent access controls applied across the relevant resources.
- When an employee leaves the company, their company identity is disabled and their remaining access, sessions, and credentials are revoked through the offboarding process.
Best Practices
- Define each environment's purpose and document the design before creating accounts or projects.
- Never use production for development, testing, or experimentation.
- Use single sign-on with multi-factor authentication for human access.
- Assign permissions to groups and roles rather than individual users wherever possible.
- Keep the number of people with production access as small as possible.
- Use automated deployment pipelines for production releases wherever possible.
- Apply consistent access policies across every region and environment.
- Review permissions regularly and remove accounts or access rights that are no longer required.
- Use clear, consistent names for accounts and environments so that production cannot be mistaken for another environment.
- Assign an accountable owner to every account, subscription, or project.
Common Mistakes to Avoid
- Running development, testing, and production workloads in the same account or project without adequate isolation.
- Creating individual cloud users and passwords when centralized single sign-on is available.
- Giving broad administrator permissions to many people as a precaution.
- Granting permissions directly to individuals without a clear reason, making access harder to review.
- Leaving access in place after someone leaves the team or changes roles.
- Allowing developers to make unapproved manual changes to production.
- Sharing a single login or credential among several people.
- Applying access controls inconsistently across regions or environments.
Updated on 28 October, 2026