A.8 Technological controls

A.8.31 Separation of development, test and production environments

Not mandatory by default – decided in your SoA

What it means in plain language

Keep development, test and production environments separate and secured.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

Environment separation reduces the chance that a defect, misconfiguration, or insecure test action affects live services. In practice, auditors often look for clear ownership of each environment, restrictions on cross-environment access, and evidence that test data is not treated like production data. Teams should show that design decisions, deployment paths, and access rights are intentionally different for development, test, and production.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Development and production share credentials, networks, or storage, allowing unintended access and weakening environment isolation.
  • Test systems contain live customer records without masking approval, retention limits, or deletion evidence after the test ends.
  • Developers can push directly to production outside a controlled release path, so segregation of duties and rollback planning are unclear.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Define each environment’s purpose, hosting boundary, approved users, and allowed data types in the Development/Test/Production Separation procedure. Assign the platform owner and release manager to maintain cloud account separation, network rules, and access reviews, while project teams request temporary access through tracked tickets.
  • Require masked or synthetic data for testing by default. Where production data is requested, route approval through the system owner and privacy lead, record the business need, masking constraints, retention date, and deletion confirmation. Link this to A.8.11 and the data-handling procedure so teams do not rely on verbal consent.
  • Configure technical barriers that make cross-environment drift visible: separate IAM roles, distinct secrets stores, named deployment pipelines, and environment-specific configuration files. Capture exceptions in a register with risk acceptance, compensating controls, and expiry dates. Review exception status during release meetings and monthly access recertification.
  • Use practical evidence points such as environment diagrams, access control lists, pipeline logs, and sample change tickets that show promotion from test to production. Add periodic walkthroughs for developers and testers so they understand that the control is about safe separation and traceable transitions, not just naming conventions.

What an auditor will ask to see

  • An environment architecture diagram showing separate accounts, subnets, secrets, and deployment paths for development, test, and production.
  • A ticket approving production data masking for test, with named approver, retention date, and deletion confirmation attached.
  • A monthly access review export showing no standing developer access to production, plus any temporary break-glass access records.
  • A release record showing promotion from test to production with peer approval and a rollback note.

Baseline documents in the kit

These free kit documents help you document or evidence A.8.31. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.8.32 — Change management and A.8.33 — Test information. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.